class, name, style are all modifiers to a tag. They are stacked by placing them in a list inside the angle brackets after the tag label. The white space (blank, tab, cr etc.) is the delimiter. Nesting multiple tags so that each modifier can be alone in it's own set of brackets is inviting error when it comes time to manually edit. It also leaves the maintenance programmer in serious doubt as to whether the nesting is needed or if it is just to separate the modifiers. By not nesting you are giving the maintainer a little less of a problem
I have been hacking pre-existing code for almost 30 years now. I much prefer code that is cleanly formatted with a minimum of unnecessary clutter. I hate code-generator code with a purple passion. Bad formatting, dead code, strange constructions that are easy to build by algorithm and are a nightmare to read and other such problems. All of these are a nightmare (read wasted hours) for a maintenance programmer.
When using a generator to build a webpage at least run it through a 'beautifier' & lint filter so that the result is somewhat readable ... Meaningful comments are nice to, but I have learned that is usually expecting too much
Unnecessary nesting & dead code are 2 things I always remove from code I am editing. It makes bug search & future modifications so much simpler.
The adventure continues
All wonderful in theory but the code for this site is probably generated on the fly and it may not be possible to have it modify the code in the way you want just to add color to the titles. It is apparent that the span color was an add, and it is simply inserted there, if it is simply closed it will probably fix the issue people are having.