Organising the English Translation for Fabcity.Hamburg

Value Proposition

Providing a translated Fabcity.Hamburg Website for English speaking audience.

concept

The Translation of the Fabcity is done by

• simply copy and past a DE Page into folder "EN" with the translated content.

Discussion Points

• How do we link a translated Pages. We must know which translated pages belong together
• How do we track changes of Pages with a translated page to it?
  • Whenever any Page with one or more associate translated pages gets a change, the change must be indicated so that any editor person can check the related translated page, too.
• Fallback solution: We don't actually need one. Once we have a large number of Pages translated, we do then offer the EN Button / Page. The english page is only showing what has been translated.
• System Text: How to translate system text (e.g. Footer)
• Links in articles need to take care of, too. It can quickly happen that accidentally a link on a EN page still links to a DE Page. I wonder if there is a workflow that helps me check cross-language Links. Is a workflow that shows me all the links they point to making sense here?

Tutorial Content Translation

1. Go to the webIDE and navigate to Pages>DE>... Here you will find all the content of the website in subfolders. (Make sure you are in the right branch (dev currently uses: chore/content-prototyping)
2. Next to the "DE" Folder You will find "EN" which will contain the exact copy of the content in English language wherever there is one.
3. Linking? How? In frontmatter?
4. Copy the content of the desired file inside DE you want to translate into a new file inside the EN folder.
5. Translate the Words inside the doc and save it in a new file in the EN Folder.
6. Submit the change to the Branche.

assigned to @moritz

changed title from en translation to Organising the English Translation

changed the description

assigned to @haus

@moritz I would like to write a tutorial about the Website Translation Process. I started (see above).

• Could you please comment on the discussion Points? Should be quick.

Could you do by this week, so I can teach others to help us out? THX

marked the checklist item Fallback solution: We don't actually need one. Once we have a large number of Pages translated, we do then offer the EN Button / Page. The english page is only showing what has been translated. as completed

changed the description

changed title from Organising the English Translation to Organising the English Translation for Fabcity.Hamburg

@moritz

changed milestone to %FCOS Suite until IF Final Conference

added To Do in fchh-interfacer-webpresence label

assigned to @moritz and unassigned @haus

moved from fchh-website-deprecated#35 (moved)

its documented here: https://gitlab.fabcity.hamburg/fcos-suite/fcos-suite-astro

closed

mentioned in merge request !291 (merged)

mentioned in commit e66e2d62

mentioned in commit 1f4c989e