Jetpack 3.5 Introduces Menu Management on WordPress.com

Jetpack 3.5 was released today, coinciding with WordPress 4.2. This release expands the capabilities of Jetpack’s centralized site management to include menus. If you have Jetpack Manage activated, you can now log into WordPress.com to manage menus for any of your sites that have opted in.

menu-management

The benefit of going to WordPress.com to manage menus for self-hosted sites was not immediately evident for those who don’t make use of the centralized site management feature. The interface is different and the dashboard contains a limited set of site management controls.

For those who manage just one or two sites, it isn’t clear why you would opt to log into WordPress.com instead of your site’s admin panel, which is essentially the command center, where everything is at your disposal.

Jetpack representative Jeremy Herve explained that the primary benefits of the menu management feature are applicable “when working on multiple sites, when on mobile, and when you don’t want to log into the self-hosted site.

“I must also admit than I’m not the biggest fan of the Menus interface in WordPress.org,” he said. “It’s confusing for new users.”

If you prefer WordPress.com’s menu manager and posting interface but want to retain the freedom of self-hosting your site, then Jetpack Manage may be a good fit for you. If the disconnected, dissimilar interfaces don’t make sense for managing your sites, then there’s no need to activate it. Currently, bulk plugin management across multiple sites seems to be the most popular use of Jetpack Manage.

The 3.5 release also includes a dozen bug fixes and a few small enhancements. View Jetpack’s changelog for details.

Would you like to write for WP Tavern? We are always accepting guest posts from the community and are looking for new contributors. Get in touch with us and let's discuss your ideas.

8 Comments


  1. I can’t see the point to this. Maybe they’re something bigger up their sleeves. Dunno.

    Report


  2. I agree that it might seem strange and unintuitive to manage a self-hosted site’s menus from WordPress.com’s central management interface. But only if you look at this feature in isolation.

    When you consider that they’re gradually adding more and more functionality that can be managed centrally, this is just another step toward whole-site management for self-hosted sites from WordPress.com’s interface.

    Perhaps there could have been a more intuitive next step instead, but perhaps not. I doubt it was done without any thought :)

    Report


    1. I have no doubt they have plenty more up their sleeves. I just don’t think the user experience makes a whole lot of sense at this point. In a year we’ll probably see a different picture.

      Report


  3. Yeah, I don’t get this one either. But to be fair, I don’t get a lot of the wp.com interfaces. I dislike using wp.com, overall. Too different and overly simplified. Don’t get me wrong, simple is good, but there are limits.

    Report


    1. I felt the same way for a while, but the posting interface through WordPress.com has totally grown on me, to the point where going through /wp-admin now feels like the old, clunky, slow way.

      Obviously, menu management isn’t something that most people interact with nearly as much as posting, but I’ve come to see /wp-admin as something that I *have* to log into in order to do certain things with my site, and this just takes another item off that list of reasons why I have to log in to my /wp-admin.

      Report


  4. I don’t use Jetpack, but I have to come in to say the picture you chose for this post is very cool!

    Report


  5. Perhaps this is a step closer to having your entire backend being available in WordPress.com

    Report

Comments are closed.