This is the behavior I'm seeing in test.wikipedia.org at the moment: https://imgur.com/a/16JO1ws. Enabling the gadget in preferences should be automatically picked up by the app and allow the user to continue. Do you see anything similar

User journey

1. Install. Install HotCat and confirm it's active in Preferences
2. Find. App surfaces uncategorized articles from your wiki, pick one.
3. Categorize. Open the article, follow popup instructions to add categories; app detects the edit.

One learning so far is that this feature will require we update the provided permission grants to our registered consumer (Starter Kit app). In order for the gadget to be installed, we need to create/edit a page under the Mediawiki namespace (/wiki/MediaWiki:Gadgets-definition) as well as creating a page that adds JavaScript (to load the gadget, ie /wiki/MediaWiki:Gadget-HotCat.js ). The table below compares the current permissions granted with what I needed for it work locally:

Leaving here related commit for documenting purposes, we can close this task now

Documenting merge request:

With this merge request we will be doing away with the need of the user to configure wiki-credentials, which I believe would resolve this ticket

@Pginer-WMF could you please confirm if clicking on "None of these? Pick a type instead" should reset scroll as well? That's the click that takes you to the list of outlines. Would like to clarify as that outlines view is technically not a "new step" within the code, but can reset scroll if needed (if several outlines are present, that page can be scrollable for sure)

Hi @GMikesell-WMF I checked a couple of articles from English to Hindi where only appendix section (see also) is suggested. Wondering are there still some scenarios where this is happening.

Source-related guidance on this screen is optional and should not imply that sources are always required at this step.

I'd like to discuss the "Similar to existing articles" feature (in this ticket, states B through E). If there is a total of, say, 10 or 15 types to select from (will depend on community), the user will presumably browser through this list and upon not finding a match the user can provide a similar article that the feature will try to match back to the same 10-15 types from above. Am I understanding this redundancy correctly? I take it the assumptions are a) that the user has an idea of what the article type they want to create should be, and b) the user may have a knowledge of a similar article beforehand. Even with these assumptions it seems the goal is still to help the user narrow down and find the right type from the already visible list. I'd love to hear more about the reasoning behind this feature.