RE: https://mastodon.social/@firefoxwebdevs/116680726980295049
i like that this feature encourages local thinking — as long as you can ensure that a portion of a page has correct hierarchy in isolation, `headingoffset` will allow it to fit into a larger outline.
i also really like that you can opt out a subtree using `headingreset`. this is the very first thing i went looking for. https://html.spec.whatwg.org/multipage/sections.html#attr-headingreset
i do think it's best used in moderation.
instead of making everything h1, i would start at h2 in most places (unless of course it's literally a document), with `headingoffset` sprinkled more intentionally.
a page with a hundred h1s is nonsensical, but the same amount of h2s can still make sense.
this could become a common pattern to counter overly zealous use of `headingoffset`:
```
<h2 headingreset>Do not fuck with me</h2>
```
@mayank
I agree. There are a lot of use cases where the contained content also exists as its own page where an h1 world be appropriate but I think there are even more where that's not the case and h2 is a better default.
And that still doesn't mean "h2 all the things!" If a component has more than one heading level, it should still use h3s below its h2 instead of more h2s wrapped in another heading offset.
@cwilcox808 agreed completely!