@maga,
I spent several hours last night downloading a list of all of the links from the guides in the old community and a list of all of the links from the new community. As part of that, I spent a bunch of time looking at the HTML on each page.
The new community has much cleaner HTML. Jive had a tag for everything. The jive_content_id_Pages URL fragment that you mention is very specific to Jive and will likely not be implemented here, it wouldn't make sense for Khoros to have a bunch of Jive tags floating around.
But the picture was even bleaker for linking to things. Each of those sections in the new guides is marked up with a section header. That's good semantic use of HTML. However, there are no identifying attributes on the on the section. It looks like this:
<section>
<h4>Pages</h4>
<ul>...</ul>
</section>
What would need to happen for scrolling to a specific section to work would be to put an id=pages attribute on the h4 element. Just calling it pages could be problematic in some cases as I found that Khoros uses some very simple words for IDs: example, the breadcrumb is id=list. Canvas would need to make sure that their IDs were unique enough to not cause problems as IDs must be unique per the HTML specification. Perhaps id=toc_pages or id=section_pages would be a good name. But it probably won't be jive_content_id_Pages.
Chrome 81+ supports "Scroll to Text Fragment", which allow you to use #:~:text=Pages and it will find "pages" on the page and scroll to it. It's not case sensitive, so it finds pages as well as Pages. Trying that here will take to "How do I organize my ePortfolio pages as an instructor?" because that's the first occurrence of "pages" on the page. It also highlights "pages" in yellow. Browser support is extremely limited. Chromium based browsers like Chrome and the last two versions of Edge support it. Of the major browsers, it leaves out Firefox and Safari completely. About 66% of browsers have support for it.
In order for you to be able to link to a section, two things need to happen.
- The headings need to have IDs on them.
- There would need to be a mapping between the old query fragments and the new ids.
I see a lot of people asking about a table of contents. The first item would have to happen before a table of contents could be created.
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.