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.

Sign up for GitHub

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 define acronyms (RFC and SEO) #19148

Merged
merged 5 commits into from
Oct 30, 2019
Merged

Docs define acronyms (RFC and SEO) #19148

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d6b66bc
add RFC definition on contributor docs
Oct 30, 2019
4ed43ae
add SEO acronym definition
Oct 30, 2019
5f731c9
Update docs/contributing/gatsby-style-guide.md
laurieontech Oct 30, 2019
785be6a
remove acronym from header
Oct 30, 2019
907760d
keep header, but change first sentence
Oct 30, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/contributing/gatsby-style-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,7 @@ If you want to abbreviate a term in your article, write it out fully first, then
put the abbreviation in parentheses. After that, you may use the abbreviation going for the rest of the article. For example, "In computer science, an
abstract syntax tree (AST) is ..."

### Use SEO optimized titles
### Use Searcg Engine Optimization (SEO) optimized titles
laurieontech marked this conversation as resolved.
Show resolved Hide resolved

This explains how to create a doc that shows up in search engines like Google or Bing.

Expand Down
2 changes: 1 addition & 1 deletion docs/contributing/managing-pull-requests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Some general things to verify in a pull request are:

- Links ought to be relative instead of absolute when linking to docs (`/docs/some-reference/` instead of `https://www.gatsbyjs.org/docs/some-reference/`)
- Language ought to be inclusive and accessible
- Issues and RFCs (if any) that this PR addresses ought to be linked to
- Issues and Requests for Comments (RFCs) (if any) that this PR addresses ought to be linked to

> 💡 When looking at a PR for the first time, it can help to read up on linked issues or [RFCs](/contributing/rfc-process/) (if there are any) to gain context on what the PR intends to add or fix.

Expand Down