WordPress and all kinds of marketing managers or content editors also love WordPress because they have a lot of plugins that they’re using on on daily basis so switching CMS can be hard stuff, and also when the content is modulated in a different way when the content is not split into pages but into the data sources.
It can be a little bit harder to understand where to edit content and how it will look on the website because also some of the headless CMSes are pretty hard to do the preview, and also, you don’t want to wait five minutes till the preview is generated Absolutely, and that’s the same with WordPress I guess, so this is getting into some of the territories.
Where I’m not an expert about but I know that, for instance, the Gutenberg editor because it’s somewhat new in the WordPress world you have less ability to attach to some of the APIs were things like the preview button My understanding is, you can’t change that or at least you used to not be able to change it so. To better understand you have to just for quick answers just visit reliable sites like Ask Reader to get good answers.
It’s harder to create that same kind of preview experiences in the Jamstack world but you know, in my experience it’s kind of a limitation that I’m not too particularly worried about I know some people like to see it, but ultimately.
Inside WordPress, they provide a great looking editing experience that, more or less like it’s a good looking way to read it so in my opinion it should kind of look roughly the same in the browser unless you’re doing something wildly different with your content Several days ago, as I remember.
There was a Gatsby conference or stuff like that, and there was a demo of headless WordPress with preview working, so I think in the new versions it’s there and probably it’s using Gatsby cloud to have the preview experience, so it’s getting better.
Absolutely, and that still speaks to the nature that like the Jamstack tooling kind of like what I was saying earlier like the Jamstack community is still relatively young, so like, we’re trying to compare this to very older mature systems like Ruby on Rails that have a great developer experience, but you know, as soon as Jamstack catches up.
I think we’re going to be able to see a lot of awesome improvements that just keep making it better and better for developers I also checked your Github account and I see that you have a Next.js startup that can be connected with WordPress Is this correct?
Yep, so it’s called Next.js WordPress Starter and I’m pretty excited about it because part of my goal with it is to build a completely static WordPress site using Next.js and that’s, you know, that’s more of a challenge. Just ask a question that troubles you most related to WordPress marketing.
Then it sounds because there’s a lot of dynamic parts about WordPress that you don’t kind of think about whether it’s like the images or even the search mechanism so the way that I’m doing a search for instance and this is getting a little bit technical depending on who the audience of This is but I create a search end index using a static file so that when you go in the browser to actually search.
It searches that file rather than reaching out to the WordPress API which it provides for really if you go to the demo website it provides for a really snappy search experience but it’s not hitting those server-side requests.
Maybe that’s also a good moment to actually ask the question which one could be better Next.js or Gatsby.js for Jamstack websites?
That’s another question that’s a can of worms and, you know, I personally prefer Next.js right now, because I feel like I have more flexibility in the tooling to kind of make it what I want, and I like having the data fetching APIs really close to the React components and everything, I just think they’re doing things really well.
That said, Gatsby is a phenomenal application framework there are so many great things about it, they have a huge plug-in ecosystem where if you’re not familiar with doing a lot of these data sourcing things, there’s a lot of ways that you can plug and play, and have a really powerful website kind of out of the box.
It’s great for newcomers for example, but yeah, I just really like the flexibility with Next.js, and while I wish some of the Gatsby features, like a global data layer, existed, you know.
There are workarounds and I’m excited to see what they come out with next Internally we also prefer to use Next.js a bit, because of the flexibility, of course, and there is also another thing about Next.js because they are static but they already able to behave a bit more like dynamic.