Use an h5 for callouts

[XhmikosR]

This is so that they are not included in ToC.

[XhmikosR]

Now that I think about it... The header levels for some of the includes don't make sense.

https://deploy-preview-27648--twbs-bootstrap4.netlify.com/docs/4.1/utilities/colors/#conveying-meaning-to-assistive-technologies

They show as children in ToC.

The thing is we can't know the level of the previous sibling item and thus use the same level in the callouts.

So, perhaps we should just hide the callouts' headers consistently?

[patrickhlauke]

nobody dies if a heading level is skipped. unless we have a way to embed callouts at any level, and the callout auto-adapts the level to be subordinate of the last heading level it's at, it's safest to keep the heading level to something guaranteed to be subordinate in every situation...so let's leave it to h5, or heck could even go to h6. whether it's included in the TOC or not is up for debate.

[XhmikosR]

The reason for this PR wasn't the skipped level. Was to show the callout in the ToC. But after thinking about it, I believe it's better if we just hide all callouts instead from ToC.

[patrickhlauke]

if we can guarantee that the callout is only ever included with a preceding h3, and not an h4 or h5, then sure. but i think it's not a major problem even as is.

[patrickhlauke]

ah gotcha,hadn't seen your comment until now. yeah, i think it's fine even if the callouts AREN'T in the TOC

[XhmikosR]

All right, I'm gonna hide them by using an h5.

[XhmikosR]

Actually, it might be a bug in jekyll-toc. Waiting for confirmation/fix toshimaru/jekyll-toc#70

[m5o]

@XhmikosR Consider review/cherry-pick 08b096d from #25838 this should cover the whole list.

[XhmikosR]

Thanks but I want this fixed upstream.

[mdo]

FWIW, I don’t want callouts to be listed in the table of contents. Any of them that are there currently are there unintentionally.

[XhmikosR]

Yeah, I think I will just change them so that they don't show up for now. No idea when this will be fixed upstream.