Three pages. The twelve guides says who each guide is for and why Guides 1, 2 and 4 are not optional, whatever you are building. Finding your way around these docs explains the four kinds of page and when to reach for each. Conventions every theme follows lists the house rules once, so that no later guide has to repeat them; read it before your first review.
Unit 05 of 05
3 pages
Choosing what to read next
Where to go after this guide: the twelve guides and the three that are required, how to find an answer in these docs, and the house rules every theme follows, stated once. Short and navigational; its job is routing, not teaching.
In this unit
Read in order
01
The twelve guides
The twelve Developer Guides after this one, a line each on who it is for and when to read it. Three are required whatever you build: Choosing how to build, the template languages, and input types, layouts, components and images. Why those three.
02
Finding your way around these docs
These docs hold four kinds of page: guides read in order, how-tos for one task, troubleshooting answers for one symptom, and reference generated from the platform. Which to reach for, what the depth levels mean, how the how-to topics and search work, and why there is no filter by template engine.
03
Conventions every theme follows
The house rules for every Core dna theme, stated once so no later page repeats them: BEM class names in SCSS, a bundle per page type, a nonce on every script tag, a cache-buster on every asset URL, no secrets in tracked files, escaped output, and links built from route names.