* Adding survey banner for community
* fixing up a kludge for the banner, making the graphic look less like swearing
* updating banner start date
* make the banner smaller
* Close as a button
* fixes
* Remove the arrow
* Updating image sizes, making the arrow do a little slide
* Revert "Remove the arrow"
This reverts commit 3dddae8108.
* Remove extra space
* Legibility tweaks
* Fixing border radius
* Making close button a real button
* Remove trailing space, plz don't re-add, Prettier
* Centering that banner
* Modified Survey header styles
* Inline Banner content at the usage site
* Fix flash by using CSS variables
Co-authored-by: Dan Abramov <dan.abramov@me.com>
Co-authored-by: Brian Vaughn <bvaughn@fb.com>
* Fix Navbar covering heading while using anchor in docs
* reduced number of lines of code from 2 to 1
* Forgot to do tests before. Have done those now with no errors
As per https://twitter.com/sliminality/status/1269033413488459776, there's feedback that the contrast isn't great for reading. I myself have trouble with low contrast text, (and long sightedness), and I thought it was fine. I was clearly mistaken. Removing this for now to get back to a non harmful position, and we can decide later what to do instead.
* manifest config added and src/images/react_logo.png added for icon
* inverted commas fix as per linter
* added legacy:true option for ios
* legacy:true lint fix
* added meta tags for ios and moved logo from src to static
* Move footer and header links into a YAML file
* Import header and footer nav YAML files directly
- Remove them from section list
- Add keys to nav array items when mapping
* Add flow error supression for YAML imports
* 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
