WikiConference North America does “Year/Pagename” e.g. “2018/Schedule” along with per-year templates that strip out the year prefix in the displayed page title and add a year-specific tagline. We have done five of these conferences now and this system has worked well for us.

How does it relate to the subset of wikitext used for edit summaries? As I understand you can do simple things in edit summaries like links but nothing fancy like template expansion.

In T210313#4900059, @Tgr wrote:

Maybe @Harej remembers if that was an intentional limitation or a bug.

Do we, as a general rule, want to prevent the creation of Jade pages that do not correspond to legal revision IDs?

I am interested in resuming work on Toolhub sometime before the end of the fiscal year so it may make sense to just keep this task around.

Even if they are the same page, a page might look different while you're in edit mode compared to if you're just reading it. (It might not be, though! Depends on what you come up with.)

Right, we shouldn't need anything terribly novel in terms of design here. A wireframe would just show what the current watchlist feed would look like with the Jade-specific features enabled.

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.

We are going ahead with these UI integrations:

• Entry view mode (i.e. the Jade page itself)
• Entry edit mode
• Diff view integration
• Watchlist integration
• Search integration

Earlier discussion on this task suggests that it got de-prioritized because it's more of a feature for ORES than for Jade, but really it can go either way. I think it's a feature of ORES (figuring out how exactly to reveal its inner workings to the outside) but also a feature of Jade (the actual visualization step).

I remember at the technical engagement offsite we discussed this very idea. I don't think we had anything more complicated in mind than "did you find this to be useful, yes/no" which is apparently good enough for most tech documentation websites.

Related Etherpad: https://etherpad.wikimedia.org/p/Jade_summary_data_use_cases

As discussed in last week's Scoring Staff meeting, the issue is that semantically, "null" doesn't mean "I don't know" – it means "there is no data." So we need a more explicit "I don't know" indicator.

Pieces of data I am interested in: