Bug report

Describe the bug

This code will make error

export const { BACKEND_URL, API_URL, CDN_URL, NEXT_PUBLIC_ROOT_URL } = process.env;

This code works as expected:

export const BACKEND_URL = 

Summary

The gatsby-manifest-plugin documentation for generating icons is unclear.

        icon: `src/images/favion.svg`, // This path is relative to the root of the site.
        icons: [
          {
            src: `src/images/favicon--short.svg`,
            sizes: `192x192`,
            type: `image/png`,
         

• I confirm that this is an issue rather than a

We have a bunch of features we can move from the Beta section to the permanent docs.

I think everything under https://www.netlifycms.org/docs/beta-features/ except i18n and Nested collections can be moved

It would make sense to move each feature at a time to make sure we're not cluttering the docs

While working on my i18n_subsites plugin, I came up with an idea how to simplify some code that is often used in Pelican: doing stuff with a temporarily different locale.
This could be neatly solved by a context manager:

from contextlib import contextmanager
import locale

@contextmanager
def temporary_locale(temp_locale=None):
    '''Enable code to run in a context with a temporary lo

Is your feature request related to a problem? Please describe.
I am using react-static to create a site that is hosted out of S3. I want to be able to use object versioning to track changes to the objects over time, but I can't do that with the main JS file, as it has a hash code in the middle. I am guessing that this is used for cache busting, but S3 already has robust etag support built in,

Summary

Add a site AMP version.

Basic example

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/

Motivation

The AMP Project support is very important to accessibility and Google's Pagerank. So, it could will be awesome had this support in Gridsome.

Describe the bug

As described here, When using the portfolio widget with enough tags as to occupy the entire width of the page, the cards are not wide enough (or are not separated enough) to occupy also the entire width (you can see it live here: <https://rodrigoalcarazdelaosa.me/en/notes/#15-16-year-

I don't really know Tokio or the best way to upgrade it, if someone has time to do it it shouldn't take too long.