Category 4 of 8 · 28 terms
Structure and systems
Models, types, components, CMSs. The scaffolding under the words, and why it decides what you can reuse.
All 28 terms in this category
- Atomic contentContent broken into small, structured, reusable pieces that get assembled into pages rather than copied between them.
- BackendEverything behind the scenes that stores, shapes and supplies the content people meet in a website, app or other channel.
- CMSThe software used to store, organise and publish content.
- ComponentA reusable part – of content, design or code – made once and used in many places.
- Content modelA structured definition of the content types an organisation has and the fields, parts and rules that make each one work.
- Content patternA proven, recognisable approach to something content needs to do again and again, adapted each time it is used.
- Content typeA category of content with a defined purpose and structure, such as a case study or an event.
- Create once, publish everywhereThe idea that content should be created once in a structured form and reused across channels instead of rewritten each time.
- DatabaseA structured place to store information so it can be queried, related and reused.
- Design systemA shared, maintained collection of components, patterns and guidance that teams use to design and build digital products and services.
- Domain modelA representation of the important concepts, relationships and rules in a defined area of knowledge or activity.
- DRY“Don’t repeat yourself”: keep one reliable source of truth instead of many drifting copies.
- FindabilityThe ease with which people and systems can locate content they know or suspect exists.
- FrontendThe part of a website, app or other channel that people see, hear and interact with.
- Headless CMSA content management system that stores content separately from the places where that content is presented.
- Information architectureThe way information is grouped, labelled and connected so that people can find it and make sense of it.
- Knowledge baseA structured collection of useful knowledge that people and systems can search, link, maintain and learn from.
- MetadataInformation about content that helps it be found, filtered, understood, reused and managed.
- MicrositeA small, focused website or section created for a campaign, product, audience or specific purpose.
- Paddle, swim, diveA way to organise one topic at different, useful depths, so people can get an overview, more detail or the full evidence without being sorted into fixed audience segments.
- PDFA fixed-layout document format often used for reports, forms and downloads – useful sometimes, overused often.
- SchemaA definition of what information something contains and how it is structured.
- SEOImproving how content is discovered and presented in search engines.
- Structured contentContent broken into meaningful parts so it can be managed, reused and presented in different ways.
- TaxonomyA controlled set of categories or labels, usually arranged from broad to narrow, used to classify content consistently.
- Ubiquitous languageA shared, precise vocabulary used across conversations, documentation and systems within a defined area of work.
- VersioningKeeping track of different versions so changes can be compared, reviewed or restored.
- WireframeA sketch of the structure of a page or screen before the final design is made.