The Special pages for Content translation is hack-ish approach to get minimal page template, removing sidebar and other page items. This was done in 2014 by sub classing SpecialPage. This worked well, but occassionally required changes since it uses internal skin and SpecialPage method for this customization. Also, issues like T259577: ContentTranslation must provide an element #mw-content-text causes issues to other code that assumes certain structure for a mediawiki page. There is also a problem of unused code from skin.
So there was a suggestion by Jon Robson to create a custom skin for Content Translation. This ticket is to capture its development.
- Create a custom skin to match the design of Content translation special pages. It should have the top header(logo, menu dropdown). Should be responsive, mobile friendly. It should not use OOUI or Vue or Jquery so that skin does not comes with a UI library. Better if skin does not require javascript at all. Testable in arbitrary pages using useskin=contenttranslation
- Disable this skin from public listing by adding to $wgSkipSkins. This must be done before merging the skin code
- CX3(Vue Section translation system) can be the first candidate to switch to this skin to evaluate and test without exposing to wider set of users
- Migrate Special:CXStats to this new skin
- Migrate Special:CX to this new skin