You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pull out all headings for the current page to show them as a section listing, similar to page contents in Wikipedia example.
I have some reservations about this pushing down the main content. One thing I'd like to try is to have it shown by request, as a pulldown from the fixed header. (Currently that header is not fixed in place for a good reason, but I've had in mind to build interactive features into it an this is a good candidate.)
It's possible there will be some confusion between this contents and the full-pamflet contents that appear at the bottom of each page. How can this be logically resolved? Would it make much more sense to have the current page's section content's be nested into the main contents? If so, then that has to go up top, and significantly push down the content. It can not be interactively displayed because the browser's "find in page" feature should always be able to find the names of other pages, IMO.
The text was updated successfully, but these errors were encountered:
I'm pro top nav for in-page navigation. I've been playing the twttr's new api docs and really like the new jump-to nav
If I ever getting around the finishing scholia I'm borrowing the jump-to used in docco annotated sources which works the same.
Wrt the main index. It works really well on the first page but not so much on content heavy pages. The next/prev nav work really well for navigating linearly through that content. When I'm reading through pamflet docs I feel like I'm readying a book (which is good) but books dont normally have a toc at the bottom of every page. What about a dedicated toc page? Kind of like a real book. You could link to it by clicking the title in the header that doesn't scroll for quick access.
Yeah, something like twitter's "jump to" dropdown is what I was imagining, integrated into the header.
The way I look at the pamflet contents is that it is effectively cost-free for them to be at the bottom of every page, and as I said I like being able to use the browsers type-to-find to search for page names. It's also context some when you finish a page, to see where you are in the pamflet.
Pull out all headings for the current page to show them as a section listing, similar to page contents in Wikipedia example.
I have some reservations about this pushing down the main content. One thing I'd like to try is to have it shown by request, as a pulldown from the fixed header. (Currently that header is not fixed in place for a good reason, but I've had in mind to build interactive features into it an this is a good candidate.)
It's possible there will be some confusion between this contents and the full-pamflet contents that appear at the bottom of each page. How can this be logically resolved? Would it make much more sense to have the current page's section content's be nested into the main contents? If so, then that has to go up top, and significantly push down the content. It can not be interactively displayed because the browser's "find in page" feature should always be able to find the names of other pages, IMO.
The text was updated successfully, but these errors were encountered: