There's nothing semantically wrong with an extra <div>. I probably should have made clearer in the article, <div>s aren't bad, and there's nothing wrong with using them, just as long as the correct semantic elements are used where their semantics apply. The sort of <div> you're describing doesn't have any semantics to it anyway, so a <div> works fine if you prefer it, and can be useful for layout purposes as well.
By the way, another thing I probably should have made clear in the article is that <header> is not strictly necessary if the only thing inside it is a heading (<h1>-<h6>). It's useful for grouping things, like a heading, an icon, and a section anchor link, and it might be useful for styling purposes, but if you don't need those things, you could just do this:
<h2>Part 1: Variety is spicy</h2>
<p><!-- some cheesy content --></p>
<p><!-- more cheesy content --></p>
That might give you the consistent feel without needing the extra <div>, if you're worried about it.
Any of the three options is fine: <header> + <p>s, <header> + <div>, <h2> + <p>s.
Yes, I like <h2> <p> <p> better, thanks.
(& I think you meant to write divs are "NOT bad" above)
Ha, I sure did 😂 Thanks! Fixed for posterity
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.