Finsweet’s PRT allows you to add arbitrary HTML markup in your rich text content;
If you’re trying to automatically ID every heading with a unique ID, so that you can save section-specific links, you can likely find a script for that. The IDs tend to be ugly-ish mashups of the heading text, but you’ll usually find that in scripts that make a table of contents from your text.
You’ll find a few auto-ToC examples here in the forum.
Thanks Jeff (@webdev )- in the past I’ve always favored <a name> links for fragment navigation, since it avoids polluting the id namespace which I primarily use for scripting.
However I didn’t realize that the name attribute has been deprecated in HTML5.
Webflow’s scripts also don’t recognize them for section navigation, which means no built-in w--current selector, smooth scrolling, or visibility in the available links list.
@chloecan please change back to using ID’s. It does look like something is interfering with your scrolling nav whichever of the two approaches you use.
Typically that’s due to a duplicate ID, or a script that affects scrolling. It’s possible an interaction could do that as well, though I haven’t actually seen that happen before.
What I’d recommend is, clone your site to a test copy, and then in that clone, selectively remove scripts and interactions until anchor navigation works again.
The content is simple, but you have a lot of scripts.
The most common culprits I see are scripts which customize scrolling behavior, and those which do loading effects. Even cookie consent scripts can interfere, if they try to bring navigation to their own pop-up at the moment of page load.
I’m suspicious of your sitesearch360 scripts because they appear to have some sort of loading animation.
But there are plenty of other scripts too… you have jQuery loaded twice, and some form of authentication & routing code happening in the header. You have also have prism & cookie consent scripts running. Lots of possibilities, let us know what you find.