CMS Article API
A CMS adapter translates your editorial record into the fields and workflow of a publishing platform. Keep that translation narrow.
Explore this guide ↗🖥️ Publishing · Topic field guide
Static Website Article API
A static article website publishes finished files instead of assembling pages at request time. The article workflow happens before deployment: gather content, validate it, render the pages, and deliver the resulting HTML, styles, scripts, and images.
Start with the right boundary
Draw a firm boundary between the build environment and the public website. A browser should receive the approved article, not the credentials or unpublished records used to create it.
A practical workflow
01. Keep an editable source
Store structured article records and assets in a versioned source collection. Separate content changes from layout changes so reviews stay focused.
02. Build a complete output
Render clean directory URLs, navigation, metadata, image references, archives, and feeds together. Check the output without relying on development-only tools.
03. Deploy and verify
Preview the files through an HTTP server, test deep links, and keep a known-good release for rollback. Verify the live domain after deployment.
Before the next handoff
- No secret material in public files.
- Every clean URL has its own index file.
- Images and feed links survive deployment.
KEEP THIS IN MIND
A static site does not become a hosted article-generation API merely because it describes one. Any private generation or publishing service belongs outside the public bundle.
Does the visitor need JavaScript to read a static article?
Not in the pattern used here. Core content and navigation are in HTML; JavaScript only enhances optional interactions.
Take the next step
Continue with from article records to a hugo static website for a complete explanation, practical decisions, and a source-backed reference. To compare the neighboring parts of the process, explore the full article workflow library.