Static Website Article API
A static article website publishes finished files instead of assembling pages at request time.
Explore this guide ↗🧩 Publishing · Topic field guide
Website Builder Article API
An article record can feed a visual website builder, but the receiving page still needs a coherent layout. Text blocks, image components, summaries, and navigation are editorial decisions as well as field mappings.
Start with the right boundary
Start with a small set of reusable page sections. A predictable article template is easier to review than a workflow that invents a new layout every time content changes.
A practical workflow
01. Inventory the components
List the title, introduction, section bodies, figures, callouts, and related links your page template supports. Decide what happens to unsupported blocks.
02. Map content deliberately
Connect article fields to the right components without flattening every section into one rich-text box. Keep visible headings in a logical order.
03. Test beyond the canvas
Review the published output, not only the builder preview. Inspect mobile spacing, reading order, links, images, and metadata.
Before the next handoff
- Unsupported content has a defined fallback.
- The published page keeps a logical heading order.
- The layout survives long titles and short summaries.
KEEP THIS IN MIND
Do not assume a visually attractive editor preview guarantees accessible or search-readable output. Inspect the resulting page directly.
Can the same article use different page designs?
Yes. Keep the article record separate from presentation, then review each template against the same content and accessibility goals.
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.