The challenge
Hand-building thirteen service pages guarantees drift: inconsistent headings, missing schema on the page nobody checked, and three slightly different versions of the same call to action.
Objectives
- Keep thirteen pages structurally identical
- Guarantee schema and metadata on every page
- Make a global change a one-line edit
- Keep the output fast and dependency-free
What we built
A Python build system that generates every page from a shared component library and a content definition, so structure, metadata and schema are produced rather than remembered.
Technology
CSS · HTML · JSON-LD · Python build system
How it was delivered
- Component library defined once and reused across all pages
- Content and metadata held in structured definitions
- JSON-LD generated per page from the same source
- Single-file output with no runtime dependencies
- Global changes applied by rebuilding rather than editing thirteen files
Outcomes
- Every page carries complete, correct metadata
- A change to the CTA is a single edit and a rebuild
- No structural drift between pages
- Output stays lightweight and fast