@ti-engine/web-content
v0.4.0
Published
A content-publishing engine for ti-engine sites: path-index routing, deny-by-default content visibility, SEO document rendering, feeds, and email capture, layered on @ti-engine/web-framework. NOTICE: This is a work in progress and the full architecture, d
Maintainers
Readme
@ti-engine/web-content
A content-publishing engine for ti-engine sites, layered on @ti-engine/web-framework the way @ti-engine/competence is. It turns a set of registered content sources into a public website:
- Path-index routing — every URL (current, legacy, translated, aliased) is an index entry resolved by a single catch-all, not a set of competing route patterns.
- Deny-by-default visibility — a record with no explicit, recognised
visibilityis visible to nobody. Filtering is applied once, in the repository query layer, so every surface (listings, archives, sitemap, RSS, search, counts, prev/next) inherits it. - SEO documents — full server-rendered HTML per URL with canonical,
hreflang, Open Graph, and JSON-LD generated from the record. - Feeds & capture —
sitemap.xml/rss.xml/robots.txt, and an email-capture primitive (preorders / newsletter / beta signups).
Status: work in progress (0.x). The architecture, module surface, and API are still settling. See
design/author-site-engine.mdfor the design record and phased plan, and the consuming site's specs underSite/docs/for the content schemas, token contract, and build spec.
Requirements
- Node.js
>= 20.12 @ti-engine/web-framework>= 1.17.0
License
Apache-2.0 © Boris Kostadinov
