JAMstack vs. WordPress: Which Is the Future of Web Architecture?
1–5 of 5 posts
Re: JAMstack vs. WordPress: Which Is the Future of Web Architecture?
#2JAMStack seems to become more and more one of these terms without a clear definition:
> “From my perspective,” he said, “[it’s] a JAMstack website if it uses one of those modern components — like maybe it uses Hugo as a static site generator, [or] maybe it uses Contentful to manage the content, or maybe it uses Netlify to get deployed.”
At least to me, that reads a lot more open than what I got from the initial proposals of the term. Apparently a Github Pages blog is "JAMStack" now...
Re: JAMstack vs. WordPress: Which Is the Future of Web Architecture?
#3Wordpress exists solely because it makes exhuberant amount of money for fanboys. These fanboys are stealing money from their clients by charging massive sums to customise either free or very cheap themes/plugins they purchase from places like Themeforest.
Without those fanboys stealing or otherwise ripping their clients off by giving them a sub par, slow and mostly insecure product that's most likely not fit for the job its intended then it would not have so much dominance.
Wordpress is built by idiots for idiots, this is as true now as the day it was famously coined.
JAMStak may or may not be the future but the Wordpress model employed by so many self proclaimed web developers cannot sustain as people wake up to being stolen from.
Re: JAMstack vs. WordPress: Which Is the Future of Web Architecture?
#4JAMStack seems to become more and more one of these terms without a clear definition: > “From my perspective,” he said, “[it’s] a JAMstack website if it uses one of those modern components — like maybe it uses Hugo as a static site generator, [or] maybe it uses Contentful to manage the content, or maybe it uses Netlify to get deployed.” At least to me, that reads a lot more open than what I got from the initial propo…
You’d be right! GitHub Pages sites do fall under the remit of Jamstack, but not ticking every single box.
GitHub Pages runs on Jekyll, one of the most long-standing static site generators in the ecosystem.
If you’re wanting to check more of those boxes, such as feeding content in from an API, you’re welcome to spin up a Jekyll site right here with a few clicks: https://jamstack.new/jekyll
Re: JAMstack vs. WordPress: Which Is the Future of Web Architecture?
#5JAMStack seems to become more and more one of these terms without a clear definition: > “From my perspective,” he said, “[it’s] a JAMstack website if it uses one of those modern components — like maybe it uses Hugo as a static site generator, [or] maybe it uses Contentful to manage the content, or maybe it uses Netlify to get deployed.” At least to me, that reads a lot more open than what I got from the initial propo…
You’d be right! GitHub Pages sites do fall under the remit of Jamstack, but not ticking every single box. GitHub Pages runs on Jekyll, one of the most long-standing static site generators in the ecosystem. If you’re wanting to check more of those boxes, such as feeding content in from an API, you’re welcome to spin up a Jekyll site right here with a few clicks: https://jamstack.new/jekyll
That makes the term pretty much meaningless, or purely a marketing play.