-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow blocks to render semantic tags for full-site editing #20200
Comments
I have a few thoughts on this:
It'd be interesting to then register variations of the group block for |
I opened PR with proof of concept for Section variation for the Group block. Feel free to play and adjust #20218 if necessary 😄 |
It also raises question marks about how to prevent users from altering the tags and creating a mess for accessibility (and SEO). |
An initial version shouldn't expose this in the UI, I recon. Whenever it becomes a user-facing feature of the group block, it should come with the corresponding analysis of content structure to indicate problems or help educate. |
As we've been working through themes in the theme-experiments repository, a few of us have quickly run into the fact that Gutenberg currently can't render semantic tags like
<header>
,<section>
,<aside>
, and<footer>
.Functionally, these would probably just be Group blocks but with different markup: they're just a place to put other blocks. So perhaps this would be some sort of option for that block, only available in full-site editing? Or maybe there's some way we can automate this to avoid confusion for users?
The text was updated successfully, but these errors were encountered: