Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] confusing gatsby-config.js #11957

Closed
CHEWX opened this issue Feb 21, 2019 · 4 comments · Fixed by #12949
Closed

[Docs] confusing gatsby-config.js #11957

CHEWX opened this issue Feb 21, 2019 · 4 comments · Fixed by #12949
Labels
good first issue Issue that doesn't require previous experience with Gatsby help wanted Issue with a clear description that the community can help with. stale? Issue that may be closed soon due to the original author not responding any more. type: documentation An issue or pull request for improving or updating Gatsby's documentation

Comments

@CHEWX
Copy link

CHEWX commented Feb 21, 2019

Hi,

New to Gatsby and I've noticed that there is no clear link back to gatsby-config.js.

For example if you were to setup a new site and then complete the quick tutorial. You'd then like to finish off with adding Google Analytics.

You search gatsby analytics and get taken to this page — https://github.com/gatsbyjs/gatsby/blob/master/docs/docs/adding-analytics.md

It's not obvious what gatsby-config.js is? Should there be a link back to the docs on this?

Also, the example of Google Analytics. Most people would just copy and paste that into their gatsby-config.js file, however, shouldn't it display like this:

module.exports = {
  plugins: [
    {
      resolve: 'gatsby-plugin-google-analytics',
      options: {
        // replace "UA-XXXXXXXXX-X" with your own Tracking ID
        trackingId: "UA-XXXXXXXXX-X",
      },
    },
  ],
};

This gives a little context.

Might be overly simplifying, just initial feedback.

@wardpeet
Copy link
Contributor

Not sure how we do it for other README.md but that's a great idea!

I would recommend something like

module.exports = {
  // ...gatsby config
  plugins: [
    // ...other gatsby plugins
    {
      resolve: 'gatsby-plugin-google-analytics',
      options: {
        // replace "UA-XXXXXXXXX-X" with your own Tracking ID
        trackingId: "UA-XXXXXXXXX-X",
      },
    },
  ],
};

@CHEWX mind opening a PR for this? That would help us a lot!

@gatsbyjs/docs do any of you have a better solution?

@wardpeet wardpeet added the type: documentation An issue or pull request for improving or updating Gatsby's documentation label Feb 22, 2019
@marcysutton
Copy link
Contributor

Ah yes, I could see how that would be confusing. To clarify your steps, did you search on Google for "adding analytics" and land on the Github page? The page on the Gatsby docs shows the file title (gatsby-config.js), but the Github version does not: https://www.gatsbyjs.org/docs/adding-analytics/#using-gatsby-plugin-google-analytics

I agree that showing a more complete gatsby-config.js structure like what you have here would help in both cases. You could also add a link to this page: https://www.gatsbyjs.org/docs/gatsby-config/#gatsby-config

@freiksenet freiksenet added help wanted Issue with a clear description that the community can help with. good first issue Issue that doesn't require previous experience with Gatsby labels Feb 26, 2019
@gatsbot gatsbot bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Mar 19, 2019
@gatsbot
Copy link

gatsbot bot commented Mar 19, 2019

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

@gatsbot
Copy link

gatsbot bot commented Mar 30, 2019

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!

@gatsbot gatsbot bot closed this as completed Mar 30, 2019
robphoenix added a commit to robphoenix/gatsby that referenced this issue Apr 2, 2019
DSchau pushed a commit that referenced this issue Apr 2, 2019
<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->
dhurlburtusa added a commit that referenced this issue Apr 3, 2019
* docs(gatsby-source-shopify): Add note about API permissions (#13037)

Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message.

* chore(docs): match the Wording Style of Other Tutorial Parts (#13034)

* chore(docs): fix typo in convincing others doc (#13033)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Fixes a misspelled word.

* fix(docs): expand guidelist on partnering with gatsby page (#13029)

Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/:

![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png)

* fix(starters): update gatsby monorepo (#12925)

This PR contains the following updates:

| Package | Type | Update | Change | References |
|---|---|---|---|---|
| gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) |

---

### Release Notes

<details>
<summary>gatsbyjs/gatsby</summary>

### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

</details>

---

### Renovate configuration

:date: **Schedule**: At any time (no schedule defined).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`".

:ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired.

---

 - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby).

* feat(blog): add gatsby is great blog post (#12777)

* chore: add blog post

* chore: keep iterating

* chore: more tweaks

* feat: nearly finish up

* chore: run tinypng

* chore: fix some typos

* chore: fix snippet

* chore: add a gif, it gets the people going

* chore: more

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* chore: change date

* chore: tighten up last section

* chore: change data

* chore: update per feedback

* chore(docs): replace absolute links with relative links (#12949)


<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* chore(showcase): Add Assortment to site showcase (#13002)

## Description

Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃

* Fix Comma Usage; Misc Updates
dhurlburtusa added a commit that referenced this issue Apr 3, 2019
* docs(gatsby-source-shopify): Add note about API permissions (#13037)

Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message.

* chore(docs): match the Wording Style of Other Tutorial Parts (#13034)

* chore(docs): fix typo in convincing others doc (#13033)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Fixes a misspelled word.

* fix(docs): expand guidelist on partnering with gatsby page (#13029)

Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/:

![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png)

* fix(starters): update gatsby monorepo (#12925)

This PR contains the following updates:

| Package | Type | Update | Change | References |
|---|---|---|---|---|
| gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) |

---

### Release Notes

<details>
<summary>gatsbyjs/gatsby</summary>

### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

</details>

---

### Renovate configuration

:date: **Schedule**: At any time (no schedule defined).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`".

:ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired.

---

 - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby).

* feat(blog): add gatsby is great blog post (#12777)

* chore: add blog post

* chore: keep iterating

* chore: more tweaks

* feat: nearly finish up

* chore: run tinypng

* chore: fix some typos

* chore: fix snippet

* chore: add a gif, it gets the people going

* chore: more

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* chore: change date

* chore: tighten up last section

* chore: change data

* chore: update per feedback

* chore(docs): replace absolute links with relative links (#12949)


<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* chore(showcase): Add Assortment to site showcase (#13002)

## Description

Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃

* feat(gatsby-dev-cli): add verdaccio support (#11525)

* feat(gatsby-dev-cli): add verdaccio support [wip]

* yuck - don't look

* just to verify verdaccio

* fix gitignore and add htpasswd with dummy gatsby-dev user

* some logging to understand why it tries to handle all the packages

* just temporarily so it hopefully at least works

* moar data

* don't copy all the packages right now

* don't rely on package name starting with "gatsby" heuristic

* tmp commit

* tmp

* fs change

* tmp

* a

* updates

* remove random files that shouldn't be here

* tmp

* revert dep changes

* ignore changes to package.json created during publishing

* testing of dep change in gatsby-cli is picked up by gatsby-dev-cli

* let's see if gatsby-dev will handle case of no node_modules

* sanity check

* adjust console message

* add missing devDeps

* more missing devDeps

* grab package.json from unpkg if package is not yet installed locally

* correctly ignore package.json changes during publishing

* cleaning things up

* htpasswd loc

* restore gatsby package.json

* adjust ignore files

* gatsby-dev-cli: ignore tests

* remove extra ln

* less console output

* turns out you don't need htpasswd after all

* use exact when installing local packages  - timestamp is used in version

* why it failed?

* use yarn for publishing - see verdaccio/verdaccio#997

* v0.1.1

* add temporary .npmrc file to allow anonymous publishes

* add some jsdocs

* update yarn.lock

* oops

* debug why still can't publish anon

* adjust npmrc content

* doh

* Revert "debug why still can't publish anon"

This reverts commit fc1045a.

* handle package installation of deps didn't change

* skip version changes for packages in gatsby mono-repo, queue copying instead of doing it immediately

* fix tests

* packages stored in verdaccio storage seems to be picked up by jest and causing trouble, so let's ignore verdaccio storage directory

* bye "wat", you will be missed

* bail early to avoid conditional bracket hell

* more bailing early

* more concise

* new line

* use exaca to simplify running yarn

* clean up www/.gitignore

* handle not existing packages

* remove unused (was needed for basic auth)

* cleanup temp file changes when process exit in middle of publishing

* ops

* Apply suggestions from code review

Co-Authored-By: pieh <misiek.piechowiak@gmail.com>

* cleanup unpkg response handler

* move stuff around

* remove tmp comment

* document traversePackageDocs fn

* restrcuture files

* add basic tests for traversingPackageDeps

* add basic tests for generating packages to publish (based on dep graph)

* fix tests on windows

* handle circular dependencies when constructing list of packages to publish

* remove cat ;(

* restore original e2e-test script

* update gitignore

* chore(release): Publish

 - babel-plugin-remove-graphql-queries@2.6.3
 - babel-preset-gatsby@0.1.11
 - gatsby-dev-cli@2.4.13
 - gatsby-plugin-typescript@2.0.12
 - gatsby-source-shopify@2.0.23
 - gatsby@2.3.6

* chore(release): Publish

 - gatsby-dev-cli@2.4.14

* docs(gatsby-dev-cli): Edit README (#13049)

* Build out Gatsby media information in docs (#12906)

* add video info, delete unnecessary stubs

Related to #12903

* fix internal link for html5 video section

* update videoTitle example

Co-Authored-By: marcysutton <holla@marcysutton.com>

* Apply suggestions from code review

thanks for the feedback!

Co-Authored-By: marcysutton <holla@marcysutton.com>

* incorporate feedback, make into real docs!!

* delete unused stubs

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <holla@marcysutton.com>

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <holla@marcysutton.com>

* chore(gatsby): fix domready package to be compatible with ie10 (#13027)

* changed domready package to domready-loaded which is compatible with ie10

* updated domready to @mikaelkristiansson/domready

* updated packages/gatsby to use @mikaelkristiansson/domready

* chore(release): Publish

 - gatsby@2.3.7

* feat(gatsby-transformer-react-docgen): use local babel config for react-docgen (#12001)

* feat: use local babel config for react-docgen

BREAKING CHANGE: now uses the local babel config with a fallback

* Update README.md

* chore(release): Publish

 - gatsby-transformer-react-docgen@4.0.0

* chore(docs): add “Why I used GatsbyJS (#12954)

Why I used GatsbyJS

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

<!-- Write a brief description of the changes introduced by this PR -->

## Related Issues

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* feat(www): don't check for overview frontmatter (#13060)

Fixes `[[guidelist]]` not being replaced in few pages (i.e. in https://www.gatsbyjs.org/docs/winning-over-stakeholders/ )

The code is handling cases when there are no children (tried building locally and it worked just fine).

Follow up to this would be to clear `.md` files that use `overview` and adjust page query. But this is just quick fix.

* chore(docs): add starter library to docs sidebar under starters (#12963)

 40% of people visiting the starters page go here next, so we should probably add this:

![image](https://user-images.githubusercontent.com/4388699/55285012-58d26180-5337-11e9-9259-68e81b4894ad.png)

* chore(showcase): Add gmartinez.dev to showcase (#13067)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Adding gmartinez.dev to showcase list in site.yml

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->


Co-authored-by: Lennart <lekoarts@gmail.com>

* fix(gatsby): don't try to statically analyze gatsby-node, require it and examine exports instead (#13053)

* fix: don't try to statically analyze gatsby-node, require it and examine exports instead

* differentiate test names

* Update packages/gatsby/src/bootstrap/resolve-module-exports.js

Co-Authored-By: pieh <misiek.piechowiak@gmail.com>

* chore(release): Publish

 - gatsby@2.3.8

* Use Loki's elemMatch operator (#13025)

* feat(gatsby): add util.promisify polyfill for older node version (#13024)

* refactor(gatsby): gatsby develop: cleanup port detection (#13006)

* chore(release): Publish

 - gatsby@2.3.9

* fix(gatsby): ignore __esModule export in gatsby-node exports (#13081)

I introduced bug/regression in #13053 by not removing `__esModule` export name from resolved export names - it break some plugins

Fixes: #13079

* chore(release): Publish

 - gatsby@2.3.10

* fix(www): Hubspot form UI (#13080)

* fix(www): Work around HubSpot’s CSS being loaded

…by pulling in react-hubspot-form locally, and modifying it slightly. See comment in `www/src/components/react-hubspot-form` for more info.

* Fix `formInput` styles

… now matching the reference homepage newsletter form — no more Futura PT for input text.

* Return nothing because linter

* Make into Two Words
DSchau pushed a commit that referenced this issue Apr 4, 2019
* Fix Comma Usage

* Fix Comma Usage; Misc Improvements (#13038)

* Fix Misuse of Commas, Et Al (#13039)

Use em dash in place of two hyphens.
Format paragraph to be on one line (apparently the convention).

* Fix Comma Usage and Do Some Misc Changes (#13040)

* Fix Comma Usage and Do Some Misc Changes

Do code formatting to match rest of file.
Use em dash instead of two hyphens.
Etc.

* Update HTML Entity

* Add Hyphen for Clarity (#13042)

* Fix Comma Usage in Blog (#13085)

* docs(gatsby-source-shopify): Add note about API permissions (#13037)

Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message.

* chore(docs): match the Wording Style of Other Tutorial Parts (#13034)

* chore(docs): fix typo in convincing others doc (#13033)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Fixes a misspelled word.

* fix(docs): expand guidelist on partnering with gatsby page (#13029)

Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/:

![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png)

* fix(starters): update gatsby monorepo (#12925)

This PR contains the following updates:

| Package | Type | Update | Change | References |
|---|---|---|---|---|
| gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) |

---

### Release Notes

<details>
<summary>gatsbyjs/gatsby</summary>

### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

</details>

---

### Renovate configuration

:date: **Schedule**: At any time (no schedule defined).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`".

:ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired.

---

 - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby).

* feat(blog): add gatsby is great blog post (#12777)

* chore: add blog post

* chore: keep iterating

* chore: more tweaks

* feat: nearly finish up

* chore: run tinypng

* chore: fix some typos

* chore: fix snippet

* chore: add a gif, it gets the people going

* chore: more

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* chore: change date

* chore: tighten up last section

* chore: change data

* chore: update per feedback

* chore(docs): replace absolute links with relative links (#12949)


<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* chore(showcase): Add Assortment to site showcase (#13002)

## Description

Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃

* Fix Comma Usage; Misc Updates

* Make into Two Words (#13084)

* docs(gatsby-source-shopify): Add note about API permissions (#13037)

Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message.

* chore(docs): match the Wording Style of Other Tutorial Parts (#13034)

* chore(docs): fix typo in convincing others doc (#13033)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Fixes a misspelled word.

* fix(docs): expand guidelist on partnering with gatsby page (#13029)

Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/:

![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png)

* fix(starters): update gatsby monorepo (#12925)

This PR contains the following updates:

| Package | Type | Update | Change | References |
|---|---|---|---|---|
| gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) |
| gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) |

---

### Release Notes

<details>
<summary>gatsbyjs/gatsby</summary>

### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.4...gatsby@2.3.5)

### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/gatsby@2.3.3...gatsby@2.3.4)

</details>

---

### Renovate configuration

:date: **Schedule**: At any time (no schedule defined).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`".

:ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired.

---

 - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby).

* feat(blog): add gatsby is great blog post (#12777)

* chore: add blog post

* chore: keep iterating

* chore: more tweaks

* feat: nearly finish up

* chore: run tinypng

* chore: fix some typos

* chore: fix snippet

* chore: add a gif, it gets the people going

* chore: more

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md

Co-Authored-By: DSchau <DSchau@users.noreply.github.com>

* chore: change date

* chore: tighten up last section

* chore: change data

* chore: update per feedback

* chore(docs): replace absolute links with relative links (#12949)


<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Suggest a more complete structure to the example gatsby-config.js file

## Related Issues

Along with #12103 this PR fixes #11957

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* chore(showcase): Add Assortment to site showcase (#13002)

## Description

Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃

* feat(gatsby-dev-cli): add verdaccio support (#11525)

* feat(gatsby-dev-cli): add verdaccio support [wip]

* yuck - don't look

* just to verify verdaccio

* fix gitignore and add htpasswd with dummy gatsby-dev user

* some logging to understand why it tries to handle all the packages

* just temporarily so it hopefully at least works

* moar data

* don't copy all the packages right now

* don't rely on package name starting with "gatsby" heuristic

* tmp commit

* tmp

* fs change

* tmp

* a

* updates

* remove random files that shouldn't be here

* tmp

* revert dep changes

* ignore changes to package.json created during publishing

* testing of dep change in gatsby-cli is picked up by gatsby-dev-cli

* let's see if gatsby-dev will handle case of no node_modules

* sanity check

* adjust console message

* add missing devDeps

* more missing devDeps

* grab package.json from unpkg if package is not yet installed locally

* correctly ignore package.json changes during publishing

* cleaning things up

* htpasswd loc

* restore gatsby package.json

* adjust ignore files

* gatsby-dev-cli: ignore tests

* remove extra ln

* less console output

* turns out you don't need htpasswd after all

* use exact when installing local packages  - timestamp is used in version

* why it failed?

* use yarn for publishing - see verdaccio/verdaccio#997

* v0.1.1

* add temporary .npmrc file to allow anonymous publishes

* add some jsdocs

* update yarn.lock

* oops

* debug why still can't publish anon

* adjust npmrc content

* doh

* Revert "debug why still can't publish anon"

This reverts commit fc1045a.

* handle package installation of deps didn't change

* skip version changes for packages in gatsby mono-repo, queue copying instead of doing it immediately

* fix tests

* packages stored in verdaccio storage seems to be picked up by jest and causing trouble, so let's ignore verdaccio storage directory

* bye "wat", you will be missed

* bail early to avoid conditional bracket hell

* more bailing early

* more concise

* new line

* use exaca to simplify running yarn

* clean up www/.gitignore

* handle not existing packages

* remove unused (was needed for basic auth)

* cleanup temp file changes when process exit in middle of publishing

* ops

* Apply suggestions from code review

Co-Authored-By: pieh <misiek.piechowiak@gmail.com>

* cleanup unpkg response handler

* move stuff around

* remove tmp comment

* document traversePackageDocs fn

* restrcuture files

* add basic tests for traversingPackageDeps

* add basic tests for generating packages to publish (based on dep graph)

* fix tests on windows

* handle circular dependencies when constructing list of packages to publish

* remove cat ;(

* restore original e2e-test script

* update gitignore

* chore(release): Publish

 - babel-plugin-remove-graphql-queries@2.6.3
 - babel-preset-gatsby@0.1.11
 - gatsby-dev-cli@2.4.13
 - gatsby-plugin-typescript@2.0.12
 - gatsby-source-shopify@2.0.23
 - gatsby@2.3.6

* chore(release): Publish

 - gatsby-dev-cli@2.4.14

* docs(gatsby-dev-cli): Edit README (#13049)

* Build out Gatsby media information in docs (#12906)

* add video info, delete unnecessary stubs

Related to #12903

* fix internal link for html5 video section

* update videoTitle example

Co-Authored-By: marcysutton <holla@marcysutton.com>

* Apply suggestions from code review

thanks for the feedback!

Co-Authored-By: marcysutton <holla@marcysutton.com>

* incorporate feedback, make into real docs!!

* delete unused stubs

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <holla@marcysutton.com>

* Update docs/docs/working-with-video.md

Co-Authored-By: marcysutton <holla@marcysutton.com>

* chore(gatsby): fix domready package to be compatible with ie10 (#13027)

* changed domready package to domready-loaded which is compatible with ie10

* updated domready to @mikaelkristiansson/domready

* updated packages/gatsby to use @mikaelkristiansson/domready

* chore(release): Publish

 - gatsby@2.3.7

* feat(gatsby-transformer-react-docgen): use local babel config for react-docgen (#12001)

* feat: use local babel config for react-docgen

BREAKING CHANGE: now uses the local babel config with a fallback

* Update README.md

* chore(release): Publish

 - gatsby-transformer-react-docgen@4.0.0

* chore(docs): add “Why I used GatsbyJS (#12954)

Why I used GatsbyJS

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

<!-- Write a brief description of the changes introduced by this PR -->

## Related Issues

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->

* feat(www): don't check for overview frontmatter (#13060)

Fixes `[[guidelist]]` not being replaced in few pages (i.e. in https://www.gatsbyjs.org/docs/winning-over-stakeholders/ )

The code is handling cases when there are no children (tried building locally and it worked just fine).

Follow up to this would be to clear `.md` files that use `overview` and adjust page query. But this is just quick fix.

* chore(docs): add starter library to docs sidebar under starters (#12963)

 40% of people visiting the starters page go here next, so we should probably add this:

![image](https://user-images.githubusercontent.com/4388699/55285012-58d26180-5337-11e9-9259-68e81b4894ad.png)

* chore(showcase): Add gmartinez.dev to showcase (#13067)

<!--
  Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or
  ask in this Pull Request and a Gatsby maintainer will be happy to help :)
-->

## Description

Adding gmartinez.dev to showcase list in site.yml

<!--
  Link to the issue that is fixed by this PR (if there is one)
  e.g. Fixes #1234, Addresses #1234, Related to #1234, etc.
-->


Co-authored-by: Lennart <lekoarts@gmail.com>

* fix(gatsby): don't try to statically analyze gatsby-node, require it and examine exports instead (#13053)

* fix: don't try to statically analyze gatsby-node, require it and examine exports instead

* differentiate test names

* Update packages/gatsby/src/bootstrap/resolve-module-exports.js

Co-Authored-By: pieh <misiek.piechowiak@gmail.com>

* chore(release): Publish

 - gatsby@2.3.8

* Use Loki's elemMatch operator (#13025)

* feat(gatsby): add util.promisify polyfill for older node version (#13024)

* refactor(gatsby): gatsby develop: cleanup port detection (#13006)

* chore(release): Publish

 - gatsby@2.3.9

* fix(gatsby): ignore __esModule export in gatsby-node exports (#13081)

I introduced bug/regression in #13053 by not removing `__esModule` export name from resolved export names - it break some plugins

Fixes: #13079

* chore(release): Publish

 - gatsby@2.3.10

* fix(www): Hubspot form UI (#13080)

* fix(www): Work around HubSpot’s CSS being loaded

…by pulling in react-hubspot-form locally, and modifying it slightly. See comment in `www/src/components/react-hubspot-form` for more info.

* Fix `formInput` styles

… now matching the reference homepage newsletter form — no more Futura PT for input text.

* Return nothing because linter

* Make into Two Words

* Fix Comma Usage; Misc Updates (#13090)

Hopefully fix a code formatting issue when in a highlighted section.

* Fix Comma Usage; Misc Update (#13103)

* chore: format
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Issue that doesn't require previous experience with Gatsby help wanted Issue with a clear description that the community can help with. stale? Issue that may be closed soon due to the original author not responding any more. type: documentation An issue or pull request for improving or updating Gatsby's documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants