-
Notifications
You must be signed in to change notification settings - Fork 2
Validation on publish #93
Copy link
Copy link
Closed
Labels
UXUser Experience polish in the CMS; usability, information architecture.User Experience polish in the CMS; usability, information architecture.content lifecycleWorkflow, approvals, localization, archiving, content governance.Workflow, approvals, localization, archiving, content governance.scaleHigh-traffic, multi-site, large content sets, reliability at scale.High-traffic, multi-site, large content sets, reliability at scale.sponsoredWork funded by sponsors; going ahead thanks to their support.Work funded by sponsors; going ahead thanks to their support.
Milestone
Description
Metadata
Metadata
Assignees
Labels
UXUser Experience polish in the CMS; usability, information architecture.User Experience polish in the CMS; usability, information architecture.content lifecycleWorkflow, approvals, localization, archiving, content governance.Workflow, approvals, localization, archiving, content governance.scaleHigh-traffic, multi-site, large content sets, reliability at scale.High-traffic, multi-site, large content sets, reliability at scale.sponsoredWork funded by sponsors; going ahead thanks to their support.Work funded by sponsors; going ahead thanks to their support.
Type
Projects
Status
v7.0 May 2025
Summary
Implementation of a frequently-requested feature: save draft versions of pages in an incomplete state, while still enforcing validation when publishing. This is a pre-requisite to implementing auto-save as proposed in RFC 99: Preliminary work to support auto-save functionality.
Intended Outcome
Incremental progress towards auto-save functionality in Wagtail.
More information
See RFC 104: Validation on publish.
This roadmap item is sponsored! ❤