As part of Section Translation (T243495), we want to support expanding existing articles by translating new sections. On desktop we want to reuse the translation editor that Content translation provides. In this way, users can translate a specific section on desktop with a familiar tool that takes advantage of the available space.
Currently, Content translation editor loads and published a complete article. This ticket proposes to extend its capabilities to be able to work with a single section instead. For example, based on a url parameter it should be possible to load the History section of the Ukulele article.
# Details
Expanding Content translation editor with a "section" mode requires some considerations (covered in separate sub-tasks):
- **T311614 Loading a single section.** Load contents for a single section in a way that users can add them to the translation and edit them normally. More efficient loading may require support from the Parsing team and can be considered separately (T237614).
- **Adjust the translation title.** For this case both the article title (non-editable) and the section title (editable in the translation) will be shown.
- **Publishing behaviour.** Publishing will add the new section to the target article at the end of the document. This will be refined in follow-up tickets (adjusting the action and messaging to the circumstances).
-- **Section-translation** Content published will include the "sectiontranslation" tag in addition to the usual "contenttranslation" one.
- **Publish settings.** We may need to initially remove the option to customize the target namespace when translating sections.
- **Access through the URL.** As a first step, the section mode will be accessible through a URL parameter. Once the overall workflow for section translation is specified, the UI supporting other steps (e.g., letting the user pick a section to translate) will connect to the current step without the need for manually creating a URL.
Apart from the differences noted, the translation workflow should work in the same way it does when a full article is translated.
{F30517880, width=80%}
___
Since some of the current limitations of the current database schema may apply, it may be good to keep the following tickets in mind {T192065}