Skip to main content
Mediacurrent logo
Hero Background Image

Blog Post

Webinar: Code-per-Node

by Damien McKenna
December 26, 2013

Drupal has many well documented best practices, many of which we've covered here previously. From using Features to export all site configuration, to applying updates on a copy of the site instead of production, to using a modern responsive base theme, there is usually a tried & trusted process for most scenarios that can help keep sites stable, and editorial teams & visitors happy. There are, however, some (very, very, very) rare occasions when it can be necessary to break with convention, cause designers & developers to pull their hair out and run around screaming, and allow the editorial team to add custom CSS (or JavaScript) to individual pages. The Code-per-Node module provides a structured, reliable and easy-to-use solution for these occasions.

Headshot

Meet team member, Damien McKenna

Damien directs internal initiatives that strengthen Mediacurrent’s commitment to open-source principles, collaboration, and sharing knowledge. Regularly ranked as one of the ten most active contributors on drupal.org, Damien has been a significant member of the Drupal community since 2007.

Related Insights