* 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
* 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
* fix(unicode-to-char): Replaced other languages unicode to text
* fix(unicode-to-char): run prettier to fix lint error
* feat(unicode-to-char): modified the replace function with p1 parameter
* Added language selector page
* PR nits
* Fix typo in variable name
* Added language icon. Show search icon in mobile.
* Tweaked header alignment
* Split languages into 3 categories based on progress:
complete, partially translated, and needs contributors
* Lower-cased pt-* language codes
* Re-added locale sort
* Renamed 'Partially Translated' header to 'In Progress'
* Specify articleLayout.container to flex in column direction
* articleLayout.container.flexDirection=column when media less than small
* Comply with eslint rules
This matters for user security.
I didn't touch blog posts & pages related to past conferences.
The `content/docs` could be HTTPS-ified as well but it contains lots of HTTP
links so maybe that'd be best done in a separate PR.
Fixes#1088
This should fix the path issues that people intermittently run into.
Gatsby sees the relative path (and the parent node with an absolute
path), joins on the parent path and the relative path, and presumes it's
a file... which is normally good, but which here is not what we want
beacuse then we're getting a resolver of type file instead of type
string referring to the relative path of the document.
This seems to fix a (long standing?) bug where the "Edit this Page"
button is broken, as well. e.g. see [this page](https://reactjs.org/community/support.html) which _should_ have an Edit this Page button
I'd need to think more as to whether there's a cleaner fix here, but
this seems to work pretty well!
Brian Vaughn
Sunil Pai
Monica Powell
George Véras Valentim
Abdelrahman Rifai
Stepan
Camilo Giraldo
Dan Abramov
Nelson Reitz
Farhad Yasir
Nat Alison
Brian Vaughn
Saransh Kataria
Nurul Sundarani
Michał Gołębiowski-Owczarek
Nikhil Erkimutt
Andrew Clark
Jack Cross
Jane Manchun Wong
Sophie Alpert
Sophie Alpert
Dustin Schau
Dustin Schau