🔧 [Refactor] Terms And Conditions Version Agreed For Use In Rebranding

[Tirokk]

🔧 Refactor

Terms And Conditions version agreed for the use in rebranding.

Todo

• show terms and conditions version number explizit in the agree VueJS component: webapp/pages/terms-and-conditions-confirm.vue
• add on the following files terms and conditions version number explizit and add comment that this number is administered really at rebranding:
  • webapp/locales/html/de/code-of-conduct.html
  • webapp/locales/html/en/code-of-conduct.html
  • webapp/locales/html/de/data-privacy.html
  • webapp/locales/html/en/data-privacy.html
  • webapp/locales/html/de/terms-and-conditions.html
  • webapp/locales/html/en/terms-and-conditions.html
• in the rebranding repo create an issue for replacing the file webapp/constants/terms-and-conditions-version.js by copy the rebranded version number file into the Docker image. done by 💥 [DevOps] Use Terms And Conditions Version In Rebranding Ocelot-Social-Deploy-Rebranding#34

Additional Todo

• Put style in one separate style file used and imported in all HTML files in webapp/locales/html and import it in all this files. Use possibly one style file per language folder to have always the same import path.

If you do this not then create an own issue.

Question

May set the Terms And Conditions version via the admin setting?
See Yunite Issue Yunite-Net/yunite.me2#24