Talk:Reading/Web/Projects/In-page Navigation

Hello,

I love those concepts and would like to implement concept 3 to my internal wiki. However I can't find information on how to implement those features or what extension the features have been implemented with.

I tried the "CollapsibleSections" extensions and it is not compatible with my version of mediawiki.

Do you have further information on how I could implement the features from concept 3?

Best regards

Edit: I just realized that this only exists for mobile pages? I wonder if there is a similar feature for the desktop version?

I, quite frankly, would love to see any of these changes rolled out for mobile view since currently there's no form of navigation. Implementation of any of these single concepts would be great.

I've tested the four design concepts on my mobile via your link and here's what I felt with each one of them:

• Jump to top button: quick and simple, but I felt it would be better if it appeared as soon as I scrolled down...not only after I scroll up. Till then, I wondered about its existence.
• Collapse and scroll: quick and simple, no complaints.
• Sticky headers: feels nice, but didn't find it practical when it came advanced navigation. True, I could say the same for the above two, but they were designed to be simple.
• Sticky headers become TOC: This solves my advanced navigation problem. Quick thing which occurred to me though: it being positioned top-left versus the App having it bottom-right made it cumbersome to move my thumb back-and-forth. People usually use their right hand finger to scroll, so I guess that's the reason the App has it positioned there. Also there's the long term issue of showing lower level <h2 sections like how they did.

Great work so far with all this!

@Ugog Nizdast thanks for engaging here and trying out the demos. It is awesome to see that the proposed feature would be useful to you. At the Wikimedia Foundation we are in the midst of our annual planning process (the annual plan is published in June) and I am certainly advocating for this feature to be worked on. Hopefully we can get some time to work on it soon.