put more specific html ids at the start

[M-Kusumgar]

No description provided.

[david-mears-2]

I merged a package version update from 1.1.3 to 1.1.4 into main via #56, but then when I tried to publish the new version to npm from main, I got

403 Forbidden - PUT https://registry.npmjs.org/@reside-ic%2fskadi-chart - You cannot publish over the previously published versions: 1.1.4

so you must have published from this branch already. Now we have two conflicting ideas in the git history of what 1.1.4 refers to.

I'm not sure how best to prevent this happening in the future - I feel like we prefer to relax the norm that 'you can only publish versions from main' so that wodin or vaxviz can build off specific WIP branches. We could say that WIP versions published for that purpose should use a pre-release version number like 1.0.0-alpha or 1.0.0-alpha.1 or 1.0.0-beta, with the flag npm publish --tag alpha or npm publish --tag beta.

In any case, it would probably help if we always communicated when we are about to publish a new version to npm.

[david-mears-2]

just leaving a comment to remind to make sure this increments from main, or at least does not decrement