* 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
* Add Prettier formatting to source files and example files, and check that Prettier formatting is maintained on PRs
* Remove trailing-comma as we are using Node 6 on Circle
* Use latest Node 6 LTS version in Circle
* Initial test suite
* Rename test to match original file
* restore test files
* Remove yarn.lock from pull request. Will run it again in a separate commit
* Fixes to testing guide (for Windows only)
* Fixed line ending detection for UNIX and Windows
* Removed incorrect instructions about translations
* Removed redudant heading and turned it into a note.
* 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
* without having having to worry about site design.
Let me know if double having is intentional
* sitemap display flex with direction as column on mobile
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.
* Add introductory blog post
For launch!
\o/
* Update post to launch date
* Add ogImage and fix how we get og:Description
Plus a few updates to the post
* Remove some code block info
* Ensure Edit this Doc links always point to the master source of truth, and not a particular version
* Only show Edit this Doc link if editUrl has been set
* Add Prettier formatting to source files and example files, and check that Prettier formatting is maintained on PRs
* Remove trailing-comma as we are using Node 6 on Circle
* Use latest Node 6 LTS version in Circle
* Remove unused test
