Page Status

The Status field records a page's editorial lifecycle state — where the page is in its journey from first draft to finished content. Set it from the Status select in the page editor, next to User Keywords.

The states

Statuses are defined by your administrator (see Configuration). The shipped defaults, in lifecycle order:

A page with no status is published. The default state is represented by absence: choosing Published in the editor removes the status: field from the page's Frontmatter rather than writing it.

How it is used

• Editor — the Status select shows the current state and saves your choice with the page.
• Search — status is indexed, so searches can filter by lifecycle state (e.g. find every draft page awaiting work).
• Frontmatter — stored as a single status: field:

---
title: My Article
status: review
---

What Status is NOT

• Not a keyword. Older versions used draft / review / published as user keywords. Those migrated to the status: field automatically — if a page still carries them as keywords (for example after restoring an old backup), they are converted the next time the page is saved.
• Not access control. A draft page is just as visible as a published one. To restrict who can see a page, use Page Private or the page's Audience; to restrict who can edit it, use Author Lock.

Configuration

Administrators define the available states in configuration under ngdpbase.status. Each entry has a label, description, lifecycle order, and an enabled flag; exactly one entry carries default: true (the state an absent field means). Deployments can add states — for example an archived state after published — via the custom configuration file, with no code change.

Related pages

• Frontmatter — all page metadata fields
• Keywords and Categories — how status fits the wider vocabulary model
• Page Private — visibility control (a flag, not a status)
• Author Lock — edit control (a flag, not a status)