The attributes would be split from the text which refers to the image (
![image](src)), and rather reside on the cms’ database or whatever. And by the following I get that that’s exactly what’d you prefer:
But my point was always that the attributes are not always just presentational, but also inherent properties of the content. So that they shouldn’t be separated and still be copied over. So that the other system can also present the differences specified by the attributes if they so desire/think it’s meaningful to do so.
If auto-generation of heading anchors is accepted into the spec, then it’s most imperative that there’s a custom method to override them, in case of conflicts between two same IDs. The syntax proposed here makes the most sense as it’s widely used already, so minimal backwards compatibility issues.
dir, at least for the code blocks example.