We already have some code which implements the judgment view mode using a Mustache template, so maybe it would be easier to just tweak this template rather than write a JS layer for prototyping?

That will depend on what the wireframe ends up looking like; if it's a big radical change, it might be worth just prototyping first before implementing.

In T212370#4836284, @Harej wrote:

if it's a big radical change, it might be worth just prototyping first before implementing.

Great, I'm okay either way here. Another potential reason to write a JS prototype would be that we need to guarantee repeatable data for each test.

Link to the current template for reference:
https://phabricator.wikimedia.org/diffusion/EJAD/browse/master/templates/judgment_page.wiki.mustache

Copied from T199128:

I'm not a designer, but I figured that it would help jump-start our design conversation if I took a stab at some layouts. Below are three wireframes that I have worked out to demonstrate some approaches we might take to generating a nice layout for a entity view. Note that the vertical "..." is intended to represent a menu tab that, when clicked, would display a pop-over menu pane containing options such as "edit", "remove", or "move". I couldn't find any standard way to represent such a thing so I made due.

Tabs

This view is inspired by the tab-based navigation of Special:Preferences. The tabs contain the consensus data. When a tab is selected, the proposals and endorsements are visible. One clear downside to this is that tabs will quickly run out of space horizontally. This can be dealt with by stacking tabs, but that is visually unappealing.

Table

This view was designed to experiment with strategies for mitigating the too-many-tabs problem. The idea is that a table of schemas would be visible. Each row would show the consensus data and some basic stats about the # of proposals/endorsements. When a row is expanded, the proposals and endorsements are visible.

Two Column

This wireframe was developed to explore a mobile compatible entity view. The vector image demonstrates two potential views of an entity. One uses the single-column mobile diff. The other uses a two column default diff view. Each schema is contained within a block that can stack and flow as the browser width changes. The blocks are initially compressed and only show the consensus data but they can be expanded to show reasoning behind the consensus proposal as well as counter-proposals and endorsements.

The basic UI

Expanded:

All collapsed:

Basic actions

Propose a label:

Endorse a label:

Advanced actions (rare)

Labels

Label menu:

Edit Label:

Edit label (Error):

Promote a label:

Delete label:

Delete label (Error):

Endorsements

Endorsement menu:

Edit endorsement:

Edit endorsement (Error):

Move endorsement:

Delete endorsement:

Etc.

Manual revert:

This screenshot contains the labeldata field for editquality. I included a lot of content because I think this label benefits from solid coaching. We'll need to set up strings for all of the relevant content bits. I'm working on contentquality next.

This screenshot shows a confirm dialog for moving an endorsement.