WordPress is evolving and you should care

Do you know WordPress, this tool that powers 27% of the web? This big old CMS everyone loves to hate because It’s oldish, it’s PHP and it’s not an SPA? but in the same time, everyone uses because it’s so great at achieving the goal it’s designed for: creating content? Well! It’s time to stop criticizing and take a look at what’s happening in the WordPress community and what we’ll get for the next iteration of our beloved CMS?

Disclaimer: I work for Automattic, the company behind WordPress.com and highly engaged in the WordPress community. I also work on one the next WP editor project.

Revolution or evolution?

WordPress is currently powering 27% of the web, but at the same time, the web is evolving. Mobile is taking over the desktop, richer UIs require more client-side interaction and less server-side rendering, new compelling competitors arrived in the CMS market which promise simpler UI to create richer content. If WordPress wants to stay the 1st choice and continue growing, it has to address these issues and that’s exactly what we’re trying to do.

In the last WordPress US, Matt Mullenweg declared that the main focuses for the next WordPress releases would be:

  • The REST API.
  • Evolving the WordPress Editor into a block-based editor.
  • Leveraging the blocks to simplify the customization (site building)

Any progress?


The WP REST API has already been merged into WordPress in 4.7. It’s not just another feature, it’s a big shift in the WordPress philosophy. This already enables new ways to interact with your WordPress content. Think “Headless CMS”, “SPA Themes”, “Mobile applications”. Also, parts of the WP Admin are being rewritten to leverage the API. Exciting times, slowly, WP admin is shifting to an SPA!!!

The Editor

Have you ever tried these compelling editors allowing you to insert blocks and move them around like LEGO bricks to build your post’s content? That’s exactly what the new WordPress editor would be like. And in fact, you can already try it as a plugin. It’s far from ready but you’ll get a sense its UI.

If you’re interested, you can follow the progress in the Gutenberg GitHub repository. And on the weekly Slack meetings on the #core-editor channel.

And you know what? It’s built using React, Redux, and modern JavaScript. Yep, true story, WordPress is embracing modern Javascript Development a and React.

These technical choices are not set in stone yet, this is still being discussed on the weekly #core-js meetings but yeah, WordPress is being modernised!!!

Stop hating WordPress, you’re using it every day, it’s time to get involved!!!


5 responses to “WordPress is evolving and you should care”

  1. Bonjour Riad
    A la fin de cette article vous parlez du choix de react redux pour gutenberg et
    j’ai justement une question à vous poser concernant le transfert de donnée dans gutenberg.
    J’ai créer une component List qui liste les icônes fontawesome pour “m’amuser” avec gutenberg.
    Une fois que l’on clique sur l’une de ces icônes j’obtiens le nom de l’icône cliqué que je mets dans letter mais le problème c’est comment récupérer cette letter dans mon block.js pour pouvoir l’utiliser dans un bouton par exemple.
    J’ai créer un petit fichier avec le code ici :https://gist.github.com/michellomp/54734c16b8f946729c2ee814107deb93
    J’imagine que vous devez être très occupé avec l’équipe de wordpress mais si vous aviez un peu de temps pour me répondre, je vous en serez très reconnaissant.

    • Bonjour,

      Tu n’a pas besoin d’utiliser Redux pour utiliser ça, il suffit just d’utiliser une prop `onChange` pour récupérer l’icone lorsqu’elle change dans ton block. Dans ton code, je crois qu’il faut modifier les appels à “this.handleClick” par “this.props.onClick”

  2. Hi Riad I’ve got one question about javascript and gutenberg. How do you use javascript script in the save function ?
    like this : save: function( props ) {
    return (

    • You can’t, save is used only to return the markup to be saved. If you want to run JavaScript in the frontend, you’ll have to embed your script in the frontend like you’d do today (without Gutenberg).

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: