I'm not sure at what point this would occur but I'm of the mind that once an article is added to the NPP queue, a TP should automatically be created with header and relevant WikiProjects listed in the banner, if it doesn't already have one.

Sounds like this could be a bot which checks for (new) pages in the queue and creates the talk page if it doesn't already exist?

Hi everyone,
I'd like to add some thoughts on how this feature could be implemented, along with a possible technical approach.

Proposed Implementation Approach

1. Trigger Point
   • When a page enters the PageTriage queue, check whether a talk page already exists.
   • If not, automatically create a basic talk page with the standard header (e.g {{Talk header}} or as defined by community consensus).

2. WikiProject Tagging Workflow (Reviewer-driven)
   • Similar to the AfC helper script, PageTriage could provide a modal dialog inside the “tagging” workflow.
   • The modal would allow NPP reviewers to select relevant WikiProjects from a searchable dropdown.
   • The WikiProject list can be loaded from the existing JSON used by AfC: Wikipedia:WikiProject_Articles_for_creation/WikiProject_templates.json.

3. BLP Detection / Prompt
   • Before inserting the WikiProject banner shell, check whether the article:
     • falls under Category:Living people
     • or contains infobox/person metadata
   • If detected (or if unclear), ask the reviewer whether to set blp=yes on the banner shell.

4. Talk Page Structure Example

{{Talk header}}
{{WikiProject banner shell
  | blp = yes/no
  | 1 = 
    {{WikiProject Foo}}
    {{WikiProject Bar}}
}}

5. Why Reviewer-Driven Instead of Fully Automatic
   • Reviewers often know best which WikiProjects apply.
   • Minimizes incorrect tagging and avoids unnecessary bot edits.
   • Still reduces work by automatically handling talk page creation + template shell setup.

6. Optional Future Automation
   • Once the system stabilizes, a follow-up task could explore light automation (e.g suggesting WikiProjects based on categories or article titles).

Benefits

1. Reduces manual workload for NPP reviewers
2. Ensures every new article has a properly structured talk page
3. Helps WikiProjects discover new articles faster
4. Follows existing patterns from AfC tools, so less re-inventing the wheel

Happy to expand further or work on a prototype patch!

Thanks for your ideas and analysis. Here's some thoughts:

• Mass adding {{Talk header}} to talk pages goes against current community consensus, if I recall correctly. So this task should probably be re-scoped to adding the WikiProject banner shell only.
• NPPers adding WikiProject tags is optional, so the modal would need to be designed in a way that it is optional, out of the way, doesn't add extra mandatory clicks if you want to skip it, or has a preference to turn it off.
• WikiProject tags and BLP detection should probably be done in separate patches, so that no one patch is too complex, which will increase the speed of reviews. We could also collect class as well. So might want to do 3 patches, starting with WikiProject tags, and then adding BLP and class if you get time.
• That proposed wikicode looks non-standard. I'd recommend using the standard formatting at https://en.wikipedia.org/wiki/Template:WikiProject_banner_shell#Basic
• I completely agree with it being reviewer-driven instead of automatic, and with possibly adding "suggested" WikiProjects later.

Hope that helps.

In T315930#8176439, @TheresNoTime wrote:

I'm not sure at what point this would occur but I'm of the mind that once an article is added to the NPP queue, a TP should automatically be created with header and relevant WikiProjects listed in the banner, if it doesn't already have one.

Sounds like this could be a bot which checks for (new) pages in the queue and creates the talk page if it doesn't already exist?

Issues with a bot would be 1) we can't mass add {{Talk header}} due to consensus against that, and 2) the bot wouldn't be able to pick WikiProjects as accurately as a human.

IMO it should be reviewer driven but be completely optional for reviewers. A BLP banner is a must but the effort should be to streamline the Page Curation tool for reviewers rather than add new tasks. There are literally 100s of Wikiprojects, not even NPPers know more than a few. A dropdown would be very long. There was once a suggestion for NPP to add stub tags.(I think it was mine). Same problem.

In T315930#11407520, @Novem_Linguae wrote:

Thanks for your ideas and analysis. Here's some thoughts:

• Mass adding {{Talk header}} to talk pages goes against current community consensus, if I recall correctly. So this task should probably be re-scoped to adding the WikiProject banner shell only.
• NPPers adding WikiProject tags is optional, so the modal would need to be designed in a way that it is optional, out of the way, doesn't add extra mandatory clicks if you want to skip it, or has a preference to turn it off.
• WikiProject tags and BLP detection should probably be done in separate patches, so that no one patch is too complex, which will increase the speed of reviews. We could also collect class as well. So might want to do 3 patches, starting with WikiProject tags, and then adding BLP and class if you get time.
• That proposed wikicode looks non-standard. I'd recommend using the standard formatting at https://en.wikipedia.org/wiki/Template:WikiProject_banner_shell#Basic
• I completely agree with it being reviewer-driven instead of automatic, and with possibly adding "suggested" WikiProjects later.

Hope that helps.

Thanks for your thoughts. I agree!

In T315930#11408147, @Kudpung wrote:

IMO it should be reviewer driven but be completely optional for reviewers. A BLP banner is a must but the effort should be to streamline the Page Curation tool for reviewers rather than add new tasks. There are literally 100s of Wikiprojects, not even NPPers know more than a few. A dropdown would be very long. There was once a suggestion for NPP to add stub tags.(I think it was mine). Same problem.

I agree, it definitely needs to remain reviewer-driven and completely optional. To avoid overwhelming reviewers with the hundreds of WikiProjects, the idea is to use a simple typeahead search box rather than a long dropdown, similar to the AfC helper script.