Editorial Flow Update, 2/7
Editorial flow is making progress and hitting interesting questions to answer. Our two primary tickets right now are #12706 and #23314.
For the first, we’re waiting on feedback on the approach from @nacin. Once we’ve gotten confirmation it’s the right direction, I’ll continue working to make the patch commit-ready.
For the second, the biggest question was how we should handle revisions for post meta and taxonomy terms. In the interest of getting to a committable patch, we’ll be dropping post meta / custom taxonomy support in favor of just being able to stage edits for the title and body content. Furthermore we’ve decided it would be worthwhile to add a new post type property so this functionality is opt-in. Posts and Pages in core will receive this by default.
Our primary goals are to have commit-ready patches for both tickets by the beginning of next week. Konstantin’s secondary goal is to chat with @westi and @ethitter and see whether revisions for post meta is within scope for 3.6. My secondary goal is to go through other editorial flow tickets and touch base with where each is at.
Next office hours are Tuesday, February 12th at 10 am PT / 1 pm ET / 1800 UTC.
Jon Brown 2:12 am on February 8, 2013 Permalink
Initially I was disheartened that you guys were dropping metadata support, but read the irclogs and it makes sense and I’m glad their are still advocates for adding it back in later.
All of which I share only to say, THANK YOU, for such an open and transparent process. Really all the teams are doing a fabulous job and all the communication is hugely appreciated, so thank you for that and all the great work.
Erick Hitter 2:21 am on February 8, 2013 Permalink
Tuesday office hours conflict (for me) with the WordCamp Base Theme chat, so I’ll note here that meta revisions are not in scope for 3.6.
While the relevant tickets (#20564 and #20299) marked as 3.6, we’ve spent a good deal of time on UI/UX, and that will likely continue to be the bulk of our focus for this iteration. @nacin marked both as 3.6 because they block #23314, but we (@westi, @adamsilverstein, @karmatosed, and I) don’t have the availability to address them at this time.
crushgear 4:16 pm on February 11, 2013 Permalink
Hi Daniel — you previously requested for some workflow examples. Here’s an example workflow from a WordPress.com VIP publisher:
1) Writer puts text in WordPress and saves as “pending review” so the editor knows its ready.
2) An editor goes in and edits the text in WordPress and schedules the post to publish, or publishes immediately if breaking news.
3) The post goes live.
4) A producer goes in and updates the appropriate fields, if they are not already filled out (category, social text, SEO headline etc). Also could fix any typos found post-launch. Probably wouldn’t need approval before going live.
5) A photo editor goes in and adds a featured image (these changes could go live without approval) and updates the post.
Revisions:
Suggestions: