5991a21818
* First batch of changes for the refactor
Added the support of gin in routes and other services/utils
Begining implementation of JetHTML
* Remove os folder
* Move scrapers to own repo
* Second batch of changes
All .jet.html are the working templates.
You can now test this PR, the index Page and upload works. If you want to complete the other html templates, you're welcome
* Move captcha to util
* Move uploadService to utils
* Use govalidator instead of regex
* Third batch of changes
All the front end should as previously.
I also fixed some minor things unrelated to the refactor (mostly style issues on static pages)
Now errors can be accessed by importing the "errors" helpers and using the `yield errors(name="xxx")` command in templates.
Same for infos.
Templates are now more hierarchized with a base template "base.jet.html" which is extended depending on the context in "index_site" or "index_admin" layouts. Those layouts are extended than in every pages.
Other helpers are captcha to render a captcha `yield captcha(captchaid="xxx")`
And also csrf, with the command `yield csrf_field()`
To translate, you don't have anymore to do `call $.T "xxx"`, you just have to do `T("xxx")`.
Pages for the website part are in folders in the folder "templates/site". Pages for the admin part are in "templates/admin". Layouts are separated in "templates/layouts". Helpers and menu are in "templates/layouts/helpers" and "templates/layouts/menu". Error pages should be put in "templates/errors"
* Added test on templates
When adding a new template, you have to tell to template_test.go, the context of the new template (if it doesn't use the common context)
* Panel admin works
Now the templating part should work. The PR can now be fully tested.
I think we should push the templating PR and do the routes/controllers/removal of services in another branch. So we know that this one is functional
* Updated dependencies
* Fixed test for modelhelper
* Fix testing for commentlist
* Fix travis :')
* Just renamed router and removed network
* Applying same SEO fix
* Update form_validator.go
* Added back regexp package
|
||
|---|---|---|
| .. | ||
| ca-es.json | ||
| de-de.all.json | ||
| en-us.all.json | ||
| es-es.all.json | ||
| fr-fr.all.json | ||
| hu-hu.all.json | ||
| is-is.all.json | ||
| it-it.all.json | ||
| ja-jp.all.json | ||
| ko-kr.all.json | ||
| nb-no.all.json | ||
| nl-nl.all.json | ||
| pt-br.all.json | ||
| pt-pt.all.json | ||
| README.md | ||
| ro-ro.all.json | ||
| ru-ru.all.json | ||
| sv-se.all.json | ||
| th-th.all.json | ||
| zh-cn.all.json | ||
| zh-tw.all.json | ||
Contributing to translation
You can add your own language support or edit it easily to the website.
Add a language
To add a language you need to copy /translations/en-us.all.json and translate the strings beside the "translation" key. Do not edit "id" which is the id used to display the translation.
You can also, if you have the website installed, create an empty languageCode.all.json (eg. en-us.all.json) and use the following command:
cd translations && goi18n -flat false en-us.all.json languageCode.all.json you need to replace languageCode with the actual language code (eg. en-us)
A new file languageCode.untranslated.json will be created with the new translation strings. Translate them and when it's done, run the following command:
goi18n -flat=false en-us.all.json languageCode.all.json languageCode.untranslated.json you need to replace languageCode with the actual language code (eg. en-us)
After creating a new translation, create a new translation string inside "en-us.all.json", like the following:
...
},
{
"id": "language_(languageCode)_name",
"translation": "(your language name, in English)"
},
...
where languageCode is the newly created ISO code (eg. ja-jp, pt-br).
Before pulling, be sure to delete .unstranslated.json file
Edit a language
To edit a language you can keep tracking of new strings added to en-us.all.json with the use of git and add the new strings manually to your file.
Or you can also, if you have the website installed, use the following command:
cd translations && goi18n -flat false en-us.all.json languageCode.all.json you need to replace languageCode with the actual language code (eg. en-us)
A new file languageCode.untranslated.json will be created with the new translation strings. Translate them and when it's done, run the following command:
goi18n -flat=false en-us.all.json languageCode.all.json languageCode.untranslated.json you need to replace languageCode with the actual language code (eg. en-us)
Before pulling, be sure to delete .unstranslated.json file