Detailed guide. An unofficial adaptation of User Guide 1.1. Source updated April 14, 2025; reviewed November 6, 2026. No running-Drupal procedure test has been performed.
Official source ↗ · Chapter 1 overview · Next: 1.2 Modules
Goal
Understand how editing content relates to configuring a Drupal site. This is a conceptual introduction, not an installation procedure.
What a CMS does
A CMS supports adding, publishing, editing and removing website content through a browser. In a typical setup, server-side programs combine database content and configuration with assets such as images, CSS and JavaScript to construct pages.
Drupal and its stack
Drupal is a general-purpose CMS with modules for functionality and themes for presentation. Drupal Core provides the base software, bundled extensions and assets. The source illustrates a stack with Linux, Apache, MySQL and PHP, while also naming alternative operating systems, servers and databases. PHP remains the language used to run Drupal’s programs.
Our qualification: these examples are not a version-compatibility matrix. Check the requirements for the release you intend to install; see the installation summary .
Choosing an approach
The source contrasts small static sites, CMS setup, purpose-specific services and general-purpose Drupal. It highlights browser editing, consistency, database-backed features, established account and content functionality, licensing and community contributions.
Our planning comparison:
| Question | What to record for your project |
|---|---|
| Who edits content? | Whether browser-based editing is needed |
| What repeats across pages? | Shared structure and presentation requirements |
| What features are needed? | Whether a specialized tool fits the full scope |
| Who maintains it? | Responsibility for updates and operation |
Our understanding check
Choose one page and identify its editable content, the feature that produces any listing, and the presentation applied by the theme. Continue with modules , themes and data types .
Connection to changes
The selected annotations concern specific extensions and packaging, not a replacement of the CMS concept. Consult the core release archive and security archive for the intended version. A conceptual overview is not a guarantee of version-specific behavior.
Sources, credits and changes
Source: Drupal User Guide 1.1 ↗ . Contributors and source links listed in its Attributions: Kristof van Tomme ↗ · Pronovix · Jennifer Hodgdon ↗ · Michael Lenahan ↗ · erdfisch . Refer to the source for writing, editing and adaptation roles, and to the guide-wide credits ↗ .
Copyright remains with the individual contributors; the official copyright page ↗ states © 2015–2025. Changes include reorganized explanations and procedures, our preparation and verification examples, troubleshooting notes, source-interpretation qualifications and release references. Original screenshots and videos are not reproduced. This adapted text is shared under CC BY-SA 2.0 . It is not an official edition or endorsement. This notice does not license unrelated articles or the site design.
Chapter navigation
Chapter 1 overview · Next: 1.2 Modules
Preface · Chapter 2 · All chapters · Search official information