WordPress REST API: start with a draft
Map a complete post, preserve its destination identity, preview the theme, and make publication a deliberate editorial step.
7 MIN READRead the guide
LAB COLLECTION / 2 ARTICLES
Websites & CMS
field notes.
Choose the right home for the story. Explore CMS drafts, static websites, page builders, and the practical boundaries between authoring, previewing, and releasing.
Inside this collection
Different destinations expect different artifacts. A CMS may accept a record, a static generator may consume content files, and a builder may expose a limited set of supported actions. The guides here focus on field mapping, media, stable destination identities, and release previews. They do not assume that every platform offers the same interface.
Your reading path
Choose one representative article with headings, an image, a caption, and internal links. Follow its path into a draft or generated release, inspect the real rendering, and make a correction. Select the WordPress, Hugo, or Ghost guide based on your actual destination rather than attempting to standardize every implementation detail too early.
Hugo publishing: ship a complete static release
Make generated files into an inspectable release with link checks, a clean artifact, public verification, and a recovery path.
7 MIN READRead the guide