I'm a big fan of JAMstack. It feels like a genuinely positive development for the web. I'm eagerly anticipating the upcoming conferences.
Of any web trend, #jamstack seems like it will be the least regrettable.
— Chris Coyier (@chriscoyier) May 22, 2019
However, I wonder if the acronym fully captures its essence. While I wouldn't suggest changing it – established names have momentum – the core strength lies in static file hosting. This forms the bedrock of its power, unlocking several key advantages:
- CDN Hosting for Everything: Even the HTML (the 'M' in JAMstack) benefits from CDN hosting, a significant speed boost unavailable with traditional approaches. This inherent speed encourages maintaining optimal performance throughout development.
-
Simplified Workflow: The development process is streamlined:
git clone
,npm install
,build
, and deploy via adist
folder push. Platforms like Netlify provide URLs for every build, even on branches, highlighting the immutability of deployments – a snapshot of files at a specific point in time. - Powerful Cloud Functions: The absence of traditional server-side languages encourages the use of cloud functions for server-side logic. This architectural approach aligns perfectly with the JAMstack philosophy.
It's crucial to avoid limiting JAMstack to just Jekyll blogs. While static site generators are highly compatible, and pre-built markup is beneficial for speed and SEO, it's not mandatory.
A client-side JavaScript application deploying a <div> and a JavaScript bundle interacting with APIs to build the site still qualifies as JAMstack. It's statically hosted (likely) with cloud functions providing data.
<blockquote>
<p>I’d say “yes”. Perhaps a little more SSR would be good for all the reasons but meh, not required for a jamstack merit badge.</p>
<p>— Chris Coyier (@chriscoyier) May 22, 2019</p>
</blockquote>
<p>The JAMstack approach encourages maximizing static files, promoting static content whenever feasible. While often referred to as "server-side rendered" (SSR), it's more accurate to describe it as markup generated during a <em>build step</em>, before deployment. Again, not a requirement, but a strong recommendation.</p>
<p>We have statically hosted HTML and other assets (CSS, images). Then:</p>
<ul>
<li>
<strong>J</strong>avaScript</li>
<li>
<strong>A</strong>PIs</li>
</ul>
<p>These are closely related. JavaScript files are statically hosted, execute, and communicate with APIs (e.g., a GraphQL endpoint) as needed.</p>
<p>A hybrid approach is also possible – pre-building some markup, while relying on JavaScript and API calls for dynamic content. Consider an e-commerce site with pre-built homepage and product pages, but a dynamically generated product catalog fetched via API calls.</p>
<p>If a new acronym were needed, incorporating static hosting and combining JavaScript and APIs into "APIs" might yield:</p>
<p><strong>S</strong>tatic <strong>H</strong>osting, <strong>A</strong>PIs, and <strong>M</strong>arkup, or <strong>SHAMstack</strong>. Perhaps not the best choice!</p>
</div>
The above is the detailed content of JAMstack? More like SHAMstack.. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
