Feature request: privacy statement and imprint

[schuettloeffel-elsa]

closes #297

• Added Imprint and Privacy links to footer
• Implemented fetching of imprint and privacy html files
• Translated both terms to all languages
• Added test files
• also see backend PR: Feature request: privacy statement and imprint opencast#5674

[Arnei]

Played around with this a bit and what can I say, it works 👍 I'll let others comment on whether the design of the pages is in line with the admin ui design docs, and instead raise some discussions points about technical stuff below.

I would prefer if we could avoid using user-generated HTML and JSON or some other form of string map instead. This would allow us more control in the frontend to ensure everything looks well, users don't have to fiddle around with HTML, and we could get some stuff like "Tel." or "Fax" translated in the frontend so users don't have to.
But I am also not at all knowledgable about the requirements for imprints and privacy statements, so if you say they absolutely require this degree of flexiblity I'm fine with it.

[schuettloeffel-elsa]

I would prefer if we could avoid using user-generated HTML and JSON or some other form of string map instead. This would allow us more control in the frontend to ensure everything looks well, users don't have to fiddle around with HTML, and we could get some stuff like "Tel." or "Fax" translated in the frontend so users don't have to. But I am also not at all knowledgable about the requirements for imprints and privacy statements, so if you say they absolutely require this degree of flexiblity I'm fine with it.

In my experience at least the privacy statements need that degree of flexibility since they are highliy unique per organization and would be almost impossible to be generalized into a template of some kind (e.g. some organizations use kind of tables in their privacy statements to visualize data access).

[Arnei]

I would prefer if we could avoid using user-generated HTML and JSON or some other form of string map instead. This would allow us more control in the frontend to ensure everything looks well, users don't have to fiddle around with HTML, and we could get some stuff like "Tel." or "Fax" translated in the frontend so users don't have to. But I am also not at all knowledgable about the requirements for imprints and privacy statements, so if you say they absolutely require this degree of flexiblity I'm fine with it.

In my experience at least the privacy statements need that degree of flexibility since they are highliy unique per organization and would be almost impossible to be generalized into a template of some kind (e.g. some organizations use kind of tables in their privacy statements to visualize data access).

Unfortunate, but oh well, it's just like that sometimes :D. In that case I'm fine with approving this once you get around to the other comments.

[schuettloeffel-elsa]

Sorry for the delay, had lots of other stuff to do, I addressed all your concerns-

@Arnei: can you have a look now?
@gregorydlogan: I implemented a switch to turn on/off both Footer Elements, you can configure it in org.opencastproject.admin.display_about in the me.json file.

[github-actions]

This pull request has conflicts ☹
Please resolve those so we can review the pull request.
Thanks.

[ziegenberg]

I did a production build run and found some warnings.

[schuettloeffel-elsa]

Thanks, commitet your suggestions