fix(docs): Update anchor titles and text for accessibility (#13678)

* Update anchor titles and text for accessibility * Add note to style guide about titles in hyperlinks
gatsbyjs · Apr 29, 2019 · ea0cf69 · ea0cf69
1 parent b0ed584
commit ea0cf69
Show file tree

Hide file tree

Showing 16 changed files with 105 additions and 95 deletions.
diff --git a/...og/2017-10-20-from-wordpress-to-developing-in-react-starting-to-see-it/index.md b/...og/2017-10-20-from-wordpress-to-developing-in-react-starting-to-see-it/index.md
@@ -8,20 +8,20 @@ tags: ["React", "getting-started", "wordpress"]
 As a frontend designer I've always prided myself on being a HTML and CSS
 specialist. My use of JavaScript has been limited to animations and DOM
 manipulation. However, at
-[Indigo Tree](https://indigotree.co.uk "Indigo Tree: We Build Awesome Websites")
+[Indigo Tree](https://indigotree.co.uk)
 we're branching out from our staple of WordPress and trying different methods of
 creating websites with functionality that our clients require, whilst maximising
 their budget.
 
 We're also bracing ourselves for what we’re anticipating to be the stormfront of
-[Gutenberg](https://wordpress.org/plugins/gutenberg/ "Gutenberg WordPress plugins")
+[Gutenberg](https://wordpress.org/plugins/gutenberg/)
 for our WordPress projects. Once it's included in the WordPress Core, writing
 components in JavaScript for the Gutenberg editor will be necessary for every
 developer on a project.
 
 So I decided to dive into learning React with a few courses and some
 experimentation. I had the aim of building a site in
-[Gatsby.js](/ "Blazing-fast static site generator for React")
+[Gatsby.js](/)
 as a test for doing projects built entirely in React.
 
 ## Letting Go
@@ -88,7 +88,7 @@ Beautiful.
 ## GraphQL: SQL-like data queries
 
 One thing I particularly love about Gatsby.js is its inclusion of
-[GraphQL](http://graphql.org/ "A query language for your API"). Like SQL, you
+[GraphQL](http://graphql.org/). Like SQL, you
 use GraphQL to query your data, whether from the WordPress API, Contentful or
 Markdown, and extract a dataset to display in your template.
 
@@ -133,7 +133,7 @@ focus on context without having to grok SCSS again, reducing mental friction.
 Following the [tutorial on Gatsbyjs](/tutorial/) I built
 up my project from scratch, breaking things profusely at first, but it honestly
 didn’t take long to gain confidence enough so that I launched my first site at
-[freebabylon5.com](https://freebabylon5.com "Our last, best hope of getting back on the air")
+[https://freebabylon5.com](https://freebabylon5.com)
 recently.
 
 Be warned: the tutorial isn’t quite finished yet, you might be better off
@@ -154,17 +154,17 @@ and others) for a faster, more efficient development experience.
 I'm glad to say I'm sold on the idea and methods of developing with JavaScript,
 and React in particular. The site I've re-built from WordPress into Gatsby.js is
 now live at
-[https://freebabylon5.com](https://freebabylon5.com "Our last, best hope of getting back on the air").
+[https://freebabylon5.com](https://freebabylon5.com).
 
 Together with my colleagues at
-[Indigo Tree](https://indigotree.co.uk "Indigo Tree: We Build Awesome Websites")
+[Indigo Tree](https://indigotree.co.uk)
 we’re now looking at using WordPress as a backend, where clients can edit their
 content without the worries of insecure plugins or other methods of being
 hacked.
 
 Using GatsbyJS with its “Bring Your Own Data” strategy makes perfect sense, and
 we’re about to start building our first Gatsby client site using the plugin
-[`gatsby-source-wordpress`](/packages/gatsby-source-wordpress/ "WordPress content into Gatsby")
+[`gatsby-source-wordpress`](/packages/gatsby-source-wordpress/)
 to pull in our data and build a totally secure website with some pretty
 impressive gains on loading time. We’ll also sleep better at night knowing
 insecurities in WordPress are no longer putting our clients at risk.

diff --git a/docs/blog/2017-11-08-migrate-from-jekyll-to-gatsby/index.md b/docs/blog/2017-11-08-migrate-from-jekyll-to-gatsby/index.md
@@ -55,9 +55,8 @@ blog with a theme I added [Tachyons](http://tachyons.io/). I managed to
 replicate 99% of my previous theme with classes from Tachyons. Something that I
 would like to do better is to remove the parts of Tachyons that I’m not using.
 
-My current CSS file has less than 30 lines. The rest of the layout is created
-with tachyons classes:
-[https://github.com/singuerinc/blog/blob/master/src/layouts/index.css](https://github.com/singuerinc/blog/blob/master/src/layouts/index.css)
+[My current CSS file](https://github.com/singuerinc/blog/blob/master/src/layouts/index.css) has less than 30 lines. The rest of the layout is created
+with tachyons classes.
 
 ### Slug + Date
 
@@ -133,9 +132,8 @@ Some key points:
   into the [`gatsby-plugin-feed`](/packages/gatsby-plugin-feed/) to recreate the
   Atom Feed)
 - React and GraphQL for free with Gatsby
-- Since I am confident with the Node ecosystem I'm able to contribute: First
-  pull request to Gatsby:
-  [https://github.com/gatsbyjs/gatsby/pull/2569](https://github.com/gatsbyjs/gatsby/pull/2569)
+- Since I am confident with the Node ecosystem I'm able to contribute: [First
+  pull request to Gatsby](https://github.com/gatsbyjs/gatsby/pull/2569)
 - Netlify vs GitLab Pages (hopefully 100% uptime)
 
 ## Final thoughts
@@ -145,10 +143,8 @@ completely changed. For me it is a whole new experience—easier, and faster.
 
 I wanted to move the blog to Node a long time ago and it is finally there!
 
-Next is to convert my portfolio (also built with Jekyll):
-[https://www.singuerinc.com/](https://www.singuerinc.com/)
+Next is to convert [my portfolio](https://www.singuerinc.com/) (also built with Jekyll).
 
 ## Show me the code
 
-If you want to take a look at the code you can do it, it is published in GitHub:
-[https://github.com/singuerinc/blog](https://github.com/singuerinc/blog)
+If you want to take a look at [the code](https://github.com/singuerinc/blog) you can do it, it is published in GitHub.
diff --git a/docs/blog/2018-02-28-documentation-project/index.md b/docs/blog/2018-02-28-documentation-project/index.md
@@ -63,4 +63,4 @@ If you'd like to contribute, look through this list of options and pick one that
 
 - Go to [Issue #4175](https://github.com/gatsbyjs/gatsby/issues/4175) to help enhance the tutorials.
 - If you’d like to contribute to and/or follow other documentation projects, go here to find the [Documentation Project](https://github.com/gatsbyjs/gatsby/projects/3).
-- And, as always, if you have time to give us feedback on what you like about Gatsby and what can be improved in the docs/tutorials, schedule a time to chat with me here! [https://calendly.com/shannon-soper](https://calendly.com/shannon-soper)
+- And, as always, if you have time to give us feedback on what you like about Gatsby and what can be improved in the docs/tutorials, [schedule a time to chat with me here](https://calendly.com/shannon-soper)!
diff --git a/docs/blog/2018-07-17-announcing-gatsby-preview/index.md b/docs/blog/2018-07-17-announcing-gatsby-preview/index.md
@@ -29,7 +29,7 @@ Over the next few months, we’ll be adding integration with other CMSs like Dru
 
 We’re incredibly excited to launch our first commercial service and to continue to push forward the Gatsby experience! We’re looking forward to meeting more of you and working together to push forward the modern web.
 
-Before you go, take a look at a GIF of Gatsby Preview in action on our own [https://wwww.gatsbyjs.com](https://gatsbyjs.com) website:
+Before you go, take a look at a GIF of Gatsby Preview in action on [our own website](https://gatsbyjs.com):
 
 <video controls="controls" autoplay="true" loop="true">
   <source type="video/mp4" src="./gatsby-contentful-preview.mp4"></source>

diff --git a/docs/blog/2018-07-31-docs-redesign/index.md b/docs/blog/2018-07-31-docs-redesign/index.md
@@ -105,7 +105,7 @@ Want to volunteer to write one? Check out all the stub articles (titles in _ital
 
 Want to sign up for a 45 minute usability test of the new structure? (It will likely take 20-30 minutes, and I blocked out 45 minutes in case you have questions and more commentary. I'll close the sign-up link once I get 5 people who sign up.
 
-- Sign up here: [https://calendly.com/shannon-soper/new-ia-usability-test/07-30-2018](https://calendly.com/shannon-soper/new-ia-usability-test/07-30-2018)
+- [Sign up here](https://calendly.com/shannon-soper/new-ia-usability-test/07-30-2018)
 
 ### Issues to be resolved
 

diff --git a/docs/blog/2018-2-7-jam-out-your-blog/index.md b/docs/blog/2018-2-7-jam-out-your-blog/index.md
@@ -37,7 +37,7 @@ _**Let’s get into it.**_
 - **NO WordPress** - similarly, I don’t want to deal with updates, themes, hacks...etc
 - **Continuous Deployment** - the site needs to always be up and running and current
 
-For the sake of brevity, let's infer that speed, development experience, scalability and lack of WordPress will be handled by Gatsby and the JAMstack. If you’re unfamiliar, take a look at [http://jamstack.org/. ](http://jamstack.org/)
+For the sake of brevity, let's infer that speed, development experience, scalability and lack of WordPress will be handled by Gatsby and the JAMstack. If you’re unfamiliar, take a look at [http://jamstack.org/](http://jamstack.org/).
 
 ## CMS-Induced Headaches
 

diff --git a/docs/blog/2019-02-05-hapticmedia-case-study/index.md b/docs/blog/2019-02-05-hapticmedia-case-study/index.md
@@ -12,7 +12,7 @@ image: "images/hapticmedia.jpg"
 showImageInArticle: true
 ---
 
-[Hapticmedia](https://hapticmedia.fr/en/ "Hapticmedia"), a creator of 3D product configurators, has been at the cutting edge of retail and e-commerce for four years. But their existing website wasn’t the best showcase of their technological prowess. When the company started, they built their website with Wordpress because that was easiest, and they had bigger things to worry about. But over time, the WordPress site became slow, difficult to update, and prone to breaking down. And as the company grew, they needed a site that could expand with them. Using Gatsby for their website rebuild meant greater stability, faster load times, and more scalability. They had initial concerns over whether a static site generator could successfully incorporate dynamic elements, but this proved not to be a problem.
+[Hapticmedia](https://hapticmedia.fr/en/), a creator of 3D product configurators, has been at the cutting edge of retail and e-commerce for four years. But their existing website wasn’t the best showcase of their technological prowess. When the company started, they built their website with Wordpress because that was easiest, and they had bigger things to worry about. But over time, the WordPress site became slow, difficult to update, and prone to breaking down. And as the company grew, they needed a site that could expand with them. Using Gatsby for their website rebuild meant greater stability, faster load times, and more scalability. They had initial concerns over whether a static site generator could successfully incorporate dynamic elements, but this proved not to be a problem.
 
 ## The Trouble with Troubleshooting