Page MenuHomePhabricator

support multiple simultaneous Blueprint sidebar configurations
Closed, DeclinedPublic


If we address T101441: Goal: Integrate the new Web APIs hub with and T101441: Goal: Integrate the new Web APIs hub with, we will have two sets of pages on using the Blueprint skin but desiring different sidebar contents. If we configure Blueprint using the SkinPerNamespace extension, this would mean hacks like two versions of the extension, or per-namespace sidebars. Maybe it's easier to be explicit and use the SkinPerPage extension with pages specifying <skin sidebar="ooui-lsg">Blueprint</skin> or` sidebar="devhub"`

Either way the extension will need to be able to load different sidebar configurations.

Event Timeline

Spage raised the priority of this task from to Needs Triage.
Spage updated the task description. (Show Details)
Spage added subscribers: Volker_E, violetto, Prtksxna and 3 others.
Spage set Security to None.
Spage triaged this task as Medium priority.Jul 28 2015, 5:26 AM
Qgil lowered the priority of this task from Medium to Low.Jul 28 2015, 8:43 AM

As long as T93610: Put WikimediaUI Style Guide on is Assigned To None + Priority Needs Triage, I think this task is Low priority.

The skin is no longer maintained