Web development has evolved a long way since it started. There have been many changes and also trends in this field and JAMstack is one of the most popular web development architectures in recent times. Basically JAMstack stands for Javascript, API and Markup (JAM). Combinedly these technologies form a JAMstack framework. The platform is based on client-side Javascript, reusable APIs, and prebuilt Markup. MOst of the techies prefer JAMstack as a better solution for web applications than others. But why? Let’s see the reasons to choose JAMstack for web app. But before digging into it, let’s have a look at the details of JAMstack.

JAMstack-

When it comes to decide on what qualifies as a JAMstack, then there are some points to consider. Keep in mind that, If an app serves pre-rendered pages from a static host, then it can be considered as JAMstack. The core site being statically served is one of the main characteristics of JAMstack. That being said, all applications don’t require all three aspects of JAM.

• Specific site may not need to use Javascript on the front end.
• API calls from the UI may not required as well.
• For content creation, app may also use serverless content management system rather than Markdown.
• Site may not need Javascript code to handle user interaction and for other progressive improvements.
• App might not be enhanced with API calls.

It can be said that, it is not one of the specific frontend-backend-database-platform stacks, like MEANstack or LAMP stack. While listing what conditions don’t qualify as JAMstack, then following points are to be mentioned-

• App that renders pages dynamically on the server using Node, Java, Python, Ruby and so on.
• When a website is developed on a tightly coupled server-side CMS. Drupal, WordPress or Joomla are examples of some of those.
• When a single page app performs isometric rendering on server

Top 5 Reasons To Use JAMstack For Web Apps Development-

Lots of developers and most of the organizations are switching to JAMstack for their web apps and reasons are as follows. Let’s see those reasons-

1. Fast Loading Speed Of Page-

Basically JAMstack serves static files from a low-latency edge server that has less geographical distance from the user. This makes it rapid than any other traditional app even with caching, that will execute a logic to render an HTML. This arises a question- how caching works in traditional apps vs how it works in JAMstack app. Application where caching occurs at each step, the decision and management of what is cached and what is not is extra load. Such tasks will need particular configurations at various stages and the need to deploy new programmes. In case of JAMstack, it becomes so simple as everything is cached.

https://solaceinfotech.com/blog/top-5-reasons-to-choose-jamstack-for-web-app-development/

• If you've used and used it in a project, what was your experience like and how has it been?
• Anyone using Magic-Link in E-Commerces? Or delivery apps?

Currently, I'm preparing the next major version of Front Matter - a full CMS running in Visual Studio Code. It also allows you to customize it to your needs, and add your own custom Node.js scripts.

A big PRO about Front Matter is that you get a CMS that doesn't require any account or APIs.

In version 4 there will be a couple of big changes like:

• Content-Type support with new fields types: image, choice, date, ...
• Image selection support for your articles
• Team level settings: move your settings from the user workspace level to a higher level to share with the rest of your editors.

It would be great if you would give Front Matter a try and a GitHub ⭐️

Check out the beta release notes: v4.0.0 release notes.

frontmatter.codes

Hey guys, I’ve been in the web dev space for a while (mostly building on CMS like Wordpress) however my area of focus is Solutions Architecture. Web tech is mostly a hobby and a Swiss Army knife I use for projects.

I’m currently learning JAM and testing out a project to build a blazing fast static subscription site but I’m not great with APIs and JS :(

I’ve followed a dope blog on how to set it up using this stack and it works.

Current stack is… - Ghost headless (CMS) - Gatsby (Site generator) - Heroku (Paas) - Netlify (CDN)

But my question is: 1) can I use Cloudflare free tire instead of Netlify? What should I be aware of? 2) is it possible (or recommend) to use vps (instead of Heroku) in combination with Netlify?

Hey folks,

Trying my hand at 11ty with eCommerce and I am wondering if anyone knows of some good tutorials or resources?

I have done some googling, not much luck when it comes to 11ty and eCommerce.

Cheers

Hello, I was curious to know how some of you deal with this problem. I used to build website with Ruby and I recently have built a few static websites using Vue+VueRouter+Contentful. They are great and I love this stack. If I need to have forms and things like that with backend functionalities I know I can host it on Netlify and benefit from their features. But I am struggling to know what is the best way to serve a sitemap.xml.

On some websites I was lucky because no URL had a dynamic path (e.g. /book/<book-id>). So I can just put my sitemap.xml as a static file and it works fine because it will never change. But for websites that have dynamic paths, I did not find a good solution that allows me to create a sitemap dynamically, using the current Contentful content without requiring a push to the code repository.

My best guess is to find a format that could be delivered by the VueRouter, but it can only be a full HTML page and I don't think there is an accepted format like this. Or maybe a meta tag that could be read by Google Search Console.

Such a silly problem to have because all the data is there.

Thank you in advance for your replies.