WordPress 2.7 Feature Preview: Publish Module (UPDATED)

I made a screencast showing off the new Publish Module that I’ve been working on for WordPress 2.7 (due in November).

It is different from the current (2.6) Publish Module in look, form, and function.  It elegantly adapts to your actions, and presents you with clear choices. You’ll never again wonder what will happen when you hit that button and send your post off into the ether.  I hope you like it!

If you’d like to try this out for yourself, WordPress 2.7-beta-1 is available now.

Update:

I’ve slightly rearranged the Publish Module due to some issues with translations and wide buttons. The result isn’t functionally different, just more structurally flexible. Check it out:

59 thoughts on “WordPress 2.7 Feature Preview: Publish Module (UPDATED)

  1. Hi,

    i am using 2.7-beta and i really really love it.. you are doing a great work with this new publish module. Thank you very very much for all the time you spend for it and for improving wordpress overall.

    Chris

  2. The main issue for me ist: Why i always need to scroll and scroll and scroll to access functions added by extensions to the writing site?

  3. The “Save Pending” could be a little confusing. It might be good to change it to say “Save as Pending.” Otherwise, I might think that the save on something is pending.

  4. this is the right way to use ajax, seems a desktop application!

    Actually, none of the Publish Module is using AJAX… it’s just local JS. We have all the data we need when first loading the page, so there’s no need to hit the server again. (Autosave, of course, uses AJAX.)

    The main issue for me ist: Why i always need to scroll and scroll and scroll to access functions added by extensions to the writing site?

    In WordPress 2.7, you’ll be able to reorder all the modules on the Add/Edit Post screen. That includes custom modules added by plugins! What’s more, it’ll remember where you put them, even if you’re using a different computer.

    The “Save Pending” could be a little confusing. It might be good to change it to say “Save as Pending.” Otherwise, I might think that the save on something is pending.

    That’s a good point, and I’ll take it under advisement.

  5. Mark, are you making screencasts at 4:40 in the morning? I take it you were up all night for this one…

    I’ve been putting in a lot of very late nights on 2.7, and I’m not the only one!

  6. Looks great – I’ve asked many of the questions about the current publishing module that you outlined at the beginning of the screencast, so I’ll be happy to use the new writing interface.

    Just a note from a user experience point of view – when I change the status from draft to pending, then open the module again and click cancel, why does it change back to pending? To me, cancel simply means to close that component, not switch it back to draft. If I want to switch back to draft, I’d expect to need to change the drop-down to draft, then click save. Otherwise, after opening the status component, you need to perform two mouse-actions to keep the current state, which seems silly.

  7. flick says:

    Looks great! A very thorough explanation too; have to admit the fact that one could achieve something from two different methods in WP had never occurred to me before (just did it intuitively I guess) but I can now see how it can be confusing for others. Very exciting to see the new interface in action incorporating a lot of the great plugins (such as Manageable) and the prospect of custom modules ‘remembering’ their position. A+++!

    p/s: Thanks for the screencast! I’ve tried creating one before and in my experience it’s a lot of work, so thanks for creating this demonstration.

  8. To me, cancel simply means to close that component, not switch it back to draft. If I want to switch back to draft, I’d expect to need to change the drop-down to draft, then click save.

    The way it works, “cancel” means cancel any unsaved status changes. I can see how it could be confusing, because “OK” doesn’t save the current changes.

    In any case, this is one area we wanted to address, but couldn’t quite settle on a new approach. We may revisit that in 2.8. The good news is that the status dropdown is only used for rare status transitions, so unless you unpublish a lot of posts or voluntarily submit posts for review, you’re not really going to use it.

    p/s: Thanks for the screencast! I’ve tried creating one before and in my experience it’s a lot of work, so thanks for creating this demonstration.

    I created it in about an hour, using a fabulous application called ScreenFlow (Mac OS X). I literally bought it 10 minutes before recording this screencast. Awesome app. For Windows users, I hear Camtasia Studio is a good choice.

  9. davidrpotter says:

    Looks great!

    One thing that struck me while watching the video was when setting the publish date in the past after it was set in the future and the major action button changes to Publish was that it seemed like a Save Draft button should have shown up. I would have thought that anytime the Publish button is displayed that a Save Draft or Save Pending button should also be shown. Make sense? Something to think about.

    Thanks,
    David

  10. Tyler says:

    This looks very promising, and I’m really glad you put so much thought and work into usability issues.

    I was one of those users who was not happy with *some* of the changes made in the 2.5 admin panel, so I’m very happy see a major developer like you put so much time into making a important feature non-ambiguous, easy-to-use, and highly functional.

    This seems very well-thought out and beautifully designed.

    Thanks for all your hard work — looking forward to using it!

  11. One thing that struck me while watching the video was when setting the publish date in the past after it was set in the future and the major action button changes to Publish was that it seemed like a Save Draft button should have shown up. I would have thought that anytime the Publish button is displayed that a Save Draft or Save Pending button should also be shown. Make sense? Something to think about.

    I considered it. I have some ideas in the works for 2.8 that may eliminate the status dropdown altogether, so I may revisit that after 2.7.

  12. Hi Mark -

    First, I want to say thanks for all the hard work that you and the rest of the WP team have put in. I’m really enjoying the 2.7 admin interface, but I’ve encountered some display issues in Firefox 2.0.0.17:

    1. Rounded buttons: A lot of the rounded buttons are not displaying properly in the normal state. The background image is showing past the rounded corners (i.e., any buttons with the blue background like Publish, Save Changes, etc.; the gray Add New Post button at the top with the dropdown; and the off-white buttons that appear through the admin section). In the hover state, the blue buttons display properly, but the others still show the background image extending past the rounded corners.

    Also, the text should probably be centered in the Publish button – in FF 2.0.0.17, it is shifted to the left.

    2. Admin menu: If the active section is at the top of the menu grouping, when active, the background image is showing past the rounded corners (i.e., Dashboard, Posts, and Appearance).

    I’ve upgraded to the 2.7-Beta2 version this AM, and these issues persist.

    Question: Do we really need the 2nd toggle menu arrow between the 2nd and 3rd menu groups? I think that the first one under the Dashboard link would be sufficient. Even with all of the submenus open in the 2nd menu group, the first arrow is still visible at the top of the screen.

  13. I agree with Charlie in that the “Cancel” Link shouldn’t actually revert the state back to “Publish Immediately.” When you click “Edit” it slides open an area to make changes. Clicking cancel is a common user interface action to dismiss the area you just opened. Think of a dialog box that pops up. You click “OK” to accept changes or “Cancel” to close the dialog box and not make any changes.

    I suggest a third button that’s called either “Undo” or “Revert”. The “Cancel” button would just cancel your intention to make a change. “Undo” would set the status back to “Publish Immediately” and “Ok” would accept any new changes you made.

    While watching the screencast this issue jumped out to me right away. It was something I didn’t expect and I’m sure other users won’t get it either.

    Otherwise, everything else is ACE! I love the animated controls. I can’t wait for the 2.7 release!

  14. Great work.

    However, I use the Save As Pending to shift finished posts (ready to publish at a later date) to a separate place and this function now adds extra clicks to it. Is it too much to ask for all the functionality to be made visible as major buttons? Make sense? I mean to say that as well as the Save Draft button there could also be a Save Pending button so that we don’t have to navigate pull down menus.

    Thanks

  15. Edisrelisdink says:

    uqurcxespeuhftgnwell, hi admin adn people nice forum indeed. how’s life? hope it’s introduce branch ;)

Comments are closed.