I feel like this might be a little more complicated than the ticket suggests, and we might need additional clarification to figure out how to do it right. Gary noted above:

When a collection page is first loaded (via a breadcrumb link, search result link, etc.), the first item in the collection overview nav should be highlighted.

...which doesn't seem to happen in #1339 if you load, for example, /catalog/aoa271 directly. That makes sense; when the page has initially loaded, none of the sidebar links have been clicked. The implication is that when viewing the collection, the first thing you see is the summary, so it should appear the same as if you'd already clicked "summary" (with the #summary anchor active).

This gets a little weird when you throw scrolling into it. If I scroll down the page to look at "background", the "summary" link will still be highlighted in the sidebar, even though I'm not "looking" at the summary section anymore. You don't notice this right now because the sidebar scrolls away along with the main content, but #1312 will make it sticky, so it'll be more obvious.

To me, the behavior that fits Gary's notes above is actually something more like bootstrap's scrollspy: highlight something based on where the user is currently "looking", i.e. what part of the page's content is currently in the viewport. That satisfies the conditions:

• something is always active/highlighted, because you're always "looking" at a part of the page
• when you scroll to a section of content farther down, the highlighted link automatically changes
• if you click something in the sidebar, you jump to that section (current behavior)

Discussion: Justin's PR #1339 is a subset but perhaps not covering all the bullet points in this ticket.
We decided to wait to work on this ticket until Gary's return.

@thatbudakguy Yes, what I was suggesting is the scrollspy behavior. As you note, #1312 is also needed to make this behavior work in the most ideal way (ensures the user can always see the highlighted overview section that they've selected). I guess I assumed at the time that #1312 was pretty straightforward and that would be in place for this ticket to work with.

I'm not sure if I'm missing any other hurdles or concerns about doing this, but am happy to meet to discuss in more detail.