Understanding Config vs Content: A Level 0 Foundation in Drupal
The distinction between configuration and content is one of the most important concepts in Drupal, according to a beginner-focused article by Saroj for Weekly Drupal. Understanding how Drupal treats site structure versus user-generated data can prevent long-term technical issues and enable smooth team collaboration.
Configuration refers to the structure of the site content types, fields, views, permissions while content includes the actual data, like nodes, taxonomy terms, and media items. Drupal treats these differently on purpose. Configuration is deployable and version-controlled, while content lives in the database and changes frequently.
Saroj outlines common mistakes made by beginners, such as editing config directly on production, using content nodes for global settings, or entering data before defining structure. These practices lead to broken deployments and inconsistent environments. A config-first mindset, where structure is built before content is added, forms the backbone of reliable Drupal workflows.
The article concludes that this principle underpins every Drupal project, especially for teams using CI/CD or managing multiple environments. Beginners are encouraged to treat configuration as code, document decisions, and avoid relying on production-only changes. As the author puts it, clear separation “reduces risk and improves confidence.”

