Page MenuHomePhabricator

[SPIKE] Explore how initial design concepts could be extended to other policies/suggestions
Open, Needs TriagePublicSpike

Description

In T322815 and T322816, we generated initial concepts for how the visual editor might prompt people to decide whether to accompany the new content they're adding with a reference.

Considering we see a potential future wherein the visual editor is providing people feedback about a range of project policies and guidelines, this task involves the work with iterating on said "initial concepts" to see if/how they might be extensible to surfacing feedback about the policies/guidelines and suggestions listed below.

Requirements

Create iterations of the design concepts we generate in T322815 and T322816 for each of the following policies/guidelines and suggestions:

Design concepts

Done

  • Design concepts that meet the requirements drafted above are documented

Event Timeline

Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptJan 3 2023, 4:37 PM
ppelberg updated the task description. (Show Details)

UPDATE
Thank you to @KStoller-WMF and @RHo; I've added the suggestions they made for other "Reactive" suggestions we could consider creating "speculative" designs for.

Note: I've taken a pass at priortitizing the "Proactive Suggestions" based on a combination of: A) the value I assume they could deliver to newcomers, Junior Contributors, and projects as a whole and B) the likelihood the feature would be implemented in the near future.

NPOV is not a tractable problem for an automated check, especially if you are looking only at new additions and not at the overall effect. If you are looking for other ideas, consider these:

  • flagging links that are on the spam list
  • unwanted/excessive formatting (e.g., '''', which produces a pointless <i></i>).
  • insufficient number of links to other pages (the ideal/practical number will vary by size of the wiki)
  • warning abut URLs that may be particularly inappropriate, especially if we could copy XLinkBot's list
  • longer pages with no ==Sections==
  • individual sections that are too long
  • empty sections
  • accessibility problems, like using a ===Level 3=== section heading with no ==Level 2== section above it
  • external links (e.g., [https://www.example.com Example, Inc.]) in the middle of a sentence or as a bare URL (so it displays as [1]).