Many designers are praising the benefits of Atomic Design. Rather than designing pages, Atomic Design focuses on designing systems of individual, reusable components. Designers aren’t the only ones thinking this way. This article explains why development is one area of a project that stands to benefit the most from this change in thought and walks through how to build components “the Drupal way”.
Latest from our Blog
Welcome to the CHROMATIC blog. We discuss topics related to Drupal web development, responsive web design, web strategy, small business, and last but not least, our company and projects.
In a previous post, Dave talked about marginal gains and how, in aggregate, they can really add up. We recently made some infrastructure improvements that I first thought would be marginal, but quickly proved to be rather significant.
Drupal makes it so easy to add image fields to your content types. Fields in core for the win! With image styles in core, its as easy as ever to create multiple image sizes for display in various contexts (thumbnails, full, etc.).
Switching the default text format of a field is easy. Manually converting existing content to a different input format is not. What about migrating thousands of nodes to use a different input format? That isn't anyone's idea of fun!
Drupal is awesome, but it is also infamous for having a steep learning curve. From beginners to seasoned professionals, everybody has areas they could improve upon. To that end (and in true DrupalCon Austin training spirit), we’re giving away a full year of Drupal training from Drupalize.me!
Features play a significant role in any major Drupal 6 or 7 project. The organization of features is often overlooked, but becomes important as a project grows. Agreeing on an effective organization strategy avoids headaches and reduces merge conflicts. After experiencing just about every strategy on projects of all sizes, we’d love to share what works best for us.