FRONT-END FOUNDATIONS
HTML · CSS · JavaScript
Document structure, responsive layouts, keyboard-accessible controls and interaction that supports the content.
In practice: publication & search interfaces ↗ENGINEERING / A CLOSER LOOK
Engineering
the platform.
We choose technology around the work it must do: how information arrives, how people find it, how the experience performs and how the next release is controlled.
TECHNICAL CAPABILITIES
Tools behind
the work.
Our publishing and information work uses front-end development, build tooling and data processing. The examples below show where each is used.
APPLICATION & BUILD TOOLING
JavaScript · Node.js
Content generation, route inventories, modular build logic and automated checks around the publishing process.
In practice: repeatable platform builds ↗DATA & DOCUMENT PROCESSING
Python
Extract and reconcile source material, prepare structured records and generate documents from data.
In practice: source processing & PDF generation ↗CONTENT & DATA MODELS
JSON · structured records
Separate content from presentation. Retain identifiers, source context and predictable fields for search and publication.
Explore the information model ↗RELEASE & QUALITY TOOLING
Git · GitHub Actions · Vercel
Reviewable changes, automated checks and a defined route from source to a verified deployment.
See the delivery approach ↗These are verified foundations in the current work, not a claim that every project uses the same stack. Frameworks, databases, APIs and external services are selected against the brief, security requirements, maintenance needs and the people who will operate the system.
01 / SOURCE
Capture context.
Records, documents and editorial inputs, with ownership and source references.
02 / MODEL
Make it consistent.
Predictable fields, identifiers, validation rules and explicit exceptions.
03 / EXPERIENCE
Make it useful.
Templates, browse paths, filters and interactions shaped around the audience.
04 / RELEASE
Make it reviewable.
Defined checks, approval points, operating instructions and a recovery route.
Checks that belong
in the build.
The TPR platform source includes regression tests, source-integrity checks, route and crawl-path audits, and indexability validation. Its release process distinguishes a protected review from a public production build and retains a rollback target.
Playwright and axe browser and accessibility review tooling supports a defined testing and release process.
Checks are defined against the requirements of the platform.
From raw material
to usable output.
Python processing in the platform workflow extracts tabular source material, checks records against the original documents and preserves source context. That makes it possible to distinguish a verified field from a gap that still needs investigation.
A public PDF-generation sample also demonstrates a data-driven publishing workflow using Python and ReportLab: structured inputs become styled tables and a reusable document layout.
Explore the information modelINTERACTIVE EXPLAINER / STRUCTURED INFORMATION
One model.
Several useful ways in.
Search and filter this small editorial index, then inspect the record behind an item. It demonstrates how a consistent content model can support multiple routes through information.
A curated demonstration using example content from The People’s Register. Runs locally in your browser.
Enable JavaScript to explore the example index.