Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add page-level TOC to aid in navigation, perhaps with overview of length #78

Open
geealbers opened this issue Jan 31, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@geealbers
Copy link
Member

My preference would be to have the ‘expand all’ option set as the default. I’m not sure what the advantage of collapsing is.

The initial collapsed state was very intentional and meant to give users a quick way of scanning the content of the page and finding the section(s) relevant to them. This seems like a more likely use case, as opposed to assuming a majority of readers will come to the page with the intention of reading the whole thing. That said, this may change when considering the following related comment.

Some testers have found difficult/unfriendly to have to open and close each section while proceeding in their reading of a chapter, although they understand what’s behind this editorial choice. They ask whether it is possible to get the table of contents of a given chapter opened in a side box. I (David) quite agree, I rapidly got lost in the chapters since most of them are very technical and dense. Moreover, the sections are often long, which means once opened you need to scroll up a long time before finding the table of content (not mentioning the probably very frequent situation where all the previous sections are still open). One interesting remark from a tester (a French conservator): she would have appreciated to have an idea of the length of a given chapter or CS, as when you have a book in hands. She conceives the Guidelines as a tool she will often refer to/reread.

I wonder if this could be connected to the Expand/Collapse controls? At least in terms of where the controls are located.

@geealbers geealbers added the enhancement New feature or request label Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant