That’s how I use IDs’ too, in small doses on the page. For elements that are only used once, as IDs’ were intended.
I find that the child elements in my header and footer are most often unique anyway so I’m not having to set up a new class or override one.
Just recently ran across a piece of code that would have got real messy with multiple classes , IDs’ were an efficient way to handle the differences.
As long as one understands the weight and specificity that IDs’ carry then they understand when to use them. A newcomer may not have that knowledge under their belt yet and can easily get themselves backed into a corner.
Sam did have a disclaimer statement at the end of post #36 ![]()