Skip to content
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 the site tagline to be a heading #59523

Closed
carolinan opened this issue Mar 2, 2024 · 1 comment · Fixed by #59654
Closed

Allow the site tagline to be a heading #59523

carolinan opened this issue Mar 2, 2024 · 1 comment · Fixed by #59654
Assignees
Labels
[Block] Site Tagline Affects the Site Tagline Block [Type] Enhancement A suggestion for improvement.

Comments

@carolinan
Copy link
Contributor

carolinan commented Mar 2, 2024

What problem does this address?

There is no way to change the HTML tag of the site tagline from a paragraph.
By enabling the the tagline to be a heading or paragraph, users and designers have more freedom to customize their site.
For example, the tagline could then be a heading above a blog.

What is your proposed solution?

Allow the site tagline to be a heading as well as the default paragrah.

@carolinan carolinan added [Type] Enhancement A suggestion for improvement. [Block] Site Tagline Affects the Site Tagline Block labels Mar 2, 2024
@huubl
Copy link
Contributor

huubl commented Mar 4, 2024

+1 I think this issue isn't isolated and impacts other blocks too. Introducing a tagName block support could potentially enhance flexibility. Something like:

supports: {
  tagName: ['p', 'span', 'h1', 'h2', 'h3', 'h4', 'h5', 'h6']
}

This would enable easy modification of the HTML tag for the site tagline and other blocks, similar to the current functionality of TagName in the core/group block.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Site Tagline Affects the Site Tagline Block [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants