Autonomy over markup in Gutenberg and FSE

[skysarwer]

It seems that the direction being taken with FSE is taking away a lot of autonomy over rendered markup from theme authors. Template areas are automatically given a class "wp-template-part". Blocks can be given class names as dense as "wp-container-block-2323u82932239", and of course, there is that large amount of inline styles with presets starting with "--wp--preset--..."

I know there is the ability to register custom presets such as "--wp--custom--...", however, I do not think this is enough.

While it might seem trivial to many, I believe that autonomy over rendered markup, including filtering out the WP prefixes from class names, or opting for very lean, minimalist classes, is important to many and should be protected as WP Core expands into new functionality.

There is something that feels right about inspecting the source code of a document and finding, clean, sane classes.

Should there be more controls to override markup (examples: removing WP prefixes, registering custom prefixes, controls to modify the markup that template parts are rendered with , that blocks are rendered with? )

I see good markup as an art form, and taking away control over that is painful to me. I am very excited about the opportunities that FSE is presenting, but I can't seem to get over this. Am I alone? Do others feel the same way? Or have different thoughts?

I would really love to talk about it.