Some css variables such as banner were defined, but header css variables
were not, and layout margins were written solidly without css variables.
The layout was broken (to the extent that it was not visible), so it was
corrected.
* Adding Social Banner with Support for Ukraine
* Changing spacing the social banner
* Fixing lint errors
* Remove external link icon from social banner
* Add banner for beta site
* Add todo
* Fix centering on mobile in old site
Co-authored-by: Rick Hanlon <rickhanlonii@gmail.com>
* 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>
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.
* 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(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'
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!
