Alternatively, for T92795 and T226282, PermissionManager's addTemporaryUserRights can be used to allow the page creation without the editcontentmodel right, and SpecialPage's userCanExecute can be used to override the right restrictions to allow users to access the special page (since the rights restriction can only be used to require a specific right, not one of multiple rights)

Just to be clear, your proposal is to create a new userright that allows to create a page with a non-default content model, but not change an existing page? It's an interesting idea that seems pretty reasonable at first glance.

In T226926#5356085, @Legoktm wrote:

Just to be clear, your proposal is to create a new userright that allows to create a page with a non-default content model, but not change an existing page? It's an interesting idea that seems pretty reasonable at first glance.

Yes, that is exactly what I am proposing

Below I've uploaded a mockup based on TemplateSandbox for how this user right could be translated into actual use. Currently, there is no special page for the creation of a new page, and the content model is assigned based on namespace and page title. This would add a bar below the editor for a user to set the content model they want, with the default content model shown being what would be automatically set if the user didn't have this right.

Other tasks for use cases:

• T72073: U4. Special page to enable Flow on existing wikitext talk pages, auto-archiving the wikitext page (v2) - introduced a dedicated right
• T85847: Grant editcontentmodel right to all logged in users - this may be a less-drastic (and thus less impactful) change
• T144475: Make it possible to create json pages in the module namespace - still open from 2016, this would solve

(And T217499: add editcontentmodel access to the templateeditor group on testwiki.)

I'd rather just see TEs get editcontentmodel tbh.

In T226926#5404471, @Izno wrote:

I'd rather just see TEs get editcontentmodel tbh.

Understandable, but granting TEs and/or mass message senders, editcontentmodel would require a lot of on-wiki discussion. I don't object, but I'd still like to see this implemented

In T226926#5404471, @Izno wrote:

I'd rather just see TEs get editcontentmodel tbh.

Definitely a good idea.

In T201495#5595348, @CCicalese_WMF wrote:

[snip]
Since we generally try not to add too many built-in user rights, we would say that a good first step for this would be for you to add this as an extension. If it gets wide adoption and is deemed to be generally useful, it could be considered for core.

Tagging Platform Engineering as a feature request to review/consider - does the response to the request for creating a new user right in T201495: Create a new user right for cross-namespace renames also apply here?

This seems like a good conversation for TechCom to get into. Managing how and when users can create pages with different content models is probably not something we should do piecemeal, but as part of a more holistic approach. Can you turn this into an RFC for discussion?

In T226926#5615258, @eprodromou wrote:

This seems like a good conversation for TechCom to get into. Managing how and when users can create pages with different content models is probably not something we should do piecemeal, but as part of a more holistic approach. Can you turn this into an RFC for discussion?

To clarify, I should make a new task with the same proposal, but formatted as an RfC?

Also, I realized (T230968: Special:ChangeContentModel should check if a page exists) that currently Special:ChangeContentModel can be used to both create new pages and change existing ones - that could be used instead of a new option when saving

@eprodromou can you respond to my question above about how to proceed with this?

@DannyS712: See https://phabricator.wikimedia.org/project/profile/52/ for more info