CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

adobe/stardust

Redesign an existing website to make it better. Built on top of impeccable.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

step-6-chrome.mdskills/deploy/reference/

stardust:deploy: step 6, chrome

The text of this part of skills/deploy/SKILL.md, which keeps the heading and points here. "Above" and "below" refer to the order of the sections in that file.

6. Chrome — authored /nav + /footer documents, template-slotted header/footer blocks

Chrome is the canonical fragment use case (D12): content lives in two authored DA documents — content/nav.html and content/footer.html — and presentation lives in the per-site blocks/header and blocks/footer CSS/JS. The stock blocks fetch the documents (loadFragment('/nav') / loadFragment('/footer'), path overridable per page via nav/footer metadata); you replace their demo CSS/JS with the prototype's chrome. Nav links become authorable; block JS runs, so interactive chrome is REAL JS, not CSS hacks.

The nav/footer documents (ENCODE side). Same body-fragment format as any content page (Step 9), deployed and published through the same chain — they must be on the publish roster or the chrome 404s. Content is default-content only, structured by sections:

  • content/nav.html: section 1 = brand (logo link), section 2 = the nav link list (<ul>), section 3 = tools/CTAs (the stock header block reads exactly these three sections into .nav-brand / .nav-sections / .nav-tools — keep that contract so the hamburger logic keeps working).
  • Nav DECODE: the pipeline wraps each list item's trigger link in a <p> on live (#98). The authored/harness shape is <li><a>…<ul>, the delivered shape is <li><p><a></p><ul> — a :scope > a trigger lookup and any .nav-links > li > a CSS silently miss on live while the harness passes (the #79 class, hitting chrome). Normalize in decorate(): match :scope > a, :scope > p > a and unwrap the <p>. Verify the desktop nav's STYLED render on the deployed preview, not just the harness.
  • content/footer.html: one section per footer band (link columns as lists, legal line, social links). The footer block renders them in order.
  • Images (logo) follow the standard editorial-image rule: upload to DA /media, author a content.da.live <img> — the pipeline emits <picture>. Internal links root-relative; external fully-qualified (D4).

The header/footer blocks (DECODE side) — template-slotted (#95), pixel parity by construction. Replace the demo CSS of blocks/header/header.css with the prototype's chrome CSS (scoped under header .nav-* / footer .footer), and adapt header.js's decorate() to build the prototype's chrome DOM verbatim, slotting the authored content by role — logo into the brand slot, each authored <li> link into the nav-link template, tools/CTAs into their slot. Behaviour comes from the header contract (stardust/chrome/header-contract.json, ../diff/SKILL.md § The header contract): each control, the action that opens it (hover, click, Enter), what its panel shows, its close paths, focus, scroll lock and motion, at desktop and mobile. The stock machinery (toggleMenu, aria-expanded, Escape and focus-out close, isDesktop) is the accessibility floor to extend, never the target: runs that kept it shipped one-level click dropdowns for hover mega menus. A mega-menu panel is authored content: nested lists in /nav, or one nav fragment per top-level item (/nav/<item>, loaded on first open, published with the nav) once a panel holds more than a few dozen links. Search, cart, account and locale reproduce their UI (overlay, typeahead, drawer, empty state); data a backend serves is a dynamics row the site owner decides.

  • Lift the chrome element's OWN box styles (#31) — margin, padding, border set on the prototype's <header>/<footer> element itself — onto header/footer (the host elements sit OUTSIDE <main>), not just the inner content styles. The gap between the last section and the footer comes entirely from the footer's own top margin (e.g. footer { margin-top: 72px }). Easy to miss: the inner content looks right while the footer sits flush against the last block.
  • Root-class hook (#26): the block renders inside header .header / footer .footer. If the prototype's chrome styling is keyed to a different root class (e.g. .utilnav / .site-footer), have decorate() emit a <div class="<that-class>"> wrapper so the lifted CSS matches unchanged.
  • Multi-row chrome (utility bar + nav): author the utility bar as an extra section in /nav; the header block slots it above the nav row. Update --nav-height (#81) to the combined height.
  • Never pair a fixed height with vertical padding on a chrome row. Under the global border-box reset (#106) height: 40px; padding-top: 12px shrinks the content box to 28px and mis-centers every utility-row item by 6px — one declaration, a whole-chrome offset (recorded). Chrome rows size from content (min-height when a floor is needed); before deploy, grep the chrome CSS for height: co-occurring with padding on flex rows.
  • Hover dropdowns need a contiguous hover surface. A sub-list placed below the trigger <li> with an offset (top: calc(100% + Npx)) closes when the pointer crosses the gap (recorded: 5/5 desktop dropdowns unreachable behind green crops). Span the <li> over the nav row with the sub-list at top: 100%, or (replica) bridge the gap with an invisible ::before on the sub-list, off in the mobile query; qa's dropdown-unreachable walks the pointer path.

What still can't run (#20, #102): authored content never carries <script> (D15), and EDS's delivered CSP (script-src 'nonce-…' 'strict-dynamic') means inline on* handlers in ANY markup never fire. Forms in chrome (a newsletter signup in the footer) are wired in BLOCK JS: render the <form> from the block, attach a real submit listener in decorate(). Scroll-state chrome (sticky shadow, shrink-on-scroll) is wired in the header block's JS. Block dependencies must not compile WebAssembly (#102): the CSP has no wasm-unsafe-eval, so WASM-based players (dotlottie, wasm codecs/parsers) silently fall back on every REAL environment while working locally — for Lottie use lottie-web's pure-JS svg renderer via a pinned-CDN module import() (strict-dynamic trusts module imports). Step 10: check the deployed page's browser console for CSP violations — a graceful fallback hides this class from every layout gate.

Per-page chrome variants: set nav: /nav-minimal (or footer: /footer-legal) in the page's metadata block to point that page at an alternate authored document — this replaces the old header: off switch (there is no stock off switch; a chrome-less page points at a minimal nav doc you author). Multilingual sites route the same way: /fr/nav, /fr/footer.

skills

README.md

tile.json