Feature summary:

Special:Namespaceinfo currently specifies various information in one cell of a table, e.g:

This includes:

• Whether pages in the namespace the can have subpages (but not if they can't)
• The standard content model of pages in the namespace
• Whether pages are considered "content pages."
• Whether there is a restriction on editing pages with a particular user right.

There is potential to add page counts to this as I have suggested elsewhere T385002: Special:NamespaceInfo should include counts of {{PAGESINNAMESPACE}}.

Use case(s)

It would be better if each of these things were their own separate column with the value recorded in the relevant cell. Values may be TRUE and FALSE if appropriate.

This will make the table clearer and more user-friendly. Currently, I find myself reading the same things over and over again.

I do note that this will have the drawback of making the table less readable on mobile view due to the limited width available, though acceptable for desktop viewing. This seems to be an acceptable drawback, given the page isn't prominent and will mostly be of interest to serious editors and site administrators. Consider enforcing horizontal scrolling to make it viewable on limited width devices.

This adheres to basic relational normalisation and 1NF principles: one attribute per column, one atomic value per cell, and orthogonal namespace properties modelled as independent fields to maximise clarity, queriability, and extensibility.