Patterns
Whole pages, assembled from the components. A pattern is where the hierarchy decisions live: what leads, what follows, and what the reader does next.
Article page
Where 90 per cent of sessions start. Two ad slots, one next step, and the summary treated honestly.
Section front
One lead, strong secondaries, compact supporting. The importance of each story apparent without reading.
Data page
Price and market pages, where two figures from different months are the story.
Where the widgets go
Every one of the 62 current component files, mapped to what it becomes. Start here if you are asking "what happens to mine".
What a pattern decides
Components answer "what does this look like". Patterns answer "what matters on this page". That second question is the one the old frontend never answered consistently, which is why a category page, a search result and the homepage each grew their own card.
The hierarchy rule
Every page has exactly one lead. Under it, a small number of secondaries at a visibly lower weight, then compact items. A reader should be able to rank the stories on a page without reading a single headline. If two things both look like the lead, neither is.