Editors note from Chris:
I love the idea of this concept, but this article was 100% tied to a particular CMS that ended up sending me some gross spammy emails that I’m entirely uncool with. So I’m nuking the article.
Vue is great. Serverless is awesome. Headless CMS’s are cool. Serverless is awesome. There are lots of tutorials out there to follow down this road.
Doesn’t the butter CMS have to have a node server behind it? Wouldn’t that mean its running on a server? Or is it just the fact that the traffic hitting the front end doesn’t need to talk to the backend that makes this good?
People hear “serverless” and think “oh lightweight no-sql app I can install in me server” nope, more like renting access to remote database and disk and hoping there is an endpoint for what you need
Great question – ButterCMS is a 3rd party service that provides a content API. Butter is not something you download and install / maintain yourself. You simply query that content API directly from your Vue.js app, there’s no CMS software for you to worry about or host. Hence “Serverless” CMS, as in you don’t need to worry about a server to get CMS capability.
What about links in the content of blog post linking to another page – would this app be able to route those?
Yeah, assuming the page has a unique absolute URL, linking should work fine.