Reusable infrastructure for structured content processing, transformation, and publishing.
Content Engine provides the shared capabilities required to transform structured content into production-ready outputs.
Rather than coupling content processing to a specific application, this repository centralizes reusable content pipelines into a well-defined foundation.
Its purpose is to provide a consistent way to author, validate, transform, index, and distribute content across multiple projects.
Content-heavy applications repeatedly solve the same infrastructure problems.
Markdown needs to be parsed.
Metadata needs to be generated.
Content needs to be validated.
Feeds and sitemaps need to be produced.
Searchable representations need to be derived.
Reimplementing these capabilities inside every application creates duplication and inconsistent behavior.
Content Engine exists to provide those capabilities once, behind clear boundaries.
Content Engine may include:
- Content collections
- Markdown and MDX processing
- Front matter parsing
- Content validation
- Metadata generation
- Reading-time calculation
- Table of contents generation
- RSS generation
- Sitemap generation
- Search document generation
- Open Graph asset generation
- Syntax highlighting
- Static content pipelines
- Content transformation utilities
```text content-engine/ ├── collections/ ├── generators/ ├── markdown/ ├── metadata/ ├── opengraph/ ├── reading-time/ ├── rss/ ├── search/ ├── sitemap/ ├── validation/ └── utils/ ```
The structure will evolve as additional content capabilities are introduced.
Content should remain:
- Structured
- Typed
- Portable
- Framework-agnostic
- Build-time friendly
- Easy to validate
- Easy to transform
- Easy to extend
Applications should consume content without having to own the entire content-processing pipeline.
Content Engine owns the transformation of source content into useful structured outputs.
It does not own the systems that consume those outputs.
For example, Content Engine may generate searchable documents or indexes, while the Search repository owns retrieval, ranking, and discovery behavior.
This distinction keeps content processing independent from application and platform concerns.
Content Engine intentionally does not contain:
- UI components
- Application routing
- Application-specific pages
- Authentication or authorization
- Search ranking or retrieval systems
- Business logic
- Deployment infrastructure
Those capabilities belong in their respective repositories.
Content Engine is one reusable capability within the broader ecosystem.
It can integrate with:
- Search — Retrieval, ranking, and discovery
- Design System — Presentation of structured content
- Bootstrapper — Project scaffolding and integration
- Testkit — Shared testing infrastructure
- Observability — Diagnostics and telemetry
- Agent Network — Machine consumption and generation of structured content
Applications such as paszed.me can consume Content Engine while keeping their application-specific presentation and routing independent.
The long-term goal is to provide a complete reusable content foundation for documentation sites, blogs, portfolios, knowledge bases, developer portals, and other content-heavy software.
Applications should be able to adopt the capabilities they need without inheriting an application framework or tightly coupled publishing architecture.
Content Engine should remain a capability, not become a CMS.
Content Engine is under active development.
Its architecture will grow from concrete requirements across consuming applications rather than speculative abstraction.
Licensed under the MIT License.