Content driven by data

Operations

Content driven by data

The same shared catalog powers site, APIs, exports and derived pages, reducing drift between narrative, runtime and operations.

Back to operations Operations payload

Why it matters

This layer avoids editorial rework and makes every new surface auditable from the source.

central catalog reused by theme, workbench, discovery and exports
deterministic public artifacts generated before dev, test and build
dossiers and filters derived from the same canonical inventory

Quality gates

npm run site:export
npm test
npm run build

Linked routes

/api/catalog · Shared catalog powering the site and public layer.
/api/discovery · Flat inventory of public resources for filters, automation and exploration.
/api/portfolio · Filterable snapshot of portfolio cases, stacks, categories and signals.
/api/stacks · Map of recurring technologies with links between portfolio and capabilities.
/api/projects · Filterable directory of technical and operational project dossiers.

Capabilities

Related projects

Related categories

Stacks