` skeleton would
run its paragraphs edge to edge.
That is not hypothetical — post_content is editable in wp-admin, and the
failure is silent and ugly. This rule gives the container treatment back to
BARE block-level prose that sits directly in or in the post-content
wrapper. It deliberately targets leaf prose elements only:
• it must NOT match the post-content wrapper itself, or every page would
be re-boxed one level down and PF-064 would simply move;
• it must NOT match `.hzo-section`, which is the whole point;
• it must NOT match block wrappers (.wp-block-group and friends), which
own their own alignment.
:where() keeps the ancestor part at zero specificity and :is() over element
names lands the whole selector at (0,0,1), so anything with a class beats it
without a fight. Padding mirrors _base/container.css exactly.
Correct authoring still wins: wrap the content in the section skeleton. This
is the net under the trapeze, not the trapeze. */
:where(main, .entry-content) > :is(p, h1, h2, h3, h4, h5, h6, ul, ol, dl, blockquote, pre, table, figure, hr) {
max-width: var(--container-max-width);
margin-inline: auto;
padding-inline: var(--space-md);
}
@media (min-width: 480px) { :where(main, .entry-content) > :is(p, h1, h2, h3, h4, h5, h6, ul, ol, dl, blockquote, pre, table, figure, hr) { padding-inline: var(--space-lg); } }
@media (min-width: 768px) { :where(main, .entry-content) > :is(p, h1, h2, h3, h4, h5, h6, ul, ol, dl, blockquote, pre, table, figure, hr) { padding-inline: var(--space-lg-2); } }
@media (min-width: 1024px) { :where(main, .entry-content) > :is(p, h1, h2, h3, h4, h5, h6, ul, ol, dl, blockquote, pre, table, figure, hr) { padding-inline: var(--space-xl); } }
@media (min-width: 1250px) { :where(main, .entry-content) > :is(p, h1, h2, h3, h4, h5, h6, ul, ol, dl, blockquote, pre, table, figure, hr) { padding-inline: var(--space-2xl); } }