Content model
Structuring what exists, naming what repeats, and deciding what the editor owns.
WEB-01 / SITEKNOuX WEB
Institutional Website
A site that has to stay correct for years
A site whose quality is mostly editorial discipline: a content model that survives reorganisations, an accessibility baseline that does not regress, and a build a non-specialist can safely update without breaking layout.
FIG. CORPORATE / SITEEditorial grid
01Content model02Interface system03Accessibility04Delivery
01 / ARCHITECTURE
The disciplines
Interface system
Typography, spacing and component rules that hold across unpredictable content lengths.
Accessibility
Keyboard paths, contrast, focus order and screen-reader labels treated as build requirements.
Delivery
A build and hosting arrangement with a documented update path.
02 / HANDOVER
What the build contains
- Content model and page inventory
- Design token set and component library
- Accessible, tested build
- Update and ownership documentation
03 / PLATFORM
Starting points
01Next.js for highly dynamic or multi-role sites
02WordPress where the editorial team needs a familiar admin
04 / SCOPE
Questions that change the architecture
- How many people will publish, and how often?
- Does legal or compliance review apply to any of the content?
- Is there a design system already in place?
05 / CONNECTIONS
Connected capabilities
Related across KNOuX
WEB-01 / NEXT STEP
Define the brief.
A site that has to stay correct for years