Change Details

== Goal == * Warn users when their topic might not meet notability guidelines. * Offer helpful alternatives instead of a dead end. * Only shown for high-risk cases identified by community rules. == Conditions == As communities define an outline for a particulr type of article, they can include a `notability-risk` parameter to capture the restrictions applied to articles of this particular type. In order to simplify the logic, we can capture some conditions as tags that can be combined. The following tags are proposed: - (default): No restrictions apply to this type of article. The default if no level is specified. - `wikidata`: Only topics that exist on Wikidata can be created. - `crosswiki`: Only topics that are available in 5 other languages can be created. - `sources`: Only topics for which the user provided sources not discouraged by the community can be created. - `junior`: Restrictions apply to junior editors only (those without previous experience having published a surviving article). - `draft`: Publication allowed only under the draft namespace (where it exists) or the user namespace (as a sub-page of tthe user page). Tags can be combined to express mor ecomplex conditions. For example, if the outline for biographies is marked as `junior-crosswiki`, junior editors would be able to create only biographies for topics that exist in 5 other wikis. If the condition is not met, a list of community-defined alternatives will be provided. These can be based on a message, and a list of title and link pairs to direct users elsewhere. Note that combining `wikidata` and `crosswiki` is equivalent to just using `crosswiki` since the later requires a wikidata item to exist already. For the rest of the tags, their combination change the restrictions making them more or less strict. == When to Show == This step sits between type selection and sources. Once we know what type of article the user wants to write, we check if the community has any concerns about it. Some article types have no concerns at all, the user skips this step and goes straight to adding sources. Some article types are flagged by the community. For example, biographies might require the person to already be written about on other Wikipedias. Animals might need to already exist in Wikidata. When a flag applies and the topic doesn't pass, the user sees a friendly message and a list of things they can do instead. One flag works differently: sources. Instead of blocking the user here, it makes the next step (adding sources) required instead of optional. This way the user isn't stopped twice, once for notability and again for sources. == Core flow == # User sees a friendly message explaining the concern. # User sees alternatives defined by the community (e.g., edit related articles, learn about notability, propose a Wikidata item). # User can choose an alternative or continue anyway. == Layout == === Mobile === * Full screen page. * Header: back arrow + title. * Friendly warning message. * List of alternative actions. * "Continue anyway" option (secondary). === Tablet/desktop === * Single centered column (600–720px wide). * Same content as mobile.

== Goal == * Warn users when their topic might not meet notability guidelines. * Offer helpful alternatives instead of a dead end. * Only shown for high-risk cases identified by community rules. == Conditions == As communities define an outline for a particulr type of article, they can include a `notability-risk` parameter to capture the restrictions applied to articles of this particular type. In order to simplify the logic, we can capture some conditions as tags that can be combined. The following tags are proposed: - (default): No restrictions apply to this type of article. The default if no level is specified. - `wikidata`: Only topics that exist on Wikidata can be created. - `crosswiki`: Only topics that are available in 5 other languages can be created. - `sources`: Only topics for which the user provided sources not discouraged by the community can be created. - `junior`: Restrictions apply to junior editors only (those without previous experience having published a surviving article). - `draft`: Publication allowed only under the draft namespace (where it exists) or the user namespace (as a sub-page of tthe user page). Tags can be combined to express mor ecomplex conditions. For example, if the outline for biographies is marked as `junior-crosswiki`, junior editors would be able to create only biographies for topics that exist in 5 other wikis. If the condition is not met, a list of community-defined alternatives will be provided. These can be based on a message, and a list of title and link pairs to direct users elsewhere. Note that combining `wikidata` and `crosswiki` is equivalent to just using `crosswiki` since the later requires a wikidata item to exist already. For the rest of the tags, their combination change the restrictions making them more or less strict. == When to Show == This step sits between type selection and sources. Once we know what type of article the user wants to write, we check if the community has any concerns about it. Some article types have no concerns at all, the user skips this step and goes straight to adding sources. Some article types are flagged by the community. For example, biographies might require the person to already be written about on other Wikipedias. Animals might need to already exist in Wikidata. When a flag applies and the topic doesn't pass, the user sees a friendly message and a list of things they can do instead. One flag works differently: `sources`. Instead of blocking the user here, it makes the next step (adding sources) required instead of optional. This way the user isn't stopped twice, once for notability and again for sources. == Core flow == # User sees a friendly message explaining the concern. # User sees alternatives defined by the community (e.g., edit related articles, learn about notability, propose a Wikidata item). # User can choose an alternative or continue anyway. == Layout == === Mobile === * Full screen page. * Header: back arrow + title. * Friendly warning message. * List of alternative actions. * "Continue anyway" option (secondary). === Tablet/desktop === * Single centered column (600–720px wide). * Same content as mobile.

== Goal == * Warn users when their topic might not meet notability guidelines. * Offer helpful alternatives instead of a dead end. * Only shown for high-risk cases identified by community rules. == Conditions == As communities define an outline for a particulr type of article, they can include a `notability-risk` parameter to capture the restrictions applied to articles of this particular type. In order to simplify the logic, we can capture some conditions as tags that can be combined. The following tags are proposed: - (default): No restrictions apply to this type of article. The default if no level is specified. - `wikidata`: Only topics that exist on Wikidata can be created. - `crosswiki`: Only topics that are available in 5 other languages can be created. - `sources`: Only topics for which the user provided sources not discouraged by the community can be created. - `junior`: Restrictions apply to junior editors only (those without previous experience having published a surviving article). - `draft`: Publication allowed only under the draft namespace (where it exists) or the user namespace (as a sub-page of tthe user page). Tags can be combined to express mor ecomplex conditions. For example, if the outline for biographies is marked as `junior-crosswiki`, junior editors would be able to create only biographies for topics that exist in 5 other wikis. If the condition is not met, a list of community-defined alternatives will be provided. These can be based on a message, and a list of title and link pairs to direct users elsewhere. Note that combining `wikidata` and `crosswiki` is equivalent to just using `crosswiki` since the later requires a wikidata item to exist already. For the rest of the tags, their combination change the restrictions making them more or less strict. == When to Show == This step sits between type selection and sources. Once we know what type of article the user wants to write, we check if the community has any concerns about it. Some article types have no concerns at all, the user skips this step and goes straight to adding sources. Some article types are flagged by the community. For example, biographies might require the person to already be written about on other Wikipedias. Animals might need to already exist in Wikidata. When a flag applies and the topic doesn't pass, the user sees a friendly message and a list of things they can do instead. One flag works differently: `sources`. Instead of blocking the user here, it makes the next step (adding sources) required instead of optional. This way the user isn't stopped twice, once for notability and again for sources. == Core flow == # User sees a friendly message explaining the concern. # User sees alternatives defined by the community (e.g., edit related articles, learn about notability, propose a Wikidata item). # User can choose an alternative or continue anyway. == Layout == === Mobile === * Full screen page. * Header: back arrow + title. * Friendly warning message. * List of alternative actions. * "Continue anyway" option (secondary). === Tablet/desktop === * Single centered column (600–720px wide). * Same content as mobile.