/* Single blog post: template layout and body typography. Enqueued only on is_singular("post"), the same one-stylesheet-per-template rule css/product.css and its siblings follow. Not part of the Tailwind bundle, and it cannot be: Tailwind builds CSS by scanning files, and a post body lives in wp_posts.post_content where no scanner can see it. Two halves, and the split matters. The g80-post__* rules style single.php, which this theme owns. Component classes, chosen freely, and safe to select on. Everything under .entry-content styles the BLOCK EDITOR'S OWN MARKUP, where there is nothing to choose. A post is written in wp-admin and the editor decides the markup: paragraphs come out as p, headings as h2/h3, and any class typed into pasted HTML is dropped on the way in. So those rules infer meaning from position: the strong-led paragraph after a heading is a caveat, the last two paragraphs are the citation and the disclaimer. That is inference, not markup, so each is written to degrade to plain prose rather than to something wrong when a post is shaped differently. Nothing here hides content or reorders it. One earlier decision is reversed here. This file used to match headings as h2.wp-block-heading, on the grounds that the editor really does store that class. It does, but bare h2 covers the same posts plus any older heading written before the block editor stored it, and an h2 that matches nothing falls back to the font-size: inherit reset in css/wordpress.css and renders as body text. The narrower selector bought nothing and could only lose. Specificity, and why the body selectors look over-qualified. Six rules target this page from the DATABASE, not from this repo, out of two different Customizer surfaces. Both print inline in , after every enqueued stylesheet, so they win any specificity tie on source order. Customizer > Additional CSS (