{{ message }}
Add a site AMP version.
Nuxt.js has an example: https://github.com/nuxt/nuxt.js/tree/dev/examples/with-amp
Gatsby AMP Plugin: https://www.gatsbyjs.org/packages/gatsby-plugin-amp/
The AMP Project support is very important to accessibility and Google's Pagerank. So, it could will be awesome had this support in Gridsome.
It should be easy to navigate back. Right now there's no built-in way to do this. We already use navigate to navigate programatically. It might make sense to add the back-navigation feature there:
navigate.back()
The way it's done natively with web apis is via history's back and go properties. back does what you would expect, and go takes a number, so you can go back mult
Example gatsby + netlify cms project
A simple and visual static web server with collaboration features.
An SWT based API for managing users and issuing SWT tokens
Statiq Web is a flexible static site generator written in .NET.
A headless e-commerce for JAMstack sites
Carefully curated list of awesome Jamstack resources
Statamic 3: Core Package
Modern full stack CMS. Built with Gatsby, GraphQL, AWS Amplify, and Serverless technologies.
Source for headlesscms.org
Source for my website and blog (Jekyll + Gulp + Netlify)
A scaffold for a quick start building with the Eleventy SSG
A template for building a simple website with the Eleventy static site generator
Add a description, image, and links to the jamstack topic page so that developers can more easily learn about it.
To associate your repository with the jamstack topic, visit your repo's landing page and select "manage topics."
Preview links are not appearing for me because my CI/CD adds github metadata in the canonical location, but the github integration looks elsewhere.
Describe the bug
Currently, the Github integration looks at a commit status's contexts for a deploy url. The thing is, the canonical way to specify a deploy url is using environment deployments. So I think the integration should look at the e