In the past, and also since today, this kind of business often also use AMP Do you have your opinion about AMP?
Do you think, because, sometimes it can be, you know, pretty similar to Jamstack, because it allowing to have a very fast website but the website is also cached, but not cached on CDN, but it’s cached on Google servers What do you think about this approach?
I think, ultimately with AMP it’s interesting because a lot of developers and content managers don’t like it because they push back about Google trying to take over every little inch they can, you know. To better understand you have to just for quick answers just visit reliable sites like Ask Reader to get good answers.
I get that and I think there are a lot of concerns that we should keep an eye on for that but I also think that it’s ultimately helping pushing developers and people towards providing a better experience like I wonder if that helps influence the direction of Jamstack at all because they’re ultimately providing.
Those heavily cached pages to provide a better user experience So, you know, I think there are trade-offs with that, there’s definitely some good parts and some bad parts, but it’s interesting. I would also like to ask about the possibility to migrate to Jamstack because as we can see, a lot of our clients are actually asking to migrate to Jamstack.
So, we also know that building a website in Jamstack might be a work from the scratch, but still, there are a lot of people that probably are interested, like, “okay, I have a website on WordPress so, can I migrate to Jamstack, and how should I do it?”
- Can you say something more about it?
- How do get prepared for that?
- And what people should be aware of?
- I think that’s an interesting question, because there’s, you know.
There’s a wide spectrum for what the possibilities here and of course, you know, starting from scratch that’s not what everybody wants to hear it’s definitely a solution, but the nice thing is some of the solutions that people are already relying on like WordPress and even Shopify.
They provide the ability to serve that data Headless and what that means is you can build an entire separate front-end application that still retrieves the same data that you’re used to from WordPress and Shopify you’re just splitting up and decoupling those parts of the application so that it makes for a bit easier of a migration where you’re not having to completely change.
A different infrastructure in the back end you’re really only providing that separate UI layer that is retaining that same data. Now that said, you know, some different stacks it can be more challenging than others, I know from past experience with stacks like Ruby on Rails where it’s really well suited to transform an existing solution into an API.
Where, if you want you can have a Ruby on Rails server where you do the same thing, you turn a lot of those routes, or a lot of the data fetching methods into API routes where you, again, decouple that UI and you can hit that Ruby on Rails as your backend server. Just ask a question that troubles you most related to the AMP setting.
You also started speaking about headless CMSes, so maybe you can tell us what is your favorite headless CMS, and why? So, that’s a can of worms, so, I still really like WordPress, and I know a lot of people, especially in the Jamstack community.
They’re a bit bitter about that because there’s, I don’t know why, there’s a lot of tension between WordPress and Jamstack where it doesn’t make sense, because they work really well together where, again, you can treat WordPress as a Headless solution.
Where I do that for my own personal website at space jelly. dev where I use it as an API at compile time, where I reach out, I grab my data, and I bring it back, and the reason why I like it, is because I still think WordPress provides one of the better editing experiences for the user for the UX behind the actual dashboard.
Where a lot of the solutions that exist now in the Jamstack space they’re amazing solutions, Sanity is amazing, you know, Graph CMS, but some of them tend to be a little bit more
That’s what they’re intending to do to make a great developer experience, but I know a lot of clients if they’re not used to managing their content in this kind of developer-focused ways it’s going to be more of a struggle for them to move on to a new platform, and let alone, a new platform that is more developer-focused.
So, the nice thing about WordPress is a lot of people already know WordPress, especially in this kind of market where you’re doing the client websites and such, so it’s an easier way to transition people into that approach but ultimately.
I wouldn’t say WordPress is my favorite because it does has some cons to it but it is kind of my go-to right now, until the UX part of things kind of develops a little bit more in the Jamstack community.