Creating a UI mockup would help us introduce JADE to new audiences, by telling the story of how it will be used.
TODO: Determine the blocking tasks before we're ready to create a mockup.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T212435 Review real-world query plans and performance for Jade | |||
| Declined | None | T238877 Write Huggle labels to Jade | |||
| Declined | calbon | T183381 Deploy pilot of Jade to a small set of wikis. | |||
| Declined | None | T212373 Complete Jade user testing | |||
| Duplicate | None | T210535 [EPIC] Jade Mockups: Prepare mockups of Jade initial feature set for user testing | |||
| Duplicate | None | T212385 Jade Implementation: Entry edit mode | |||
| Duplicate | None | T199128 Jade Mockups: Entry edit mode | |||
| Duplicate | Harej | T168993 Prepare a UI mockup for the JADE editor interface | |||
| Invalid | None | T153157 JADE: Link from scored edit to this tool feedback interface | |||
| Duplicate | Halfak | T212374 Jade Wireframes: Entity edit mode |
Event Timeline
Comment Actions
https://commons.wikimedia.org/wiki/File:JADE_mock_(diff).svg
This is just one place that JADE could appear.
Comment Actions
This task assumes the existence of a canonical/reference UI for JADE. I am not sure there is agreement there should be one.
Comment Actions
The work product created from this task may need to change depending on the outcome of T208748. As I've been looking into what kind of product JADE should be, I am beginning to scope the work around JADE in terms of different use cases. The interfaces should be designed should be done with the use cases in mind.