Summary

Recently, I made the PR using GitHub's web interface to edit the Gatsby docs markdown file directly. However, in order for it to pass and be approved, I had to fix linting. To do this, I needed to pull down the repo, run the linter, then update my PR.

I didn't mind doing this at all, but I think this process could be improved.

If someone wants to update the docs, they should be able to do so by directly editing the file and submitting a PR.

Relevant information

I spoke with @shannonbux and she suggested I start a discussion around this idea of improving the contributing process for Gatsby.

Proposed Solution

Maybe we could modify the linting process to ignore Markdown files? Or somehow have a way for the contributor to run the linter within the browser?

I'm probably lacking more information but throwing these ideas out there.

Hi,
When running gatsby develop or build most of the time it will fail on the first try and then without any code changes running the same command after will build successfully.

I am writing my own source plugin so maybe I am missing a step but during the development process before I implemented page queries, the builds will always compile and I could query the schema. I would then transfer the query from graphiql to in page query and I would get build errors.