* Always use PROJECT_NAME, even for user and org pages
The symptom was that if we had a user or org page (e.g., https://JoelMarcey.github.io), we would try to copy files to a directory within a directory, getting errors like:
```
Error: Copying build assets failed with error 'Error: Cannot copy '/Users/joelm/dev/JoelMarcey.github.io/website/build' to a subdirectory of itself, '/Users/joelm/dev/JoelMarcey.github.io/website/build/JoelMarcey.github.io-master'.'
```
This is because we were setting the end of `fromPath` to empty if we were using an org or user page.
But we don't need to do that. The `PROJECT_NAME` (set in `siteConfig.js` as `projectName`) is the user or org repo
e.g., https://github.com/JoelMarcey/JoelMarcey.github.io/ has a `projectName` of `JoelMarcey.github.io` with an `organizationName` of `JoelMarcey`.
So now the `fromPath` and `toPath` look like:
`fromPath`: `build/JoelMarcey.github.io`
`toPath`: `buuid/JoelMarcey.github.io-master`
By convention both BuckleScript and ReasonReact are PascalCase. Also removed BuckleScript from fbOpenSource because it's not technically under that umbrella.
* 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.
