| • thcipriani | |
| May 23 2025, 7:30 PM |
| F72296215: PatchdemoSketchVersion1Page3-WF2.png | |
| Feb 23 2026, 10:52 PM |
| F72296216: PatchdemoSketchVersion1Page3-WF1.png | |
| Feb 23 2026, 10:52 PM |
| F72296053: PatchdemoSketchVersion1Page4.png | |
| Feb 23 2026, 10:52 PM |
| F72296051: PatchdemoSketchVersion1Page3.png | |
| Feb 23 2026, 10:52 PM |
| F72296052: PatchdemoSketchVersion1Page2.png | |
| Feb 23 2026, 10:52 PM |
| F72296050: PatchdemoSketchVersion1Page1.png | |
| Feb 23 2026, 10:52 PM |
| F72296054: PatchdemoSketchCurrentAnalysis.png | |
| Feb 23 2026, 10:52 PM |
Now that we have wikifarms, the next step will be allowing users to configure individual wikis differently. This would require significant rework to the existing create form.
We've moved Patch Demo to use the slim PHP framework. In order to make changes to the create wiki form, we'll need to break the index page into reusable parts.
In particular, the create form should be easy to manipulate, change, and break apart as needed.
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| index: split template into multiple partials | repos/test-platform/catalyst/patchdemo!356 | brennen | brennen/creation-partial | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T412301 Add support for configuring each wiki farm wiki's content/interface language | ||
| Open | Feature | None | T412738 Allow adding/removing extensions and config from individual wikis in a wiki farm | ||
| Open | brennen | T395162 Template-ify Patch Demo index page | |||
| Open | EBomani | T414525 Design a usable heterogenous wiki farm UI | |||
| Resolved | brennen | T416627 Rearrange Patch Demo webroot | |||
| In Progress | brennen | T429238 Port Patch Demo create a wiki form to Codex PHP (CSS supported codex) | |||
| Open | EBomani | T432019 Move expiry.php into a Slim action, template, etc. |
@Tacsipacsi here's the task I promised in code review. Were you proposing vue-ifying or only using codex CSS? Or both one step at a time?
Sorry for not replying here earlier. I think Patch Demo should be usable to the extent possible without JS. (Of course, things like auto-selecting checkboxes when choosing a preset won’t work, but manual selection of the checkboxes should.) This would speak for Codex CSS, but if we can do server-side rendering of Vue or another kind of fallback, that should be fine too.
Brainstormed some potential designs for the UI that would allow for feature expansion without affecting too much of the existing structure and workflow and while using the space effectively. These are not final and are here mainly for documentation purposes as we continue discussing the path forward and await more information from actual UI/UX professionals at the foundation since it feels warranted for a change at this scale.
The considerations on usability without JS are something we are keeping in mind and since we have not ventured into using Codex before, this is still to be determined. Will communicate updates regarding the evolution (or complete overhaul) of the design as iterations go on and more information is gathered.
Currently:
Version 1:
To make adding new features to Patch demo visually cleaner and the UI scaleable, Codex assets like form templates and tabs for pagination and navigation (among other things). The aim here is for the creation form to have ample space that allows for iteration and scaling with regards to features and patchdemo capabilities without growing to an overwhelming degree and physically demanding more of the page. This version uses tabs to have 4 distinct sections with the settings divided into their relevant categories. One thing to note is "Wikifarms" gets its own tab and in it, specific configurations for wikis can be achieved by allowing customization. It has been noted that this step should probably come earlier in the creation process or be combined with the general settings, but those options are yet to be brainstormed.
The sketches below illustrate the most important thing: with this format, the process of wiki creation improves (less scrolling to create a demo), and also becomes something we can expand on in a much easier way.
Again, none of this is final and this task will be updated as it goes. Implementation will only happen after proper approvals occur this as it is a very significant change and will determine how future feature integration occurs. Thanks!
brennen opened https://gitlab.wikimedia.org/repos/test-platform/catalyst/patchdemo/-/merge_requests/356
Draft: index: split template into multiple partials
brennen merged https://gitlab.wikimedia.org/repos/test-platform/catalyst/patchdemo/-/merge_requests/356
index: split template into multiple partials