Change Details

**Feature summary** (what you would like to be able to do and where): After discussing {T340606} I’ve tried looking into some of the ways a person can discover hidden categories and discovered that currently, the list of page properties on action=info page is borderline unreadable on any large page. Example: - https://ru.wikipedia.org/wiki/Ильин,_Иван_Александрович?action=info - English version: https://ru.wikipedia.org/wiki/Ильин,_Иван_Александрович?action=info&uselang=en A list of 173 templates is listed in a very long table cell, same with everything else. I think we should drop the table in that section and put the lists to be multi-column under separate headings for each type of page property, so they can be scanned more easily and quickly, similarly to what is done on https://en.wikipedia.org/wiki/Special:SpecialPages (but preferably with no column count restriction). It should be hopefully relatively easy to implement. There is also an issue with accessibility of the page because it uses a bunch of table row headers that aren’t marked as such (`<td>` → `<th scope="row">`), but that’s harder to fix given that default styling for `wikitable` class would make the tables look worse. Tables also lack <caption> element in all cases. (I am listing all of this here because filing tasks on Phabricator for every issue is too complicated.)

**Feature summary** (what you would like to be able to do and where): After discussing {T340606} I’ve tried looking into some of the ways a person can discover hidden categories and discovered that currently, the list of page properties on action=info page is borderline unreadable on any large page. Example: - https://ru.wikipedia.org/wiki/Ильин,_Иван_Александрович?action=info - English version: https://ru.wikipedia.org/wiki/Ильин,_Иван_Александрович?action=info&uselang=en A list of 173 templates is listed in a very long table cell, same with everything else. I think we should drop the table in that section and put the lists to be multi-column under separate headings for each type of page property, so they can be scanned more easily and quickly, similarly to what is done on https://en.wikipedia.org/wiki/Special:SpecialPages (but preferably with no column count restriction). ``` <h3>Templates used on a page</h3> <ul> … </ul> …etc ``` It should be hopefully relatively easy to implement. There is also an issue with accessibility of the page because it uses a bunch of table row headers that aren’t marked as such (`<td>` → `<th scope="row">`), but that’s harder to fix given that default styling for `wikitable` class would make the tables look worse. Tables also lack <caption> element in all cases. (I am listing all of this here because filing tasks on Phabricator for every issue is too complicated.)

**Feature summary** (what you would like to be able to do and where): After discussing {T340606} I’ve tried looking into some of the ways a person can discover hidden categories and discovered that currently, the list of page properties on action=info page is borderline unreadable on any large page. Example: - https://ru.wikipedia.org/wiki/Ильин,_Иван_Александрович?action=info - English version: https://ru.wikipedia.org/wiki/Ильин,_Иван_Александрович?action=info&uselang=en A list of 173 templates is listed in a very long table cell, same with everything else. I think we should drop the table in that section and put the lists to be multi-column under separate headings for each type of page property, so they can be scanned more easily and quickly, similarly to what is done on https://en.wikipedia.org/wiki/Special:SpecialPages (but preferably with no column count restriction). ``` <h3>Templates used on a page</h3> <ul> … </ul> …etc ``` It should be hopefully relatively easy to implement. There is also an issue with accessibility of the page because it uses a bunch of table row headers that aren’t marked as such (`<td>` → `<th scope="row">`), but that’s harder to fix given that default styling for `wikitable` class would make the tables look worse. Tables also lack <caption> element in all cases. (I am listing all of this here because filing tasks on Phabricator for every issue is too complicated.)