Concerns about Block Markup (Overriding default Block classes)
-
Hey all,
I am currently studying the new full site editing framework, and I have concerns over markup.
In a block theme where everything is a block, it seems reasonable to me that some instances will want to override the automatically generated classes “wp-template-part, wp-container-6223e85e30a66, wp–is–default–style”, and so on, and so on.
It seems that core developers are envisioning a future where every WP installation has homogeneous, WP branded markup, with custom styling rules applied to these classes (or custom classes added on top of that).
This vision scares me. I think theme authors have the right to establish custom markup if they want. Personally, I am working on a theme framework and I want very minimal, clean markup. Transitioning to FSE and having this new class structure imposed on my project, makes me uncomfortable, even though I very much want to integrate the new, end-user focused features that have been introduced.
Is there any way to override these classes for the core blocks and block templates? I would love to cultivate a discussion on this.
Thank you!
-
It’s also possible to override the default block style using the
classNameattribute when defining block variations.variations: [ { name: 'blue', title: __( 'Blue Quote' ), isDefault: true, attributes: { color: 'blue', className: 'is-style-blue-quote' }, icon: 'format-quote', isActive: ( blockAttributes, variationAttributes ) => blockAttributes.color === variationAttributes.color }, ],See:
https://developer.www.ads-software.com/block-editor/reference-guides/block-api/block-variations/More reading:
https://developer.www.ads-software.com/block-editor/how-to-guides/themes/create-block-theme/#global-styles-presets
https://developer.www.ads-software.com/block-editor/how-to-guides/themes/block-theme-overview/#what-is-the-structure-of-a-block-theme
- The topic ‘Concerns about Block Markup (Overriding default Block classes)’ is closed to new replies.