Clarify hero background fallback in inner page layout spec
This commit is contained in:
@@ -41,13 +41,13 @@ Changes:
|
||||
- Render `hero_vector` as an absolutely-positioned, right-anchored, bottom-anchored `<img>` inside a new `.page-hero__vector` container, with `aria-hidden="true"` and `role="presentation"`.
|
||||
- Stop rendering the `intro` paragraph inside the hero. The `intro` field is now rendered in the new page-intro partial. (The heading still renders inside the hero, so the page title and the optional heading override work as before.)
|
||||
- Keep the `heading`, `breadcrumbs`, and `call_to_actions` rendering unchanged.
|
||||
- When no `hero_image` is set, the existing `background_color` (or the default dark gradient) is the only background.
|
||||
- When no `hero_image` is set, the existing `background_color` style (or the default `bg-dark` token) is the only background.
|
||||
|
||||
Both new images are `loading="lazy"` and decorative.
|
||||
|
||||
## Hero Partial CSS — `views/partials/page-hero.css` (new)
|
||||
|
||||
The partial needs a small CSS file for the absolute positioning and mask treatment that Tailwind utilities do not express cleanly. Inline styles in the partial are acceptable as a fallback if a CSS file is undesirable, but a dedicated file follows the project's existing pattern (`contact-block.css`, `homepage-hero.css`).
|
||||
The partial needs a small CSS file for the absolute positioning and mask treatment that Tailwind utilities do not express cleanly. A dedicated file follows the project's existing pattern (`contact-block.css`, `homepage-hero.css`).
|
||||
|
||||
Rules:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user