There's been a lot of talk recently about files that are not components.
Questions I'd like to find answers for:
1) After https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Vector/+/578660/ is merged the master templates are called `index.mustache` (new) and `legacy.mustache` (old). Are these names acceptable and meaningful given the split? Should we rename to e.g.
* `index` and `index-legacy`, or
* [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Vector/+/578671/ | PageLayout ]] and `PageLayout-legacy`, or
* `layout` and `layout-legacy`, or
* `master` and `master-legacy`?
2) Do we need to refactor any of the existing template to create new components that have been suggested? If so what are the scopes of these components?
* `#content.mw-body` to [[ https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Vector/+/578660/ | Content.mustache ]], `Content.less` and [[ https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/585367/2/resources/skins.vector.styles/Content-legacy.less#1 | Content-legacy.less ]],
* Common root of VectorTabs (`#mw-head`) to ArticleTools
* Logo (`.mw-logo`)
3) What are the guidelines for using template partials? I (@Jdlrobson) believe that we should only use template partials for the purpose of loops or inside the master template and try to avoid them if we can. Template partials within template partials are a potential sign that our templates have got overly complex (Yo-Yo problem) and are likely to suffer from the same issues that we see with class inheritance.
* Note from @Demian: Template partials are the equivalent of composition in OOP (best practice), not inheritance (long-term issues).
4) What common language can we (engineers, designers) agree on. See also: [[ https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements#/media/File:Annotated_Wikipedia_Vector_interface_(logged-out).png | design nomenclature ]].