valid-void commented 3 years ago

Language switch strategy

branch: ' language '

DE/EN switch button

[x] create raw button

The button should:

[x] refresh the page
[x] effect the routing --> /en/... + /de/...
[x] change its appearance
[x] get a design
[ ] position of button within single pages

Define 2 environments

[x] set up routing --> /en/... + /de/...
[x] create service for easy implementation
[x] name the service 'language-api-switch.service'
[x] call routing (en / de) from router

Test run

[x] CMS: use exsisting 'Projekts' as collection type for english content as well
[x] implement language enum
[x] implement relation fields (de_equivalent, en_eqivalent)

After test run --> production mode

[x] repeat for 'Persektives' and 'Podcasts'

How should we handle podcast > single pages? Translate only the ones where they speak english?

Considering CMS

How do we handle 2 languages considering backend?

Within Strapi we can organize our EN content and DE content in two different ways. Either we create additional collection types (option 1) or we reuse the existing collection types (Projekts, Perspektives, Podcasts, Themes, Impressum).

Option 1

Projekts + EN_projects
Perspektives + EN_perspektives
Podcast + EN_podcast
Theme + EN_theme
Impressum + EN_impressum

Option 2

Projekts (DE+EN)
Perspektives (DE+EN)
Podcast (DE+EN)
Theme (DE+EN)
Impressum (DE+EN)

separated collection types	reusing same collection types
DE and EN are completely separated	DE and EN share the same collection
+ clear separation beforehand	- separation afterwords (graphql)
+ + easy to relate DE and EN version	- - relation within same collection is not possible
	solution: add text field and paste related link manually
- DE content can not be reused	+ DE content can be duplicated
- annoying to handling media files	+ easy to handle media files
- relations must be added from scratch	- - relations must be overwritten (careless mistake?)
- maintenance	+ maintenance

Hybrid useful?

Themes could be managed within the same post? e.g. Themes >

key: theme_name_DE
key: theme_name_EN

Impressum and menu maybe as well What about podcast? It does not contain so many information.

Questions:

How do we handle related projects/perspectives/podcasts? Can we reuse DE related projects/perspectives/podcasts within EN page?

Elements that needs to be translated:

CMS:

[x] Projekts
[x] Perspektives
[x] Podcasts
[x] Themes
[x] Impressum
[x] Programme
[ ] ? image captions (needs to be language neutral)

Angular:

[x] Menu
[x] about
[ ] about > add english version to HTML code
[x] footer
[ ] ? "Aus heutiger Sicht. Diskurse über Zukunft"

JSON files:

[x] generated questions
[ ] Team list > add english profression translation

No translation:

[x] podcast player --> anyway in German

clyptomania commented 3 years ago

Content Internationalization with Strapi

Translating content from a language to another has been requested by many of you. As you may have seen on our website, the Internationalization plugin is not available yet because we need to go out of alpha before developing new plugins. But, no worries, we have a good work around to help you internationalize your content! The solution is: suffix your fields.

https://medium.com/strapi/content-internationalization-with-strapi-507ef5869c15