14 Comments

  1. Rhys C

    You all are killing it! Keep up the great work @ Zac Gordon, Jason Bahl, Rich Tabor, Muhammad Muhsin, Alexandra Spalato

    Report

  2. Anh Tran

    This is a great news! Gatsby is very interesting and I’m planning to discover more about it.

    Report

  3. Hashim Warren

    Gatsby has a long way to go to have a publishing experience that rivals all-in-one WordPress.

    Try previewing your content. Or make a quick edit after it’s published. Or add a form to a page.

    The workflow is dev friendly but hostile to content creators

    Report

    • Kellen Mace

      These are important points to consider, for sure. Some thoughts –

      Fast Builds:
      From what I’ve heard, the Gatsby team is working on supporting incremental builds in the future, so that when changes are made, only the static pages of the site that were affected would be regenerated. So that would make builds lightning fast. You’d be able to tell content creators: “After you update a post/page, you’ll be able to reload that page on the frontend and see your changes reflected there within seconds.”

      Previewing Changes:
      The Postlight Headless WordPress + React Starter Kit project has a way to view draft posts from the decoupled frontend React app. Here’s the code: https://github.com/postlight/headless-wp-starter/blob/master/frontend/pages/preview.js. I bet that could be adapted for Gatsby so that when a logged-in user visits a certain endpoint on the static site, the React app fetches the data for that draft post from the WordPress backend and displays it in exactly the same way it would display a published post. Sounds like setting that up could be a fun project! :)

      Adding Forms:
      Adding a form to a page can be done, as long as you use the WP REST API, WPGraphQL, or some other means to send the submitted form field values back to the server to be stored.

      So in summary, I agree that these things are harder to implement with Gatsby than what you get out of the box with a traditional, monolithic WP site, but I think they’ll get easier. And depending on the site, dealing with them may be worth it for the speed gains and other features that Gatsby brings to the table.

      Report

    • Miriam Schwab

      The idea of merging the world of static site generators and WordPress is appealing on many levels, and this development is refreshing. However, what you described are serious limitations, and also a huge amount of plugins would be incompatible with this approach.

      That’s why we created Strattic: it allows you to use WordPress as usual, no change in behavior, and we’re not tossing PHP out the door. But the production site on the live domain is generated as a static site so you also get all the benefits of a fast, very secure static site. (Plus a CDN, plus SSL for all, and more.)

      In any case, all these efforts contribute to bringing WP more in line with modern web development approaches, and it’s great. Looking forward to seeing where this project goes!

      Report

  4. Sallie Goetsch (rhymes with 'sketch') (@salliegoetsch)

    For some of us, React is still a deterrent rather than a selling point. Still, it’s interesting to see.

    Report

  5. Bastian

    it lets them throw away the entire old school PHP based WordPress theming system

    I don’t understand this constant bashing of PHP as of late. WordPress is where it is thanks to the ease of PHP.

    Report

    • Kevin Provance

      Because – I guess – React is all the rage now? Which it isn’t. It’s the new, popular, shiny thing that has people Oooing and ahhing. More FB assimilation as far as I’m concerned.

      Y’all will remember how well. NET did, right? 😉

      Report

    • Jason

      This isn’t bashing PHP in any way. The source, WPGraphQL is built on PHP and empowers the WordPress server in great ways.

      This is decoupling concerns though. Letting the WordPress server do server things and letting a new stack of theme rendering do theme rendering things.

      It’s not a move _away_ from WordPress, but a marriage between WordPress and a new stack.

      Partly because, as Kevin said, it’s new and shiny, but also because it solves some real problems (speed/security) and improves (arguably) the developer experience.

      Report

  6. Json

    OK.

    But what if i create booking forms or other non-static content?
    This means finding new ways to generate the data back in WP.

    That makes no sense at all.

    First we had html and

    Then dynamic languages. PHP, Javascript …

    Then CMS – in this case WordPress. With a bit of caching and code optimization, a WP page can be very fast.

    Yeah and today?
    html, javascript (unlimited frameworks), css (unlimited frameworks), node.js, webpack, graphql, CLI without end, etc.

    What do we do with it?
    We first build a WordPress page and then we pack the whole thing again in a framework to Gatsby and then pack Markdown again.

    Unfortunately that makes no sense at some point.

    To build a simple landing page you need html and css.
    Not more. Hardly anyone can still build a website with these simple tools today.

    It’s crazy what Web development comes up with to find fewer and fewer solutions that are simple.

    Report

  7. Martin Forgenie

    I speed-tested their main website as well as their showcase sites. The showcase sites appear rather slow compared to many wordpress websites. Their own site is extremely fast although it does seem to be slow on all the speed tests.

    Report

  8. Russell Heimlich

    I’m sure this is scratching a technical itch and more Gatsby themes sound great. But if you want a screaming fast WordPress site you could use a full page caching solution and be done.

    Report

Comments are closed.

%d bloggers like this: