* Write more detailed Admin architecture docs

* Add section on production deployment to gatsby-admin docs

* Absolute URLs so they work on npm etc.

* Fix pronouns and wording

* Clean up some more

* Tighten up language around production deployment

Co-authored-by: Brent Jackson <jxnblk@gmail.com>

* Update packages/gatsby-admin/README.md

Co-authored-by: Brent Jackson <jxnblk@gmail.com>

Co-authored-by: Brent Jackson <jxnblk@gmail.com>

…stor (#25974)

* Handle webpack in state machine

* Add internal export

Co-authored-by: Yogi <me@yogi.codes>

Co-authored-by: Aisha Blake <aisha@gatsbyjs.com>

Based on a recent increase in the volume of requests, I'm updating how people can request their free Gatsby swag for contributions that aren't made on GitHub.

…25965)

* feat(gatsby-source-filesystem: improve wrong url rejection message

The existing message made tracing down a bug from within the new WP source plugin harder than necessary.

Old message: `wrong url: ${url}`

Updated message: `url passed to createRemoteFileNode is either missing or not a proper web uri: ${url}`

* chore: format

* update rejects test to match new message

Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>

…cs (#25926)

* change bash to shell

* dont change text file code language

* chore: add tests to static-query filepaths

* fix windows paths

 - babel-preset-gatsby@0.5.4
 - gatsby-admin@0.1.100
 - gatsby-cli@2.12.66
 - gatsby-core-utils@1.3.14
 - gatsby-page-utils@0.2.19
 - gatsby-plugin-manifest@2.4.21
 - gatsby-plugin-mdx@1.2.29
 - gatsby-plugin-offline@3.2.21
 - gatsby-plugin-page-creator@2.3.19
 - gatsby-plugin-preload-fonts@1.2.19
 - gatsby-plugin-sharp@2.6.22
 - gatsby-recipes@0.1.56
 - gatsby-remark-images@3.3.21
 - gatsby-source-contentful@2.3.32
 - gatsby-source-drupal@3.5.26
 - gatsby-source-filesystem@2.3.23
 - gatsby-source-shopify@3.2.25
 - gatsby-source-wordpress@3.3.26
 - gatsby-telemetry@1.3.23
 - gatsby-transformer-remark@2.8.27
 - gatsby-transformer-sqip@2.3.22
 - gatsby@2.24.11