# Jamstack Published articles for Jamstack. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Making your site visible to LLMs and AI agents: 6 techniques that work, 8 that don't DevFeed: [Making your site visible to LLMs and AI agents: 6 techniques that work, 8 that don't]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-11-04T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [Search engine optimization (SEO)](), [agentic browsing](), [Artificial Intelligence](), [Claude Code](), [static-site-generator](), [AI Chat]() Tags: [accessibility](), [adobe](), [agent-readiness](), [agent-skill](), [agent-skills](), [agentic](), [agentic-browsing](), [agentic-commerce](), [ai](), [ai-agent](), [ai-agents](), [ai-answers](), [ai-assistant](), [ai-assistants](), [ai-bots](), [chatgpt](), [claude](), [dx](), [frontend-real-time](), [jamstack](), [llms](), [perplexity](), [sdks-extensions-plugins](), [seo]() ### AI overview The article's six-month server-log findings support two priorities: clean, server-rendered HTML for chat assistants, and Markdown content negotiation for coding agents that request it. In the authors' logs, chat fetchers mostly read HTML; over half of agent reads in September and October were Markdown, nearly all from Claude Code. Serve `.md` routes and negotiate `Accept: text/markdown` with `Vary: Accept`, correct q-value handling, and `406` responses for unsupported formats. Keep HTML semantically structured and lightweight, and measure requests in server logs because AI crawlers often do not run JavaScript. The authors found little AI use of `llms.txt` (ChatGPT fetched it once on their site), so they recommend it only as a low-cost, low-expectation addition. JSON-LD may help search indexes and shopping systems indirectly, though tests cited found most models could not read it directly. Check crawler access and distinguish provider crawlers from on-demand fetchers; results vary by audience and client. ### Source excerpt Most AI SEO advice is unproven. We tested what ChatGPT, Claude, and Perplexity actually read on our own site. Six techniques that make a site agent-friendly and visible to LLMs, eight that don't, and the metrics to tell the difference. ## Ship agent skills like packages: discovery index, digests, and install sources DevFeed: [Ship agent skills like packages: discovery index, digests, and install sources]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-08-12T00:00:00Z Content type: tutorial Language: en Sources: [Evil Martians]() Topics: [Agent Skills](), [AI-assisted coding](), [sha256](), [npm]() Tags: [agent](), [agent-experience](), [agent-skills](), [ai](), [ai-coding](), [ai-coding-agent](), [catalog](), [coding](), [coding-agent](), [coding-agents](), [digests](), [discovery](), [dx](), [file](), [how-to](), [index](), [install](), [jamstack](), [json](), [llms](), [packages](), [packaging](), [sha-256](), [skills]() ### AI overview The article presents a way to publish coding-agent skills as installable packages. A skill is a folder of instructions for a repeatable practice, authored in a GitHub repository and served from the publisher's domain. A `.well-known/agent-skills/index.json` discovery index lists skills and their metadata, including a SHA-256 digest; hosting the served files on the publisher's domain lets the digest match the bytes installers receive. The excerpt distinguishes single-file, multi-file, and bundle packaging, and recommends offering multiple install commands for readers using different tools. It frames the approach as familiar package-management machinery applied to skills. Detailed commands and packaging procedures are not present in the supplied excerpt. ### Source excerpt How to publish agent skills so any AI coding agent can find and install them: the .well-known/agent-skills/index.json discovery index, SHA-256 integrity digests, single-file vs multi-file vs bundle packaging, and every install command. Worked from the catalog we just open-sourced. ## Which AI actually reads your site? Two months of LLM traffic, measured DevFeed: [Which AI actually reads your site? Two months of LLM traffic, measured]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-07-21T00:00:00Z Content type: news Language: en Sources: [Evil Martians]() Topics: [Large Language Model](), [LLM observability](), [Internet Traffic](), [Back end]() Tags: [admission](), [agent](), [agent-experience](), [agent-skills](), [agents](), [ai](), [ai-assistants](), [ai-crawlers](), [all](), [analytics](), [backend](), [bots](), [course](), [dx](), [html](), [jamstack](), [llm](), [llms](), [llms-txt](), [markdown](), [server](), [traffic](), [zero]() ### AI overview Evil Martians tracked about 268,000 LLM-related requests to evilmartians.com over two months using server-side request instrumentation. The excerpt reports that ChatGPT fetched rendered HTML and almost never Markdown, while Claude Code requested Markdown 76% of the time, delivered through content negotiation. llms.txt was fetched mostly by bots other than the AI assistants it targets, and a hidden AI hint received no measurable hits. The authors say client-side analytics misses crawlers that do not execute JavaScript; tracking should run at request time in edge middleware or another request hook, classify raw requests and headers, then send server-side analytics events or parse logs. The excerpt does not provide the full measurement breakdown. ### Source excerpt We told you to measure. So of course we did it ourselves too: two months of server-side LLM traffic to evilmartians.com. Find out which agents read HTML, which read Markdown, what llms.txt actually does, and the one technique that got zero hits. ## Lessons from Netlify's Journey to Success DevFeed: [Lessons from Netlify's Journey to Success]() Original publisher: [Read original article]() Author: Chris Bach Co-founder; CSCO; Netlify Published: 2024-08-05T00:00:00Z Content type: article Language: en Sources: [Dotfiles Insider]() Topics: [Netlify](), [Jamstack](), [API Business Models]() Tags: [browser-based-ide](), [browser-ide](), [cloud-coding](), [cloud-dev-environment](), [cloud-development-environment](), [cloud-editor](), [cloud-ide](), [cloud-programming](), [co-founder](), [code-in-cloud](), [code-on-web](), [coding-environment](), [content-marketing](), [developer-community](), [ide-editor-online](), [ide-in-browser](), [ide-online](), [jamstack](), [netlify](), [online-code-editor](), [online-ide](), [online-programming](), [online-web-dev-ide](), [online-web-development-ide](), [sde](), [standardised-development-environment](), [stories-insights](), [web-architecture](), [web-based-coding](), [web-ide]() ### AI overview Netlify's co-founder and CSO describes lessons from building the company around JAMstack, including decoupled web architecture, developer community building, go-to-market strategy, delivering early product value, and adapting to industry changes. The article also discusses fundraising timing and developer advocacy as growth strategies. ### Source excerpt Netlify's Co-founder and CSO, Christian Bach, shares key lessons on transforming web architecture with JAMstack ## Why I migrated my blog from WordPress to Eleventy and Netlify DevFeed: [Why I migrated my blog from WordPress to Eleventy and Netlify]() Original publisher: [Read original article]() Author: Lea Verou Published: 2023-07-21T00:00:00Z Content type: article Language: en Sources: [Lea Verou's blog]() Topics: [Eleventy](), [Jamstack](), [Content Management System](), [WordPress](), [Netlify](), [Git](), [Markdown](), [Developer experience](), [GitHub Copilot]() Tags: [11ty](), [blog](), [cms](), [developer-experience](), [eleventy](), [git](), [github-copilot](), [ia](), [jamstack](), [markdown](), [meta](), [netlify](), [open-source]() ### AI overview The author explains why WordPress became less suitable for her blog and describes migrating to Eleventy, a statically generated site workflow using Git, Markdown, and Netlify. She highlights simplicity, developer experience, and reduced reliance on plugins while noting the effort required to migrate years of content, plugins, and styling. ### Source excerpt WordPress has been with me since my very first post in 2009. There is a lot to love about it: It's open source, it has a thriving ecosystem, a beautiful default theme, and a revolutionary block editor that makes my inner UX geek giddy. Plus, WP made building a website and publishing content accessible to everyone. No wonder it's the most popular CMS in the world, by a huge margin. However, for me, the bad had started to outweigh the good: Things I could do in minutes in a static site, in WP required finding a plugin or tweaking PHP code. It was slow and bloated. Getting a draft out of it and into another medium was a pain. Despite having never been hacked, I was terrified about it, given all the horror stories. I was periodically getting "Error establishing a database connection" errors, whose frequency kept increasing. It was time to move on. It's not you WP, it's me. It seemed obvious that the next step would be a statically generated blog. I had been using Eleventy for a while on a variety of sites at that point and loved it, so using that was a no-brainer. In fact, my blog was one of my last remaining non-JAMstack sites, and by far the biggest. I had built a simple 11ty blog for my husband a year ago, and was almost jealous of the convenience and simplicity. There are so many conveniences that just come for free with this workflow: git, Markdown, custom components, even GitHub Copilot as you write your prose! And if you can make the repo public, oooooh, the possibilities! People could even file PRs and issues for your blog posts! Using Netlify as a platform was also a no-brainer: I had been using it for years, for over 30 sites at this point! I love their simplicity, their focus on developer experience, and their commitment to open source. I also happen to know a bunch of folks there, and they have a great culture too. However, I was dreading the amount of work it would take to migrate 14 years of content, plugins, and styling. The stroke that broke the camel's ## The future of databases is not just a database DevFeed: [The future of databases is not just a database]() Original publisher: [Read original article]() Author: Stack Published: 2022-11-11T13:20:00Z Content type: article Language: en Sources: [Stack]() Topics: [Supabase](), [Jamstack](), [rachels-ramblings]() Tags: [convex](), [fullstack](), [jamstack](), [modern-web-development](), [perspectives](), [platform](), [reactivity](), [typescript](), [video](), [web-development](), [workflow]() ### AI overview A video presented at Jamstack 2022 describes Convex as a reactive backend platform combining a database with functions, workflows, sync, search, and file storage, built with TypeScript and intended to work with developers and their agents. ### Source excerpt The future of databases is Convex. This video originally aired at Jamstack 2022, highlighting the next evolution of modern web development architecture. ## Supabase Beta October 2021 DevFeed: [Supabase Beta October 2021]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2021-11-07T07:00:00Z Content type: article Language: en Sources: [Supabase]() Topics: [Supabase](), [API](), [Database](), [PostgreSQL](), [Documentation](), [Self-hosted](), [Jamstack](), [Next.js](), [Nuxt.js](), [Vue.js](), [Netlify]() Tags: [api](), [apis](), [article](), [auth](), [docs](), [github](), [guides](), [jamstack](), [netlify](), [next-js](), [nuxt](), [postgresql](), [providers](), [recap](), [schema](), [self-hosting](), [vue]() ### AI overview Supabase's October 2021 beta recap announces three new Auth providers--Slack, Spotify, and MessageBird phone logins--and multi-schema support across the Dashboard and API. It also highlights new documentation and guides, PostgreSQL Functions coverage, community activity, conference appearances, 20K GitHub stars, and the upcoming Launch Week III. ### Source excerpt Three new Auth providers, multi-schema support, and we're gearing up for another Launch Week. ## Netlify Becomes Astro's Official Hosting Partner DevFeed: [Netlify Becomes Astro's Official Hosting Partner]() Original publisher: [Read original article]() Author: Fred Schott Published: 2021-09-09T00:00:00Z Content type: news Language: en Sources: [The Astro Blog]() Topics: [Astro](), [Netlify](), [hosting](), [Open Source](), [software-development](), [Jamstack]() Tags: [astro](), [developer-experience](), [hosting](), [integration](), [jamstack](), [netlify](), [open-source](), [open-source-maintenance](), [partner]() ### AI overview Netlify becomes Astro's first corporate sponsor and official hosting partner, contributing $2,500 monthly to Astro's open source maintenance and development. The partnership's first integration will add a "Deploy with Netlify" button to Astro's official starter templates. ### Source excerpt We are happy to announce that Netlify has become Astro's first corporate sponsor and exclusive hosting partner, donating $2,500 each month towards the ongoing open source maintenance and development of Astro. ## The Jamstack with Next.js and Prisma DevFeed: [The Jamstack with Next.js and Prisma]() Original publisher: [Read original article]() Author: Daniel Norman Published: 2020-12-11T00:00:00Z Content type: tutorial Language: en Sources: [Prisma]() Topics: [Jamstack](), [Next.js](), [Prisma](), [software-architecture](), [Web Development](), [Web app](), [Scalability]() Tags: [architecture](), [developers](), [incremental](), [jamstack](), [next-js](), [prisma](), [rendering]() ### AI overview A tutorial on building interactive Jamstack web applications with Next.js and Prisma. It explains rendering and logic trade-offs, data placement, static generation, and a hybrid approach using server and client-side techniques. ### Source excerpt Learn how to build interactive Jamstack apps with Next.js and Prisma and incremental static re-generation. ## Going Full Static DevFeed: [Going Full Static]() Original publisher: [Read original article]() Published: 2020-06-18T00:00:00Z Content type: release Language: en Sources: [Nuxt]() Topics: [Nuxt.js](), [Jamstack](), [Server-side rendering](), [Crawler](), [HTML](), [Single-page application (SPA)](), [Web Development]() Tags: [engineering](), [hosting](), [html](), [jamstack](), [navigation](), [nuxt](), [performance](), [release](), [server-side-rendering](), [ssr]() ### AI overview Nuxt 2.13 introduces full static export for JAMstack applications. The static target pre-renders pages to HTML, extracts payloads for client-side navigation without API calls, improves smart prefetching, includes a crawler, supports SPA fallback behavior, and improves the development experience and deployment speed. ### Source excerpt Long awaited features for JAMstack fans has been shipped in v2.13: full static export, improved smart prefetching, integrated crawler, faster re-deploy, built-in web server and new target option for config ⚡ ## Choosing a Website Platform: WordPress, Wix, or JAMStack DevFeed: [Choosing a Website Platform: WordPress, Wix, or JAMStack]() Original publisher: [Read original article]() Published: 2020-06-14T00:00:00Z Content type: opinion Language: en Sources: [Markus Hatvan]() Topics: [Website](), [WordPress](), [Jamstack](), [Web Development](), [gatsby](), [Next.js]() Tags: [gatsby](), [git](), [jamstack](), [next-js](), [open-source](), [performance](), [security](), [website](), [wordpress]() ### AI overview The article compares WordPress, WYSIWYG tools such as Wix, and JAMStack solutions such as Gatsby and Next.js for building a website. It presents the author's subjective reasons for preferring more control over code and performance, while acknowledging WordPress's speed of setup, plugin ecosystem, and ease of use. ### Source excerpt How to choose where to set up your website when you have so many options and so little time. ## Why I Chose SapperJS For My Website, And What I've Learned About The Framework So Far DevFeed: [Why I Chose SapperJS For My Website, And What I've Learned About The Framework So Far]() Original publisher: [Read original article]() Published: 2020-06-13T00:00:00Z Content type: opinion Language: en Sources: [Markus Hatvan]() Topics: [Framework](), [Jamstack](), [JavaScript](), [Website]() Tags: [developer-experience](), [framework](), [jamstack](), [javascript](), [website]() ### AI overview A developer explains why they chose SapperJS for a website built with a modern JAMStack setup. They compare alternatives including Next.js, Gatsby, Hugo, and Nuxt.js, considering performance, SEO, developer experience, innovation, and the opportunity to explore different JavaScript frameworks. ### Source excerpt Since I wanted to go for a website built on a modern JAMStack setup, I had these options based on framework popularity and matureness. ## Using VueJS + GraphQL to make Practical Magic DevFeed: [Using VueJS + GraphQL to make Practical Magic]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2018-08-27T22:29:00Z Content type: tutorial Language: en Sources: [nystudio107]() Topics: [GraphQL](), [Vue.js](), [Content Management System](), [Front end](), [JavaScript](), [axios](), [Bootstrap](), [Jamstack]() Tags: [auto-complete](), [axios](), [bootstrap](), [craft](), [everyday](), [form](), [graphql](), [headless](), [insights](), [jamstack](), [javascript](), [like](), [magic](), [practical](), [problems](), [saving](), [searching](), [solve](), [submission](), [using](), [vuejs]() ### AI overview A practical tutorial showing how to use VueJS and GraphQL with a headless Craft CMS backend to implement auto-complete search and save contact-form submissions. It introduces the frontend and backend tooling used in the examples, including Axios, Bootstrap 4, Craft CMS, and CraftQL. ### Source excerpt Make some practical magic with VueJS + GraphQL to solve everyday problems like auto-complete searching and form submission saving with a headless Craft CMS server ## Managing content for a JAMstack site with Netlify CMS DevFeed: [Managing content for a JAMstack site with Netlify CMS]() Original publisher: [Read original article]() Author: {"twitter"=\>"hlaueriksson"} Published: 2017-06-30T12:00:00Z Content type: article Language: en Sources: [Henrik Lau Eriksson]() Topics: [Jamstack](), [Netlify](), [static-site-generator](), [Hugo]() Tags: [api](), [apis](), [architecture](), [azure](), [azure-functions](), [blog](), [blog-post](), [build-tool](), [callback](), [client](), [cms](), [code](), [command](), [configuration](), [content](), [hugo](), [jamstack](), [modern-web-development](), [netlify](), [web](), [web-development]() ### AI overview Netlify CMS provides a Git-based way for non-technical users to manage content for a JAMstack site: edits are pushed to Git and trigger a new site build. The excerpt describes adding it to a Hugo site using a five-part setup: create a Netlify site from a Git repository, configure its build, register a GitHub OAuth application, install an authentication provider, and update the site code. It presents Netlify CMS as an open-source option for static site generators, but does not include the specific build settings, OAuth values, or code changes. ### Source excerpt Content for the modern web development architecture: ## Building a JAMstack site with Hugo and Azure Functions DevFeed: [Building a JAMstack site with Hugo and Azure Functions]() Original publisher: [Read original article]() Author: {"twitter"=\>"hlaueriksson"} Published: 2017-05-31T20:00:00Z Content type: tutorial Language: en Sources: [Henrik Lau Eriksson]() Topics: [Jamstack](), [Hugo](), [azure functions](), [static-site-generator](), [Web Development]() Tags: [apis](), [architecture](), [azure](), [azure-functions](), [bootstrap](), [css](), [hugo](), [jamstack](), [javascript](), [jquery](), [modern-web-development](), [web-development]() ### AI overview The excerpt describes a JAMstack recipe site built with Hugo, jQuery, and Azure Functions: Hugo generates the static markup, while JavaScript calls reusable APIs implemented as Azure Functions. It presents the approach as offering better performance, security, scaling cost, and developer experience, and highlights Hugo's fast builds and Windows installation. The example uses TOML configuration and data, Markdown content with front matter, Hugo templates and partials, and page attributes to provide data to JavaScript. The excerpt ends during the JavaScript description, so it does not show the full implementation or how the API functions work. ### Source excerpt Modern web development architecture: