product-example 1 linked patterns checked
WordPress post status
Documents post statuses such as publish, draft, future, pending, private, trash, role and capability-based workflow, and how post status controls whether content is public, scheduled, or awaiting review.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Publish workflow | Choose publish workflow when the primary task is making edited material visible, live, scheduled, retired, or no longer visible in a selected destination. | Saving a draft does not imply publication, and publishing cannot proceed until target, readiness, permissions, and validation requirements are resolved. | WordPress supports publish, draft, future, pending, private, trash, role-based workflow, and post status as public visibility state. |
Comparisons supported by this source
- Publish workflow vs approval workflow vs review queue vs draft state
WordPress documents publish, draft, future, pending, private, and workflow behavior controlled by post status and roles.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: WordPress.org Documentation. Last checked: .