A CMS is an editorial system with drafts, revisions, permissions, and attached media. A public site consumes only an approved view. The four lessons follow one article from a versioned public route through a private preview, an exact media asset, and a publication event that must reach caches and discovery surfaces. Each page gives an operational failure, a bounded implementation, checks, and links to adjacent Web Development topics.
Topics in this track
- CMS Public Projections and Route Identity — Expose only published fields through stable route identities and explicit response contracts.
- CMS Draft Preview Authorization and Cache Isolation — Bind preview access to a caller and revision while preventing private responses from reaching shared caches.
- CMS Media Variants, Alt Text, and Asset Ownership — Publish bounded media metadata with stable assets, useful alternatives, and deliberate retention.
- CMS Publish Events, Cache, Search, and Rollback — Reconcile a publication revision across routes, caches, search, and linked navigation.
Prerequisite paths
Content Discovery and Structure; HTTP Delivery and Cache Ownership; Authorization and Tenant Boundaries.
Practice and check
Build Project: CMS Publication Reconciliation and review Web Development: CMS publication contracts.