Background

The content transform team are making changes to the HTML. Thanks to the way this has been built the changes are easily revertable if necessary.

User story

As a user I want minimal disruption to my wiki experience while we migrate from the old HTML format to the new HTML format.

Deployment plan

• The markup is first deployed on opt-in skins - Monobook, Timeless, CologneBlue etc..
• A User-notice should be filed
• Logstash is monitored and we address any problems with gadgets relating to this change.
• Provided we have not identified any issues in 7 days we will then update the markup on Minerva skin and we'll move this to QA
• Logstash is monitored and we address any problems with gadgets relating to this change.

QA

Exploratory testing:

• Test on various projects and languages
• Using mobile skin scroll to any section heading
• Inspect section for any unusual visual differences from normal. For example: do icons look misaligned or out of place; does the section look different from normal.
• Check the section can be exanded/collapsed
• Check any buttons in the heading can be clicked.
• Confirm there are no JS errors in console when clicked.

Communication criteria - does this need an announcement or discussion?

When the date for deploys is known and finalized, a user notice should be filed prior to deployment on Monobook and Timeless by tagging this phabricator ticket with user-notice.

sign off steps

• Create a task for rolling out the change on Vector 2022 and Vector skins.

Roll back plan

Since skins should be backwards compatible with old and new markup it is safe to revert a patch at any stage in the deployment process in event of significant issues. IF significant issues are encountered, work on this task should pause until that is taken care of.