Websites & CMS
Choose the right home for the story. Explore CMS drafts, static websites, page builders, and the practical boundaries between authoring, previewing, and releasing.
What connects these topics
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.
A useful way to begin
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.
Go deeper in the Lab.
Map a complete post, preserve its destination identity, preview the theme, and make publication a deliberate editorial step.
Choose a topic.
Website Publish API
Publishing a website involves pages, assets, metadata, and navigation. A website workflow should deliver a coherent release rather than treating every file as an unrelated upload.
WordPress Publish API
A WordPress publishing workflow benefits from a remote draft, editorial review, and a deliberate status change. Begin with the lifecycle before choosing how your own application authenticates.
Landing Page Publish API
A landing page needs a focused message and a complete release package. Explore small purpose-built pages without losing metadata, accessibility, or a working next step.
Hugo CMS Publish API
Hugo can sit behind an editorial interface as a static-site publishing target. This topic focuses on preparing content files for a separate website build rather than presenting a generator as a hosted CMS.
Website Builder Publish API
A builder integration starts with the capabilities of the chosen platform. Collections, page layouts, assets, and release permissions are separate questions, not one assumed universal operation.
Sites Publish API
Multi-site publishing is more than repeating a request. Each destination may have its own audience, path structure, editorial rules, and release authority.
Custom Website Publish API
A custom website lets you choose the content model and release process. Use that flexibility to make responsibilities clear rather than coupling every editorial field directly to presentation code.
WordPress Plugin Publish API
A plugin can add project-specific behavior inside WordPress. Begin by deciding what belongs within the CMS rather than duplicating an entire external publishing client there.
Hugo Website Publish API
A Hugo website release is the generated set of files readers receive. This topic concentrates on output directories, media, feed files, and a dependable deployment boundary.
Ghost Website Publish API
Ghost publishing involves administrative changes that are distinct from reading public content. Plan the workflow around preparing a draft, rendering it accurately, and approving its release.
Folder to Website Publish API
A folder-to-website workflow promotes a complete directory into a public release. Its simplicity depends on that directory containing everything needed to render the intended site.
Static Website Publish API
One static website can be released as a coherent set of files. This route focuses on a straightforward content publication with no application server requirement.
Static Websites Publish API
A fleet of static websites adds coordination work beyond a single-site release. Explore shared templates alongside distinct domains, editorial identities, and independent release records.