5304873feb
English is a better starting point for a good translation than the current translation; if we need to look again we can check git history. I did some translation a number of months ago ago, but figured it would be best to put that in the next PR to avoid getting hung on up the translation not being perfect.
Zaimki.pl / Pronouns.page
Installation
git clone git@gitlab.com:Avris/Zaimki.git
We're using FontAwesome Pro, so to set up a local copy without having a FA license,
open package.json and replace
"@fortawesome/fontawesome-pro": "git+ssh://git@gitlab.com:Avris/FontAwesomePro.git",
with
"@fortawesome/fontawesome-pro": "git+ssh://git@gitlab.com:Avris/FakeFontAwesomePro.git",
Do not commit that change!
Build Setup
# install dependencies
$ make install
# configure environment
$ nano .env
$ make switch LANG=pl
# serve with hot reload at localhost:3000
$ make run
# build for production and launch server
$ make deploy
$ nuxt start
Copyright
See LICENSE
Development Documentation
Read https://en.pronouns.page/new-version
When you add a new language, remember to modify the file ./src/locales.js to add your language. true means the translation is finished and published, so you'll probably want to go with false.
If you're having problems using Yarn, npm is probably fine, but remember to switch any yarn [x] commands for npm run [x]
Remember to modify the ./.env file. You don't really need to set up any external APIs, just make up a secret. In order to test the login system, you can type in an email followed by a + (example@pronouns.page+). This way, you won't need a mailer, as the code will always be 999999. This feature is exclusive to development builds.
Current translations being worked on
- Catalan - @peiprjs
- [Add yours!]