Hi @Aklapper, my apologies for the delay, I am just coming back from sick leave and did not see this before. My project partner and I are still interested in working on this and would like to keep it open. We will discuss what project tag to put on this and I will do that as soon as it's decided but reopening for now. Thanks and let me know if this alright.

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.

Oh, good call, did not know about those. Thank you!

Hey @Aklapper, my apologies for the pings, I still need this task for the bot tests. Please feel free to unsubscribe to this task if it helps because I have no other way to check this without calling it. Thank you and I have a great rest of your day :))

Investigating this right now. One main issue I am facing with triage is that the failure is not consistent. From my testing locally, on staging, and on production, the link is malformation is intermittent. The one thing that is clear is that it is happening with catalyst backend environments only. The following examples illustrate this:

Thank you @A_smart_kitten! Updated task to indicate that has been determined. Will get the change reviewed to ensure nothing breaks in release versions before or after (although unlikely).

Figure out what version we were on when we set $wgUseCodexSpecialBlock and $wgEnableMultiBlocks to universally true

Thank you @Dzahn! :)

Hello @Dzahn, got your Email and sent over a verification response. Thanks for getting to that so swiftly :))

Actually, might also be the case that my other username on here (accidentally created when I was no longer a contractor) is the issue. The user was EBomani-WMF and account has since been disabled, though, so I'm not sure.

Thank you so much, @thcipriani, @Dzahn and @Aklapper!

I joined as a contractor but converted to full-time about a year ago. I am not sure why it still indicates that and not sure what to do to fix it. Please inform and I will get to it.

Completed during office hours today. Leaving "In Progress" to mark resolved during planning.

The bot is now reporting appropriately for all created and deleted environments 🎉.

Updated the mockup to reflect the agreed upon design. Please see images below.

Attaching the images from the latest design discussion we had. Our main objectives were surrounding usability and reducing visual clutter wherever possible.

It came to my attention that the previous images are not showing up for others despite looking good on my end. This is my attempt to fix this, hopefully that works.

Created some mocks for what we could do on the front-end side to represent the Wikifarms on Patch demo. The current version has it such that :

• If 'CampaignEvents' extensions is clicked, the option to create as a wikifarm becomes enabled and so does the text box asking for how many of them to create (probably should do a drop down and have an upper limit for this)
• Once decided, the creation process happens as it would normally but the screen lasts longer as it would need to complete all wikifarm wikis.
• When done, the wikifarm created will be displayed on the table similarly to how other wikis are except there will be a clickable option that exposes all the wikis that are contained in a wikifarm.

The bot now announces creation and deletion of both legacy and catalyst backend environments created. My most recent tests were done on staging with the merged API changes and the creation and deletion logs can be seen on the test task.

This was fixed and merged. Staging is now back to normal.

The UI was affected by recent changes that converted the wikis table into a form which inadvertently made the form rule on max-width also apply to the main wiki "table" (in quotes because it is now a form not a table by definition) . This limited width should not be applied to the wiki "table". The display looked as follows:

PatchDemo! Sorry for the unnecessary ping, will delete soon :)

From my investigation into this, I found the following about potentially using OpenTofu for infrastructure and configuration management on Catalyst: