Page MenuHomePhabricator

Provide option to select the lead section in the pick a section step
Open, MediumPublic

Description

The "pick a section" step allows to select the section you want to translate from an article. Although the emphasis is on sections missing, it is also possible to select sections that are already present in the translated article (to expand their contents or replace them). However, this is not possible for the lead section.

This ticket proposes to include the option to select the lead section as part of the "Section present in <language-name>". The section will be listed as:

  • "(Top)" as title, to make it consistent with the New Vector term used in the table of contents.
  • An excerpt of the initial text of the page in the target language is used as description (only one line of text, cropped with ellipsis). This intended to clarify what this special section is really about by exemplifying it since the terms to refer to the lead section may not be widely known.

bn.m.wikipedia.org_w_index.php_title=Special_ContentTranslation&from=en&page=Moon&sx=true&to=bn(iPhone SE).png (667×375 px, 65 KB)

Although most of the time articles in both languages will have the lead section, the system should be able to handle the case where the source language ha a lead section but the article in the target language does not have one (e.g., only consist of sections). In such case, the lead section option will appear in the "Section missing in ,language-name>" and will include a description with an excerpt from the source article instead.

Event Timeline

@Pginer-WMF I do not believe that this task should have T353244: Resolve key regressions preventing the unified dashboard to replace the desktop one as parent task, since this is a new feature and not a regression fix.

@Pginer-WMF I do not believe that this task should have T353244: Resolve key regressions preventing the unified dashboard to replace the desktop one as parent task, since this is a new feature and not a regression fix.

Good point. However I still think it makes sense here. With the current desktop version it is possible to publish an initial version of the translation for a new article (e.g., just the lead section) and then continue translating it further later (using the pencil icon from the "published" view).

With the new dashboard, what we provide by default is the possibility of extending the existing article with new sections. So from the user perspective they won't be able to translate further the lead section of a new article, while it was possible before.

So here the regression is in terms of not being able to support a certain behaviour. Even if the way we propose to support it involves replacing an old feature with a new one, the purpose is to still support this behaviour (avoid breaking backwards compatibility).