Patterns
Patterns solve recurring tasks by composing existing components. They are distinct from the component library: a component is one reusable interface unit; a pattern explains how several units work together for a person’s goal.
The initial library documents existing behaviour first. Every pattern page records its composition, data or content requirements, responsive and accessibility behaviour, and source-backed implementation evidence. Use Components for individual interfaces and Pattern library for the authoring recipe.
| Documentation layout | The documentation shell that combines orientation, article reading, and deliberate continuation links | |
| Editorial article | The durable reading and continuation structure for blog posts and TIL notes | |
| Filterable collection | A data-driven collection with optional filters, structured results, sorting, and client-side pagination | |
| Reference index | The data-driven reference-page composition for finding and moving through a large structured dataset | |
| Site navigation | The site-wide header composition for primary navigation, search, language, and theme controls |