I’m really excited to see our editorial flow get some love in the 3.6 cycle! We always want to be as extensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. as possible and post statuses are one of those places where we’re not near as good as we should be. The plan goes something like this:
- Fully support the existing register_post_status() API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
- Make sure things don’t break when you add your own custom statuses
- Update the metabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. UI User interface to show any newly registered statuses in the drop down, etc.
- Add a ‘moderation’ flag so that unpublished statuses can be explicitly identified
- Support for non-standard public post statuses
- Enhance the existing API
- Add support for registering post statuses to specific post types
- Allow for caps checks on different post statuses
- New remove_post_status() function for removing an already-registered post status
- Editing workflow for already published content
Additionally, we hope to address some issues around post meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. for revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., which is tightly related to the workflow for already published content.
@markjaquith and I have chosen Daniel Bachhuber to lead this. If you’re not sure why, just Google WordPress Edit Flow and it’ll all make sense. There’s a lot of heavy-duty under the hood work here, so please leave a comment if you’re interested in lending a hand.