1. David Shanske

    I have an out of the box solution for REST API authentication I worked on with others, the WordPress IndieAuth plugin. I agree that integrated options not being there is a problem. But there are a few maintained solutions.


  2. Shash

    Hey just wanted to say I’m in a similar huddle regarding the rest API. For authentication via JWT, I came across this plugin which can do logins via JWT tokens.

    I also rolled a review for it on wpplugincheck too. I’m using it for production atm if anyone isn’t feeling confident on using it.

    For the time being, I feel like the rest api is lacking in a lot of areas, especially documentation and lack of good examples. I’m exploring using airtable via airpress as an alternative.


  3. Kishore

    We are have done a application where we are doing through WordPress OAuth 2.0 Server to connect to our SASS app WPdrift. But JWT also we have used in past.


  4. Anh Tran

    The name “Just Write” catches me as we have a WordPress theme called Justread!

    Anyway, I love the minimalist design of the app. How does it work with Gutenberg (when it comes)?


  5. Marc

    “As the WordPress admin continues to grow and become more complex, some people get excited and others moan and grown,”

    *groan :)


  6. Unai

    Great article Sarah. It perfectly represents the state of WordPress right now. I saw a really bright future for WP when they launched the WP Rest API but all that kinda deflated right at the end. The Rest API stayed kind of stagnant while they decided to double down back on the very thing the Rest API seemed to be trying to move WordPress away from: becoming a simple Visual Composer CMS and a Squarespace competitor, instead of a CMS/App-framework for everyone.

    Sadly, I don’t think there’s any coming back now, so I hope some other project takes over and fills that hole. I’m quite interested in headless CMSs, which seem to be getting a lot of traction, but none of them have less than a long way to get where WordPress is in term of features, let alone community support.

    We’ll see how we manage content in the years to come, but seems like, for the more tech inclined, WordPress won’t be there, at least not so much as it’s been all those years. We’ll also see if that means a movement in the dev community too, since they are the ones most interested in the API way of doing things, and not so much in the Squarespace one. If that’s the case, maybe Matt Mullenweg should learn a thing or two from Steve Ballmer: Developers! Developers! Developers! :D


    • Jason

      Funny you should mention that. Check out what I just started building after Just Write … https://github.com/themeblvd/backroad


      • Unai

        Nice! I think it is a great moment to start a headless CMS project. Although I personally prefer php-based systems over Node.js ones, so shared hosting users don’t get cut out. But nice project anyway, good luck with it! (:


    • Kishore
    • Leonardo Losoviz

      You can also check the project I’m building: https://getpop.org (sorry for the self-promotion!). It basically wraps WordPress in a way that allows it to behave like a headless CMS. The installation scripts are not ready yet (I need a few months more of work), but the concept works like a charm, allowing to do absolutely everything that you can already do in WordPress (including authentication) through standard HTTP requests, and getting a JSON response back (it is not REST though). And it’s pure PHP, Handlebars and vanilla Javascript, so other than Handlebars (just for markup, and very easy to use), it’s pretty much the same technology stack as WP (the open source repo is at https://github.com/leoloso/PoP). Just check it out, I hope you like it :)


    • Jeff Chandler

      It should be noted that Gutenberg heavily utilizes the REST API in WordPress and when work began on the new editor, the team discovered a lot of things lacking in the API. Over time, they’ve made a number of improvements to the API alongside Gutenberg and it seems like a lot of people believe that the API has simply been ignored which isn’t the case.


  7. Piotr

    The biggest problem is speed namely lack of it and it can’t be fixed so easily.


  8. Rob McClellan

    In all honesty, a writing interface like this is what I expected out of Gutenberg.


Comments are closed.

%d bloggers like this: