* Add lang and hreflang for screen reader UX
I wanted to add `lang` and `hreflang` to the link element for translated languages. `Lang` is used by screen readers to switch language profiles to provide the correct accent and pronunciation.
>If you have multiple versions of a page for different languages or regions, tell Google about these different variations. Doing so will help Google Search point users to the most appropriate version of your page by language or region.
> Note that even without taking action, Google might still find alternate language versions of your page, but it is usually best for you to explicitly indicate your language- or region-specific pages.
Source: https://support.google.com/webmasters/answer/189077?hl=en
* add hrefLang and Lang attributes
* add alternate pages to head
* Apply suggestions from code review
Co-Authored-By: Alexey Pyltsyn <lex61rus@gmail.com>
* mark english hreflang as x-default
* make english the default on the languages page
* rethink default-x
The previous phrase "plugging out" is uncommon in English. Saying "disconnecting" is better than "unplugging" because many mouse users have wireless mice, and is more accurate.
AppSeed is a FullStack Web App Generator that allows you to choose a visual theme and apply it on a full, but flexible, technology stack in just a few minutes. The app generator can be used without an account. Read more: https://AppSeed.us
* inputs array > dependencies array
I think initially this was referred to as the "inputs array" in the docs, then it was changed to the "dependencies array" everywhere except it looks like a few were missed.
* inputs array > dependencies array
I think initially this was referred to as the "inputs array" in the docs, then it was changed to the "dependencies array" everywhere except it looks like a few were missed.
* previous page link is not linking to the previous page, but to the second last.
The example code is on both, the `Introducing Hooks` as well as `Hooks at a Glance` page, but the linked page is the `Introducing Hooks` and I think that's the right one (the `Hooks at a Glance` page probably got added later?).
Not sure about the phrasing so, having "introduce" twice in one sentence ...
* Update content/docs/hooks-state.md
Co-Authored-By: 0xnoob <49793844+0xnoob@users.noreply.github.com>
Co-authored-by: Alexey Pyltsyn <lex61rus@gmail.com>
The link should probably either go to directly to the beginning of main concepts (which is what my proposes change does), or to the anchor -tag of "Step-by-Step Guide" (#step-by-step-guide). There is no other link in the article which refers to another anchor-tag, that's why I chose to directly link to the main-concepts.
* Fix anchor link offset with fixed header
* handle h3 too
* h4 as an anchor
* don't affect UI by any means
* no need for px
* more fixes
* consistency
* more consistency
* pixel perfection
* fix h4 after gatsby-highlight
* final touch
When copy and pasting `npm install jest-cli —save-dev` you get this error
`Invalid tag name "—save-dev": Tags may not have any characters that encodeURIComponent encodes`
I replaced the unicode characters '—' with ascii hypens '-'
