31–40 of 52 posts
How is this different from a single page app? The article is also loaded with BS: > Faster performance. Serve pre-built markup and assets over a CDN Just like every single-page app. > More secure. No need to worry about server or database vulnerabilities Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API. > Less expensive. Hosting of static files are cheap…
Earlier quoted context omitted.
Yup, it pulls stuff in ahead of time. That said, that's just for the initial render. Once things are mounted and "static" can take advantage of apollo or whatever request lib you'd like for "dynamic" content. But the idea is to build out most paths in the build phase and then push up. A lot of the time thats all a site will need. It works amazingly well, at least with Gatsby.
How is that different from a regular single-page application? My understanding of JAM from watching [1] was that your entire site is static, except for JS that calls out to serverless APIs to CRUD your content on the backend or initiate some workflow with a third-party service like PayPal or Twilio. If your site allows user comments, then you would rebuild your static site every time the user comment is submitted ins…
Comments normally would probably be something like Disqus but I've also seen a demo of a Netlify dev doing a hacky hijack of their forms function which allowed you to approve a comment then re-render based on approved comments.
You can also setup a CD system that builds every X seconds/minutes/hours/days/etc.
It's just a different way to build websites. I think it's useful for marketing websites but not as helpful when you need a true app.
[1] https://www.gatsbyjs.org, also checkout: https://www.gatsbyjs.org/showcase/
How is this different from a single page app? The article is also loaded with BS: > Faster performance. Serve pre-built markup and assets over a CDN Just like every single-page app. > More secure. No need to worry about server or database vulnerabilities Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API. > Less expensive. Hosting of static files are cheap…
25 days ago I made this comment: "The key is to invent a new term for an existing entity. Here the author tries to introduce the term "document site" for static websites." The same happens here. Take an existing concept. Stick a new label-term on it. Market it like you're the inventor of this revolutionary concept to the unaware. Profit.
Earlier quoted context omitted.
Yup, it pulls stuff in ahead of time. That said, that's just for the initial render. Once things are mounted and "static" can take advantage of apollo or whatever request lib you'd like for "dynamic" content. But the idea is to build out most paths in the build phase and then push up. A lot of the time thats all a site will need. It works amazingly well, at least with Gatsby.
So there is no server-side rendering of content? Will Google index this correctly?
Oh look, something that takes 10x longer to develop than static html that is more performant and easier to manage.
I’m all for SPAs for products that reach a certain level of complexity. They are 10x more capable, but take 10x the work.
I did just implement Netlify CMS in a project though. Super easy to get set up and it's open source. It's missing some things from more polished CMSes that you might expect, like editor roles, but it's still pretty young. The project lead is really responsive and I have high hopes for it long term.
How is this different from a single page app? The article is also loaded with BS: > Faster performance. Serve pre-built markup and assets over a CDN Just like every single-page app. > More secure. No need to worry about server or database vulnerabilities Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API. > Less expensive. Hosting of static files are cheap…
In pure JAMstack, APIs are used only at the build step, and you don't have to expose them. You get your content such as blog posts from the API, render them to html and store on CDN.
Monolithic architecture refers mostly to Wordpress. With JAMstack you separate your CMS from your frontend, and you can manage your content with a service like https://www.contentful.com/ that doesn't define how the content gets rendered.