/* Cascade layer order for the blog. Loaded FIRST, before every other sheet.

   Layer order is fixed by first appearance, and later @layer statements only
   append names not already seen -- which is why fh-tokens-landing.css can keep
   its own `@layer reset, base, layout, components, patterns, utilities, page;`
   verbatim: by the time it is parsed every one of those names is already
   ordered, so its statement is a no-op. That is what lets the fh-* files stay
   byte-identical copies of the landing's.

   `blog` is Type-on-Strap, wrapped by assets/css/main.scss. Its position is the
   whole trick and it is pinned on both sides:

     ABOVE `base` and `reset`, because fh-reset.css carries
     `a { color: inherit }`, `body,h1-h6,p,blockquote,ul { margin: 0 }` and
     `img,svg,video { display: block }`, and fh-base.css sets the body face to
     Urbanist. Below those, the blog would lose every article link colour, all
     prose spacing, inline post images, and Inter body copy.

     BELOW `components`, because that is what lets .fh-nav__links{display:none}
     beat the theme's bare nav{display:flex} -- otherwise the desktop bar
     renders on top of the drawer at every width -- and lets .fh-nav__link beat
     `nav a{}`, and .fh-foot__list{margin:0} beat `ul{margin-left:1em}`.

   `bridge` is last: assets/css/fh-blog-bridge.css, for the conflicts layers
   cannot sort. See that file. */
@layer reset, base, blog, layout, components, patterns, utilities, page, bridge;