Practical guide
How to choose a Drupal theme layout
Compare themes using real content, visitor tasks, dependency checks, and a practical selection worksheet.
Content updated
Begin with a real page
Choose a representative article, service description, or product record. Include a long title, a real photograph, supporting links, and the next action you want the reader to take. Use the same content in every layout you compare.
A comparison worksheet
| Decision | What to record | How to check it |
|---|---|---|
| Primary task | Read an article, assess a service, or compare a product. | Ask a new reader to explain what the page helps them do. |
| Content regions | Main text, navigation, related reading, and optional promotion. | Remove optional blocks and see whether the task becomes clearer. |
| Images | Purpose, crop, source, rights, and text alternative. | Check the page with images unavailable and with a narrow screen. |
| Dependencies | Core version, modules, slideshow behavior, and external scripts. | Separate historical features from components you can currently support. |
| Interaction | Menu, form, gallery, or purchase behavior. | Test the entire journey with a keyboard, including errors and confirmation. |
| Maintenance | Who owns each page, document, and time-sensitive claim. | Give a stale page to the owner and ask what needs review. |
Choose the simplest useful structure
A service business often needs a small set of clear pages. A publication needs an article template and a stable archive. A product catalog needs consistent attributes. Choose by that structure before choosing a palette.
Example: a personal blog with occasional project work
Start with a reader who wants to understand the author and find a useful article. Crown offers a showcase and historical style options; Ripple takes a simpler presentation. Put the same author introduction, three post titles, and one project summary into both proposed layouts. Choose the structure that makes the writing easier to reach. This is a planning example, not a package test.
Example: a publication with several topic feeds
A publication needs repeatable article fields before it needs more homepage blocks. Compare Insight’s two historical showcase treatments with Showbox’s Views-based arrangements. Decide whether a second featured package answers a different reader need. If it does not, use one lead story and simpler topic feeds. Document the fields and feed rules for the rebuild rather than assuming old configuration can be reused.
Record your shortlist
For each candidate, write down the reader task, the content regions you need, the dependencies to replace, and one reason to reject the design. Resolve missing information before making a final selection. A screenshot is evidence of composition, not proof of current compatibility or accessibility.
Compare all 31 historical theme specifications or use the printable website planning worksheet.