This is ready for development. It is worth noting that it may be easy to develop this task alongside of T219391, about the collapsible start module. But that task is not required for newcomer tasks.

@RHo -- this is coming to you first for designs

This is almost ready for development.

Hi @Kudpung -- @ifried and I talked about this task, and it looks like it's not one of the NPP priority tasks that are included in the large amount of work being done by the Community Tech team via the wishlist. When Community Tech is finished working on those NPP tasks, they'll need to move on to other wishlist items, and the responsibility for maintaining Page Curation tools will come back to the Growth team (the team I'm on). The Growth team will be able to address breaking bugs to make sure that patrollers can continue to do their work, but we'll not be able to commit to extending Page Curation to include features like the idea on this task (about moving to draft namespace). I totally understand why that idea is useful, but the Growth team is going to be using all our bandwidth in the coming year to pursue our priority of increasing the retention of new editors in mid-size Wikipedias. So for new features like this one (for the future that we can foresee), it could be approached in future wishlists or through volunteer developers. Let me know if you have any questions!

Hi @Kudpung -- thanks for checking in on this. I'm tagging @ifried, who is the product manager working with the Community Tech team right now on the NPP requests from the wishlist. She'll be able to tell us whether/where this idea does or does not fit in with the current plans.

@kostajh -- thank you for making the prototype, for experimenting different ways, and for your notes on this Phab task and in chat. I spent some time with the prototype, and I have some initial reactions and questions.

@Etonkovidova -- I tried to test this by creating a new account with Javascript, but I was not even able to create the account. I got an error message on the account creation page saying:

I just removed the following idea from the description because it is going to be worked on in T232400:

@nettrom_WMF -- god question. T211446 is a task that has captured some ideas for changes to the welcome survey that we've had over time, and this task here (T232400) accomplishes one of them. I'll now modify T211446 to show that that idea is covered by this task.

@Urbanecm -- I don't think we went over your work on this together. What did you end up building? Do you have screenshots?

I see that this is in production now and working fine (@Etonkovidova -- you do agree that this in production, right?). I did notice the blink, but it's quite fast and does not seem to damage the experience. Therefore, I think this is resolved.

@Arrbee -- thank you for filing this. Please let me know if/when you need support to work on it. The Growth team's current work on newcomer tasks may yield a feature that is the right fit: using the help panel as a way to guide users on specific types of tasks, like in this mockup.

This task is complete because we have listed all the maintenance templates and categories we need for now, and have the counts to determine which ones to use. That list is specified on T232423.

This task is complete because we have listed all the maintenance templates and categories we need for now.

This task is complete because we have listed all the maintenance templates and categories we need for now.

This task is complete because we have listed all the maintenance templates and categories we need for now.

This is ready to be worked on, and is a high priority because it will have a substantial impact on the homepage discovery rate (and therefore the newcomer task discovery rate) for mobile users. I'm putting it in Ready for Development so we can prioritize against newcomer tasks work.

I just thought about this a little bit, and I have an argument why we should not change the link target. There are many places in the wiki that a user will encounter their own username, such as in their signature, in their watchlist, and when other users ping them. Those links currently do not lead to the homepage. Therefore, I think the user should learn that only a couple special places will lead them to their homepage: the personal tools link (left nav on mobile) and the tabs once they are in the user space. I think it could be more confusing if the user never knows which links will and will not lead them to their homepage.

Thank you!

@alexhollender -- thanks for pointing this out. This immediately makes me wonder how many pages get created via the redlink on desktop. More specifically, something like "what percent of new pages (that are not subsequently deleted) created by new editors on desktop are created via the search redlink?" I don't expect that we have the instrumentation to actually answer that question.

@RHo and I have to discuss this, since we're committed to addressing it. I've put it on our agenda to discuss.

This is ready for development, but should not be deployed until we hear from @nettrom_WMF on whether we should just do this, or should wait for a clearer milestone for affecting our data collection and analysis.

@RHo -- tagging you here because this is the parent task that represents the change to the mentorship module you mocked up in this page while we planned for newcomer tasks. When you've settled on a design for this, we can make this task ready for development.

@Catrope -- did you end up deleting the local overrides? If so, we can close this task.

@RHo -- this is the placeholder task for restyling work that surfaced in the newcomer tasks mockups. I don't consider this a higher priority than our newcomer tasks work, but designs can go on this task for development in the future.

Moving to Needs Design and assigning to @RHo.

@Trizek-WMF (and @Tractopelle-jaune) -- the team discussed this today, and we think that the solution proposed by @Catrope in T174349#3866824 could work. This would be adding an "Exclude selection" to the tag filter, like in the namespace filter:

@Trizek-WMF -- thank you for pointing out this new request. We have not yet started pursuing this feature, and the team has not discussed it in a while. I am moving it back to "Needs Discussion" so that we can do that.

This is ready for development.

This is going to "Needs Design" because @RHo is still finalizing what happens to the start module once suggested edits is initialized.

This is ready for development.

@Pginer-WMF @Amire80 @Trizek-WMF -- would you be willing to weigh in on the wording for this question? We want to calibrate it so that people are saying the languages with which they could succeed at Content Translation.

@nettrom_WMF -- it would be great if you could take the first step here, and run the numbers of what percentage of users who see the survey click each of these links. I'm hoping that it's easy to get. It would also be helpful to split by wiki and by desktop/mobile. We only need to know this for users who got Variation A.

This is ready for development.

@nettrom_WMF @kostajh @Catrope @Tgr @marcella -- the first step with this one is to get some thoughts and ideas down around the right way to do it, and when the right time is to do it. I think we probably need to hear from @nettrom_WMF first because of the reverberations this change would have in our experiments that are currently running.

Thanks for filing this, @Stryn, and for uploading the video. Since multiple users are experiencing this, I think we can assume that several more are also experiencing it but haven't said anything.

The design brief linked in the description is complete, and the team has spent time going over it. This task is finished.

@Theklan -- I'll try to clarify about the namespaces. The EditorJourney project records all page loads that newcomers do in their first 24 hours, regardless of the namespace. This is because we want to understand how often newcomers are reading help documents, going to the help desk, attempting edits, etc. EditorJourney also records the page titles of the pages the newcomer visits so that we can tell they are looking at something specific, like a specific tutorial or the help desk. But we don't want to record the page titles of articles they're reading, because that's too sensitive, and we don't need to know it. It's good enough to know that they are visiting an article in the main namespace. So the question is which namespaces in Basque Wikipedia are the sensitive ones that we should not record the page titles, like Article, Article Talk, File, File Talk, etc. The list we usually include is 0 (Article), 1 (Talk), 6 (File), 7 (File Talk). But if your wiki uses the Portal, Book, or Draft namespaces, we might want to include those, too.

@kostajh -- the survey should run as an A/B test for Basque. But I haven't yet made the Phab task for welcome survey because Basque still has a couple things to translate before that's ready. I think we're only ready to go with EditorJourney for now, which is why T232061 is this task's only child task.

This is ready for development. Please check the appropriate item in the description when complete.

@Trizek-WMF @Theklan -- before we begin deployments, I want to make sure of a couple things:

This is ready for development (along with its children).