We've moved to a paginated nav framework, after our knowledge bases expanded to a point where Top Nav was no longer feasible. Pagination uses a bit of JS to slide div blocks of content in and out, as the user navigates through paginated tabs of topic blurbs.
Not an out of the box solution of course, but it works great, leveraging Flare's TOCs to set up the paginated tabs. However, breadcrumbs don't carry over well. TOC endpoints that point to single articles are fine. But folder-level TOC entries require JS to get the correct tabset loaded, and need a 'handle' to achieve this.
Has anyone found a way to add an attribute or a query string to the link specified in TOC entry > Properties? That is, this field:
For some bizarre reason, Flare treats a query string in any URL in this field as equivalent to a bookmark, and does two things:
1. Reports the query string as a 'Failed to find bookmark' warning in the build log.
2. Strips the query component from the href when it builds the bookmark <a>.
The query string is harmless, so I've no idea why it would be stripped out when the bookmark link is built.
The best way of adding a handle would be to add a 'data-' attribute. However, if you try adding a URL to this field like so:
Code: Select all
/Content/KB_Home.htm data-target="GetStarted"
Long shot, but has anyone ever tried inserting an attribute or appending anything to a TOC link like that? If I just wanted to trigger generic behaviour when a TOC element is clicked I can just use a selector, but I want to trigger behaviour based on the value of the TOC entry.
Workaround
A possible workaround would be to have a dummy file filled with dummy anchors to point to, so that Flare happily retains any # or ? component of the URL, but what a palaver. Still, worth a shot.
Thanks.