Following the user journey from an administrator’s perspective, the process feels cumbersome and potentially confusing. The proposed workflow in the interactive prototype requires switching back and forth between the StarterKit dashboard and Content Translation. It also presents instructions for novice translators within the StarterKit app, but these cannot be enforced there. The same issue applies to publishing, as administrators can easily publish translations without following the provided instructions.

As a potential improvement, I suggest replacing the checklist approach with a concise set of best practices for administrators to review before translating. The current checklist creates the illusion of enforceable interaction between StarterKit and CX, which is not actually supported.

Another, more resource-intensive option would be to integrate the interactive instructions directly into CX, where compliance could be enforced for novice translators. However, I do not recommend this approach at this time, given the project’s current time and resource constraints.

Setting the design details aside, this task requires the ContentTranslation extension to be installed on the current wiki, which is not the default. Assuming CX is installed, the task is simple and straightforward.

ngkountas opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/21

move padding from main app to routes

In T422472#11793210, @ngkountas wrote:

Setting the design details aside, this task requires the ContentTranslation extension to be installed on the current wiki, which is not the default. Assuming CX is installed, the task is simple and straightforward.

About the extension requirement for this task, we can consider adding a process later for wiki communities to request installation of the extensions needed to use the starter kit. Ideally, this should be handled as part of the wiki creation process itself. I’m not sure if Gadgets or CX extension installation are already part of that flow. Would be useful to understand at what stage in the wiki journey these are considered, and who is responsible for requesting and installing them.

In T422472#11792974, @ngkountas wrote:

Following the user journey from an administrator’s perspective, the process feels cumbersome and potentially confusing. The proposed workflow in the interactive prototype requires switching back and forth between the StarterKit dashboard and Content Translation.

Definitely agree there are navigation challenges in the user flow right now and the UX is not the most ideal. Something we can revisit in a future iteration. If and when we have a starter kit extension, I imagine some of the complexities in the current UX flow, especially navigating between the two different environments, Toolforge and the wiki will get simplified.

I am re investigating this right now. After taking a fresh look at the user flow in the mockups, I agree that there is quite a bit of back and forth happening between the Content Translation tool and wiki which might be unnecessary.

On Step 2 I think the step can already be "Translate & Publish" and then we skip Step 3. The publish button could be "Mark as Done" rather than publish, because publish actually happens in the Content Translation tool itself.

Here is the link to revised prototype.

There maybe languages where the machine translation quality might not be the best. To address this, we could add a tip that says: "If the machine translation available for your language is of poor quality, choose "Start with empty paragraph" from the MT options list instead."

Here is the link to revised prototype.

toluayo merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/21

Translate an important policy page

ngkountas opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/26

Translate policy page: Enable CTA for translation

As discussed offline, the bullets in Step 2 would ideally be moved into a “Suggested tips” box and displayed as a closable dialog when we eventually port the starter kit into an extension format. Since that technical implementation isn’t possible right now, it would be better to keep them as bullet points for now and require users to review them before closing the task.

The same approach would apply to T422472 and T422214#11863690.

toluayo merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/26

Translate policy page: Enable CTA for translation

ngkountas opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/36

Translate Policy Page: Complete the full flow of task and details

eamedina merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/36

Translate Policy Page: Complete the full flow of task and details

ngkountas opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/37

Refactor translation URL logic: extract to useFivePillarsUrl composable

toluayo merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/37

Fix multiple issues blocking completion of "Translate Five Pillars" essential task

ngkountas opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/54

Refactor: adjust widths and layout in essential tool pages

eamedina merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/54

Refactor: adjust widths and layout in essential tool pages

ngkountas opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/66

Fix: Adjust landing step for Translate Five Pillars essential tool

Noticed a few minor issues while testing this feature with test.wikipedia:

• The description on the task page reads: "..Translating it helps new contributors on Wikipedia Wikipedia understand the core principles of the project." I am guessing that "Wikipedia" is added twice because Test Wikipedia is being interpreted as Wikipedia?
• Also, I noticed that the left page margin is significantly smaller compared to https://starterkit.toolforge.org/install-gadget-tool. Ideally, the translate task page should have the same left page margin as the gadget task page.
• At what point will the "Translate & publish" step become green and ticked?

Thank you @srishakatux for your comments! Addressing them below:

The description on the task page reads: "..Translating it helps new contributors on Wikipedia Wikipedia understand the core principles of the project." I am guessing that "Wikipedia" is added twice because Test Wikipedia is being interpreted as Wikipedia?

That's right, the message works well for production wikis only.

Also, I noticed that the left page margin is significantly smaller compared to https://starterkit.toolforge.org/install-gadget-tool. Ideally, the translate task page should have the same left page margin as the gadget task page.

This issue has been addressed in this MR, which is currently under review.

At what point will the "Translate & publish" step become green and ticked?

The requirements for the steps in this tool are:

1. To continue from step 1, the user needs to start a draft translation for the Five Pillars page. Until then, the "Continue" button will be disabled.
2. To mark this task as done, the user needs to publish a translation for the Five Pillars page in the target wiki (even publishing in user namespace works). Until then, the "Publish in Content Translation" checkbox will be unchecked and the "Mark as done" button will be disabled.

In T422472#11954558, @ngkountas wrote:

2. To mark this task as done, the user needs to publish a translation for the Five Pillars page in the target wiki (even publishing in user namespace works). Until then, the "Publish in Content Translation" checkbox will be unchecked and the "Mark as done" button will be disabled.

Which means that the tool will detect if user published a translation? I am not able to test the entire flow as I am running into the following error on test wikipedia: "Critical error: Content translation failed to load due to internal error."

@srishakatux right, the tool will detect if user published a translation. In order to test the flow, I would suggest logging in with a production wikipedia in which the Five Pillars article is missing (e.g. https://nrm.wikipedia.org) and start CX there. You can publish your translation to the user namespace, so that you can test the entire flow.

ngkountas opened https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/70

Fix: clarify "Five pillars" step 1 requires saved translation draft

ngkountas closed https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/70

Fix: clarify "Five pillars" step 1 requires saved translation draft

toluayo merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/66

Fix: Adjust landing step for Translate Five Pillars essential tool