Update: What’s Coming Up With WordPress 3.6

The updated target date for WordPress 3.6 Beta 1 is March 27.

By the time Beta 1 rolls around, the core team will have the feature set complete, which means the time for bug testing 3.6 against your themes and plugins will have arrived. According to the 3.6 project schedule, the target date for 3.6 launch is April 29.

Here’s a quick update on where the 3.6 features currently stand. If you aren’t caught up on the features, please take a peek at this introduction post.

Post Formats UI: The UI for post formats is getting a refresh (featuring a drop down selector for formats and better previewing) to make it easier to use and faster to publish. You can take a peek at the wireframes here, and follow along the conversation here.

Autosave and Post Locking: The main goal of this update is so that users never lose a post. This is done by leveraging browser-level storage in modern browsers for situations where users lose their internet connections or their browsers crash. With this enhancement, edits are stored locally and synced back to WordPress at the next possible opportunity. If you are logged out while on an admin page, you will be notified and allowed to log in straight on the page so that you won’t lose your work. As for post locking, if you arrive on a page that is currently being edited, you will be given the option to “take over” or go back.

Revisions: The UI for comparing previous revisions of a post has been significantly updated, including a scrubber bar that allows the user to move forward or back in revisions, and colored text to indicate content that has been added or removed. Take a look at a rough mockup here.

Editorial Flow: This feature has been removed from the 3.6 cycle, but the team is planning to tackle it in future releases.

Menus: The UI for creating custom menus has been significantly cleaned up, with new checkboxes to select where the menu will be displayed in the theme, accordion styling to menu items (being tested), new help text and keyboard accessibility for rearranging menu items.

Twenty Thirteen: As Mark Jaquith writes: “With Twenty Thirteen we’re taking a bold stance: this theme was meant for blogging, and it’s not a blank canvas. It comes pre-marinated with playfulness and warmth and opinions.” Take a peek at a demo of the new Twenty Thirteen theme here.

Where can I find more information?

If you’re not familiar with Make WordPress Core, it’s a good blog to visit. It tracks the open-source development of WordPress, and is the homebase of much of the development discussion.

How do I get involved?

Want to help make WordPress better? Take a peek at the Core Contributor Handbook, or sit in on the weekly developer chat. They will need a lot of help with bug testing and squashing in the coming weeks. Lots of members of the VIP community contribute to core, so you’ll see familiar faces.

When is 3.6 coming to WordPress.com VIP?

Shortly prior to the release of 3.6 on WordPress.org, the 3.6 features will be merged into WordPress.com VIP. This will most likely happen in April, and we will be posting updates here in the weeks before to notify you. If you aren’t already, at that point you’ll need to be testing against trunk, getting the latest nightly build or even better, using an SVN checkout of trunk to test how your sites work on 3.6. You can also use the Beta Tester plugin to easily update beta releases and test.

What’s Coming Up With WordPress 3.6

Some really neat features are going to be included in WordPress 3.6, which is rolling out this spring.

Here’s a quick peek at the road ahead (but know that everything listed here is tentative, as it is still under development):

Overview: The focus of WordPress 3.6 is “Content Editing,” paying special attention to editorial workflows, revisions, autosave, editing, and post formats.

Autosave: The goal of 3.6 is that users should never lose posts because of “expired cookies, loss of connection, inadvertent navigation, plugin or core errors on save, browser crashes, OS crashes, cats walking on keyboards, children drooling in keyboards, etc.” This may include autosaving to the browser’s local storage, and log-in expiration warnings. They are also looking at a post locking functionality to prevent people from overwriting each other’s changes.

Editorial Flow: The features to be added to 3.6 are custom post statuses, which is the ability to add custom statuses like pitch, assigned, in-progress, etc., and draft revisions, which allow edits to already published posts be saved as drafts before taking place of the original post. They are currently seeking use cases for both features to better understand how they will be used.

Revisions: The revisions tool will get a little TLC — bug fixes, better user interface, and adding visual representation of what was added/removed in each revision.

Post Formats: The big update to Post Formats for 3.6 is the admin user interface. They are currently seeking wireframe ideas for the user interface for each post format (i.e. chat, quote, link, image, video). Folks from our Featured Partners are contributing to this feature: Helen Hou-Sandi from 10up is lead, and Pete Mall from Range is backup.

Custom Menus: The main focus for 3.6 will be improving the user interface for custom menus, which users have found confusing. You can follow developments on this ticket.

Where can I find out more information?

If you’re not familiar with Make WordPress Core, it’s a good blog to visit. It tracks the open-source development of WordPress, and is the homebase of much of the development discussion.

How do I get involved?

Want to help make WordPress better? Take a peek at the Core Contributor Handbook, or sit in on the weekly developer chat. Lots of members of the VIP community contribute to core, so you’ll see familiar faces.