Global Page Translation templates

svenseeberg commented 1 year ago

Motivation

For region managers it is often not easy to onboard additional editors. Therefore, text is often created in word documents instead of directly in the system. This is also due to lack of trust.

Proposed Solution

We need to make it easier for external contributors to create texts that fulfill basic requirements and can directly be used for Integreat. We can create (a simple) page template system that helps creating a text that is suitable for Integreat.

The network management needs a management for the templates. Templates consist of a name and a field for the HTML source code. We do not need a WYSIWYG editor here, as we can simply copy the source code from other pages.
The editor needs a new menu to choose from available templates and insert them into the current page. The text should be inserted at the current cursor position (and not overwrite existing page content). But usually it should be used in empty pages.
Languages can be ignored in the first iteration. The templates are available in all languages and the CMS does not know which language each template has. I expect that we will only have German templates at the beginning. If it turns out that languages are important, we can add the relation later and migrate the content with de as the default language.

Alternatives

N/A

Additional Context

Together with #316 editors can easily create a simple draft page and create an external link for external contributors to improve the text.

Design Requirements

N/A

svenseeberg commented 1 year ago

There is one open question: do we need a reference to a language in the templates? Maybe we don't. The title could be sufficient. And it also might be okay to use a template for the wrong language. For example it would probably be okay to use an English template for a German page if the editor can read English. And I don't think there are many real life scenarios were this would become an issue.

osmers commented 1 year ago

@svenseeberg yes, I think it is not really a relevant scenario - maybe it would be prudent to only have templates in the German page editor?

svenseeberg commented 1 year ago

I think we should keep it easy and ignore languages. We can introduce them later, if we have to.

osmers commented 1 year ago

I agree - also, it wouldn't be too difficult to just get them translated, right?

svenseeberg commented 1 year ago

Yes, we could do this with automatic translations. However, I would still initially keep the functionality as close to the bare minimum as we can. That means ignoring languages at the start and test if the feature is useful at all.

osmers commented 1 year ago

Sounds good to me :) now we just need to develop a template or two, right?

svenseeberg commented 1 year ago

They would be dynamic. That means we can enter them in the network management. But yes, in the end we would need them.

dkehne commented 10 months ago

i do not see that this is the solution for the mentioned problem. I would not develop such templates but start with https://github.com/digitalfabrik/integreat-cms/issues/316 and see how this improves the process already.

people who feel more comfortable to create some content on their local machine first, will always do that no matter how easy the cloud-solution is. this can only be changed by training and showing the benefits, not by using a more UI which is more simple.

dkehne commented 10 months ago

i will drop it from time schedule and suggest to close it...

svenseeberg commented 7 months ago

@osmers can you discuss Daniel's comment within the service team?

osmers commented 7 months ago

We discussed this and would like to close the issue but keep it as an idea, if possible...

digitalfabrik / integreat-cms