What we currently use in most manuals is (b). That’s dozens of official manuals and hundreds of third-party manuals.
Introducing a second official layout with tiles instead of the table of contents is fine in my opinion, but we should point out when we want to use which one. My opinion on this is:
- TOC: For many main menu items.
- Tiles: For a few main menu items where the titles are intuitively clear to the normal reader. It should not end in endless scrolling, especially on mobile devices.
The second decision relates to metadata: I echo Sybille: “The metadata […] down there looks a bit weird to me.”. It looks like a programmer solved a UX problem on-the-fly. My opinion on metadata is:
- It should be at the top of the document, especially for mobile device users who would otherwise have to scroll all the way down.
- They shouldn’t take up too much vertical space so that the reader can immediately see the abstract text of the manual, which has been accomplished by removing things like “keywords” etc. in recent documentation standard runs.
- It should be of value to the reader, which is accomplished by allowing the reader to take a quick look at the state of the manual before diving into it: Has it been rendered recently or is it likely to be out of date, has the correct manual been loaded or is the version switch broken, for which extension key and package name is this manual correct, and so on. Such a check after reading the summary and table of contents/tiles would sometimes waste the reader’s time unnecessarily.
- It should follow the best practice of other types of documentation, such as a dissertation, letter or email, where the metadata is at the top and then the abstract/subject and text.
In any case, any change to the documentation should be documented in the documentation standard and applied to all official manuals.