Expected Visual changes
| Skin | Before | After |
| Modern | {F53342262} | {F53342280} |
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 skins with approx < 1% of users - CologneBlue, Modern, Timeless, Nostaglia , Monobook (merge by end of day 20th)
- A User-notice should be filed T365078
- The configuration is updated to support the rendering of the new heading markup
- Logstash is monitored and we address any problems with gadgets relating to this change.
Not done
- 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 (merge on 28th)
Reason: We found errors so deferred this to sprint 5.
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. > T365736
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.