* enhance footer with social media buttons
* Update api-site-config.md
* Update Footer.js
* fix minor issue on social-footer
* update facebookAppId description in api-site-config
* rm heading & pad footer social button
* Update api-site-config.md
* migrating to react 16
* Add WarriorJS to Docusaurus users (#656)
* Separate users data from code
* Add WarriorJS to Docusaurus users
* [Feature] Introducing image compression using imagemin (#654)
* Introduce imagemin for compressing images
* Replace original images with the optimized ones
* Add imagemin-svgo to dependencies
* Remove console statement, replace let with const
* Replace let with const
* Add --skip-image-compression
* Run Prettier
* Fix header
* Prettier
* Rename authorImage to authorImageURL for clarity
Update documentation
* Fix typo
* Add documentation for authorImageURL
* Add support for authorImage
We will remove support for authorImage in favor of authorImageURL, after we remove authorImage from react-native-website
* Update guides-blog.md
* Update guides-blog.md
Even if we were on Spanish pages, it still showed English in the Header nav.
This makes it so that the Header nav shows the currently selected language.
* Add input title to improve a11y
Resolves pa11y error:
```
• Error: This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.
├── WCAG2AA.Principle1.Guideline1_3.1_3_1.F68
├── #search_input_react
└── <input type="text" id="search_input_react" placeholder="Search" aria-label="Search" class="aa-input" autocomplete="off" spellcheck="false" role="combobox" aria-autocomplete="list" aria-expanded="false" aria-labelledby="search_input_react" aria-owns="...
```
* Fix Prettier failure on Circle CI
* Versioning ids should be based on whether translation is enabled
Ref: ff117979c6 and a5e963dba1
Tested locally on:
Docusaurus
Relay
Test site from `npm run examples`
* Prettier
* without having having to worry about site design.
Let me know if double having is intentional
* distinguish case of no translation and en lang
* prettier recommends
* distinguish case of no translation and en lang
* prettier recommends
* merge with latest origin/master changes
* typo
* link with language fixes
* do not show language dropdown if only one enabled
* check translation outside of LanguageDropDown.render
* without having having to worry about site design.
Let me know if double having is intentional
* distinguish case of no translation and en lang
* prettier recommends
* distinguish case of no translation and en lang
* prettier recommends
* merge with latest origin/master changes
* typo
* Do not show users related UI if no users have been specified
* Fixed typo in Docusaurus homepage link
* Allow projects without icons
Not every project has an icon, so avoid showing a broken image in that case.
* Do not show project icon in the footer if there's no footer icon
Google Chrome guesses the language if this is not present. Large quantities of source code can confuse it and lead to it selecting completely the wrong language.
