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
WordPress Page Article API
Evergreen WordPress pages need different editorial thinking from a chronological blog. An About page, a product explanation, and a documentation landing page often depend on hierarchy, navigation placement, and stable URLs more than publication order.
Start with the right boundary
Plan the page’s place in the site before transferring its text. Decide whether it belongs under a parent page, what navigation should point to it, and which existing URLs must remain stable.
A practical workflow
01. Define the page role
State whether the page introduces a topic, explains a process, or helps readers choose a next step. Keep this goal distinct from a blog announcement.
02. Map the page fields
Review title, body, excerpt where used, slug, parent relationship, featured media, and template expectations against the destination site.
03. Preview the full context
Check the theme layout, navigation, breadcrumb trail, mobile rendering, and internal links after creating a draft.
Before the next handoff
- A stable URL and intended parent.
- No accidental duplicate of a blog post.
- The page makes sense from the navigation.
KEEP THIS IN MIND
Do not assume that moving article text into a page automatically creates a useful landing page. The surrounding hierarchy and next-step links matter.
Should an evergreen guide be a page or a post?
Choose according to the site’s information architecture. A reference page may belong in a hierarchy; a dated editorial article may fit the blog archive.
Take the next step
Continue with a safer wordpress article workflow: draft, preview, publish 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.