THE WORDPRESS NEWS CORE
FEATURING WORDPRESS COMMUNITY EXPERTS AND THE WP DAILY ARCHIVES

Rethinking the WordPress Editor

Over the past couple of weeks there have been a couple of feature tweaks and improvements in the mix for WordPress’s content creation experience.

First, the UI team is making some headway on a functional front-end editor which allows users to create new posts, upload media, and change metadata—all from the front-end. It’s being designed from the ground up to provide a great UX and a barebones UI. A user will be able to use WYSIWYG tools in the admin bar and modal windows for creating galleries and adding custom fields, all without having to move to the back-end. You’ll also be able to add new posts from the front-end. This means that for content creators, editors, and authors—the back-end admin panel will become increasingly less important.

modular_2

Next up, TinyMCE 4.0 is being rolled into core. As far as aesthetics, this doesn’t mean much except a bit of a cleaner look. But it also gives the team a more quality API to hook into, a better file structure and a more maintainable codebase overall. For now, there is a plugin which patches old 3.0 API hooks for backwards compatibility too. In general though, this means TinyMCE will be even easier to build on top of and hook into.

So where is all of this heading? Over the past year or so, I’ve seen the various WordPress make teams become more unified in their development. Things seem to be merging together and the result has been a much better WordPress. Overall, the UI has been noticeably better, especially in terms of the look and feel. Still, major steps forward have mostly happened on the back-end. I’m sensing more changes coming to the front-end soon.

Last week, Christopher Butler posted an article provocatively titled The way you design web content is about to change. Butler was referring to his own, non-licensable CMS that Newfangled uses, but the idea was fairly simple. Modular content blocks, each designed independently of the overall layout of the site. So, as a designer and developer, you design and code up a slider, a media block, a text block, two-column block, etc. Then, content authors can arrange these blocks together however they want, creating both simple and complex layouts all from the same modular blocks. The idea is to move away from the concept of layouts, and start designing from the content out.

From Christopher Butler's Post

From Christopher Butler’s Post

At the end of the article, Butler mentions that there are a couple of ways to get this done in a CMS like WordPress with plugins such as Advanced Custom Fields. But I would venture to guess that WordPress core is moving this way too.

Right now, the platform is focused on building a richer and secure back-end so that it can be used to create applications. But when the focus turns back towards the front-end and the admin experience for average users, I think that modular content will become a strong move forward. It’s been discussed before in the community, and I think that the UI/Core team has even explored it. Functionality like content blocks may not be that far off. And if we can move the structuring of these blocks to the front-end they will be even more powerful. That way the back-end can be just that, for administrators and developers to tweak global options. Users will be able to visit their site, fit together a series of blocks with videos, sliders and more, and create whatever layout they wish. Oh, and that’s all without going to /wp-admin. And because each block is designed to be modular, no author will move outside the design and thematic parameters of their site. At least, that’s where I hope it’s moving.

Of course this is all hearsay, just one man’s opinion. But when I see changes like the recent updates to core, I remain hopeful that this is the direction WordPress could take. As a site builder, WordPress is extremely powerful, especially with the right tools and plugins. But for a designer, it can be frustrating to set-up structured blocks for clients to follow. WordPress has a chance to pave the way to a better experience overall.

The old WYSIWYG method of editing is coming to a close, but WordPress has the ability to adapt. For now, just enjoy the new benefits of TinyMCE 4.0 and look forward to a full-blown Front-end editor coming to core, but let’s keep our eye focused on the future. This is just the beginning of the discussion, I’m interested to hear what you, the community, think of any idea like this.

Please share your thoughts with us in the comments section below! 


jayhoffmann_photoJay Hoffmann is a WordPress developer hailing from NYC. In the strictest sense of the word, he is a WordPress enthusiast with an eye for front-end development and design. He has been working with WordPress since 2006 and currently works for a popular children’s media company. This year, Jay started Tidy Repo, a curated list of the best and most reliable plugins from around the web. You can also follow Jay on Twitter.
  • callmeisaac

    LOL, just fry up a few CPTs and mix them with Display Posts Shortcode
    http://www.billerickson.net/shortcode-to-display-posts/

    One CPT is for the content and the other for the blocks.

    • Jay Hoffmann

      Yea, I know that it’s more then possible to get this system up and running, but I think the value would be if it could get rolled into core, and if editing could happen on the front-end.

      • callmeisaac

        I came upon this solution for connecting blocks to content, but I use P2P to link CPTs abstractly for example connecting CSS and JS to different pieces of content.

        CSS and JS needs to become unhinged from plugins and it is easy to enqueue a CPT as JS and CSS.

    • http://www.sennza.com.au Lachlan

      Shortcodes are a solution for developers to achieve the above, but I feel like these a horrible experience for the end user. Not something I would ever ask a client to learn/manage. I think the content block concept would be a great step forward for WordPress

  • http://www.sennza.com.au Lachlan

    Thanks for the article Jay, I read Christopher Butler’s post last week and thought it was great. The more people that help promote this concept for WordPress, the greater the chance of it getting into core.

  • Tracey Rickard

    These are exciting times ahead for WordPress designers, front end editing alone is going to solve so many challenges. It will be interesting to see how this progresses with modular layouts.

    • Jamie Oastler

      I agree. Check out easel.io (a Bootstrap mockup tool) for a great example of the direction that the front-end editor could go to handle modular layouts. I’ve been using it of late with http://320press.com/wpbs/ to quickly build the markup / css and then pull that back into theme templates with the dynamic content from WP. Would love to see the front-end editor grow in that direction and support for meta boxes (like ACF) along with custom fields.

      WordPress already has the best content editing experience in my mind. But the overlap in potential awesomeness to transform WP even further between front-end editing, metamorphasis and content block “feature as plugin” pieces is huge!

      • Jay Hoffmann

        Awesome resource Jamie, thanks for sharing. Ideally we can fuse the kind of experience you get creating a layout with a tool like easel with actual content creation.

  • http://www.donnafontenot.com/ Donna D. Fontenot

    I like the idea of blocks, but what happens when a designer makes a block that is designed to be say, 600px wide, and the user wants to place it in a 200px sidebar? If they resize nicely, fine, but if not, it could just be another pain for the user (and whoever has to support the user).

    • Jay Hoffmann

      I think in order for this to work, designs have to be done in a modular, responsive way. That means all blocks are designed to fit the width of their container. It’s a bit tricky, but it’s closer to how things are build these days anyway.

TOP