@gemboss/website-ui 0.5.0 → 0.7.0

package/AGENTS.md

@@ -10,14 +10,17 @@ Files you will use, all inside `node_modules/@gemboss/website-ui/`:
 | file | what it is |
 |---|---|
 | `website.css` | the whole kit, one file (tokens, base, layout, components, sections) |
-| `js/website.js` | header, mega menu, mobile menu, theme toggle, scroll reveal, segmented control, busy buttons, an article's contents and its tables' scroll box; no dependencies; `window.gwWebsite.init(root)` |
+| `js/website.js` | header, mega menu, mobile menu, theme toggle, scroll reveal, segmented control, busy buttons, an article's contents and its tables' scroll box, the footer's folds; no dependencies; `window.gwWebsite.init(root)` |
 | `js/website.mjs` | the same script as an ES module for apps: `import { init, destroy } from '@gemboss/website-ui/website.mjs'` |
 | `system.json` | every value of the system: colours, spacing, type, radii, shadows, widths |
 | `templates/page.html` | the page skeleton: start every new page from it |
-| `templates/sections/*.html` | ready sections: hero, features, split, showcase, logos, stats, steps, pricing, FAQ, CTA, prose, article, post list… |
+| `templates/footer.html` | the footer of every site (the footer of gemboss.ai): fill it once, in the site's shared partial |
+| `templates/sections/*.html` | ready sections: hero, features, split, showcase, logos, stats, steps, pricing, FAQ, CTA, prose, article, post list, a short form, testimonials… |
 | `demo/index.html` | every component on one page: open it to see what exists before you build anything |
 | `demo/brand-profiles.html` | a GemPages-style brand: its accent, the accent button, soft corners, the floating header |
 | `demo/article.html`, `demo/blog.html` | a whole blog post (breadcrumbs, meta, contents, prose, callouts, FAQ) and the blog index (post list, pagination) |
+| `demo/forms.html` | fields in every state, choices, the footer newsletter, a short form, stars, the testimonial wall and the rating badge |
+| `demo/footer.html` | the full footer (Ask AI, columns that fold on phones, family rows, theme toggle, wordmark), and the same for a GemPages-style brand |
 | `docs/components.md` | every class, what it is for, its variants |
 | `docs/theming.md` | what a brand other than GemBoss chooses (accent, wash, logo, three named profiles), and what it must not change |
 
@@ -56,6 +59,9 @@ Files you will use, all inside `node_modules/@gemboss/website-ui/`:
 
 1. Copy `templates/page.html` into the site. It links `website.css` and `website.js`, has the skip link, the
    header, the `<main>` and the footer. Fill the header and footer once (they are the same on every page).
+   **The footer comes from `templates/footer.html`.** A brand fills its rows (the columns, the family rows, the
+   words) and deletes the optional parts it does not use (Ask AI, newsletter, family rows, theme toggle, wordmark);
+   it never invents a footer part (a logo strip, badges, a map, a second bottom row). Something missing is a gap.
 2. Pick sections from `templates/sections/` in the order the page needs. A typical page: hero → proof (logos or
    stats) → 2 to 4 feature sections → one showcase or split → FAQ → final CTA. Not every page needs every section;
    fewer, clearer sections beat more. A page that is read rather than scanned (a blog post, docs, terms, privacy) is
@@ -74,7 +80,8 @@ Files you will use, all inside `node_modules/@gemboss/website-ui/`:
 - **Colour roles** (CSS variables, light and dark): `--gw-bg`, `--gw-bg-soft` (the neutral raised fill),
   `--gw-surface`, `--gw-ink`, `--gw-ink-2`, `--gw-muted`, `--gw-line`, `--gw-line-strong`, `--gw-action`,
   `--gw-on-action`, `--gw-accent`, `--gw-accent-strong`, `--gw-accent-soft`, `--gw-success`, `--gw-warning` (and
-  their tints `--gw-success-soft`, `--gw-warning-soft`), `--gw-night` (the dark band). Wash hues `--gw-wash-pink|violet|sky|mint` exist for the hero wash and illustrations only.
+  their tints `--gw-success-soft`, `--gw-warning-soft`), `--gw-danger` (an error, a destructive button; `--gw-danger-soft`,
+  `--gw-on-danger`), `--gw-line-control` (a form control's border, 3:1), `--gw-night` (the dark band). Wash hues `--gw-wash-pink|violet|sky|mint` exist for the hero wash and illustrations only.
 - **Dark mode** follows the visitor's system and the theme toggle (`data-theme` on `<html>`). Use the variables and
   it works; a hard-coded colour breaks it.
 - **Accent as text** (links, the active menu item, step numbers) is `--gw-accent-strong`; the plain accent is for
@@ -85,6 +92,17 @@ Files you will use, all inside `node_modules/@gemboss/website-ui/`:
 - **A button that waits** (a form sent, an audit started) gets `aria-busy="true"` from the page's script until the
   answer comes: the kit keeps its label and width, draws the ring and ignores a second press. Nothing else: no
   `disabled`, no loading class, no spinner of your own, no "Loading…" label.
+- **Forms** (0.6.0): a field is `.gw-field` (its `<label>` above, the control, the error, the hint), the controls
+  `.gw-input`, `.gw-select`, `.gw-textarea`, `.gw-check`, `.gw-radio` (a group in `.gw-choices`), one field and its
+  button in a row `.gw-form-inline`, a short form `.gw-form`. Ask as little as you can: one field beats a form, and a
+  form keeps two or three fields (`templates/sections/form.html`). A field in error is `aria-invalid="true"` plus its
+  `.gw-field__error` in words; the page decides when, the kit draws it.
+- **Footer** (0.7.0): `templates/footer.html`. Columns are `<details class="gw-footer__fold">` with the heading in the
+  `<summary>`: rows that fold on phones, open columns from 768px, no script needed. A link that leaves the site gets the
+  ↗ (`.gw-footer__ext`); one with `target="_blank"` also `<span class="gw-visually-hidden"> (opens in a new tab)</span>`.
+  The wordmark is `aria-hidden="true"`.
+- **Ratings** (0.6.0): stars `.gw-stars` (`role="img"`, `aria-label="4.9 out of 5"`, `style="--gw-stars: 4.9"`), the
+  wall `.gw-testimonials` of `.gw-card.gw-testimonial`, the badge `.gw-rating-badge` (`templates/sections/testimonials.html`).
 - **One choice out of two to four** (Monthly / Yearly) is `.gw-segmented`, a radio group; what each option shows
   carries `data-gw-show="group:value"`. Markup: `docs/components.md`, `templates/sections/pricing.html`.
 - **Type**: Inter. Headings weight 650, tracking −0.022em; display h1/h2 weight 600, tracking −0.03em. Body 18px,
@@ -119,11 +137,19 @@ Files you will use, all inside `node_modules/@gemboss/website-ui/`:
 - Don't write "Click here", "Learn more" as the only words of a link; say where it goes.
 - Don't use the em dash (—) in visible text. Use a comma, a colon or a full stop.
 - Don't invent numbers, customer names, logos, testimonials, ratings, awards or certifications.
+- Don't show a rating or a testimonial without a link to the page it comes from, and don't reword a review, round a
+  score up or average one yourself (section 6).
+- Don't build a form of many fields where one question does; don't use the placeholder as the label; don't tick a
+  consent box for the reader or word a refusal to shame them ("No thanks, I like losing sales").
+- Don't tell an error by its colour alone: `aria-invalid="true"` and words in `.gw-field__error` that say how to fix it.
 - Don't write fake numbers on a mock-up without the caption "Illustrative data." under it, and don't reword it.
 - Don't style an article's headings, lists or code in site CSS; wrap the article in `.gw-prose`.
 - Don't make a callout whose kind only its colour tells: `.gw-callout` starts with its `.gw-callout__label` in words.
 - Don't type separators (›, /, >) between breadcrumbs, and don't build a contents list whose links point at ids the
   page does not have: build it from the article's own h2s.
+- Don't add a footer part the template does not have, and don't build footer columns that fold with your own script:
+  fill `templates/footer.html` (its family rows take another brand's siblings: GemBoss, GemX, GemUpsells on a
+  GemPages site). Don't put the assistants' logos in the Ask AI row.
 - Don't animate layout properties (width, height, top, margin), and don't autoplay motion that cannot be stopped.
 - Don't ship a page you have not seen at 320px.
 - Don't write CSS that overrides a `.gw-*` class to change how it looks. If the kit's version is wrong for you,
@@ -144,6 +170,13 @@ Files you will use, all inside `node_modules/@gemboss/website-ui/`:
   (a `.gw-note` or a `role="status"` line). Under `prefers-reduced-motion` the kit's ring stands still.
 - A single choice is a radio group (`.gw-segmented`): one Tab stop, the arrows move and choose. Never a row of
   `aria-pressed` buttons for it.
+- A form field has a visible `<label for>` above it; its error and hint sit under it and are named by
+  `aria-describedby` (the error first). An error is `aria-invalid="true"` on the control plus words that say how to
+  fix it ("Enter your work email, like name@example.com"); after a failed send, move the focus to the first field in
+  error. Mark the optional fields "(optional)". A group of checkboxes or radios is a `<fieldset class="gw-choices">`
+  with its question in the `<legend>`.
+- Stars are `role="img"` with the value in words (`aria-label="4.9 out of 5"`); a number shown beside them is
+  `aria-hidden="true"`.
 - A wide table gets a scroll box a keyboard can reach: the `.gw-table` wrapper, or, for a bare table in `.gw-prose`,
   the box `website.js` adds. Give the table a `<caption>`: it names the box.
 
@@ -159,6 +192,11 @@ Files you will use, all inside `node_modules/@gemboss/website-ui/`:
 - Made-up numbers in a drawn mock-up: `.gw-window__caption` says exactly "Illustrative data." (vi: "Dữ liệu minh
   hoạ.", zh: "示意数据。"), plus one sentence only when a demo brand needs naming ("Vital Glow is a GemBoss demo
   brand."). Real numbers in a window: the caption names their source.
+- **Ratings and testimonials**: every one links to the page it comes from (the store's review page, the review
+  itself), and says only what that page says: the score and the count as shown there on the day you copy them, the
+  reviewer's own words (cut with an ellipsis, never reworded), their name and store as they wrote them. No made-up
+  review, no quote you wrote for a customer, no score you averaged yourself, no rating without its link (`check`
+  warns: `rating-source`). Do not name internal tools as the source.
 - Image sources: record where each image comes from (the brand's own screen, a licensed photo). No photos of real
   people or other brands' logos without permission.
 - Other languages: rewrite each page for its reader (transcreation), do not translate sentence by sentence. Facts
@@ -223,7 +261,9 @@ uppercase labels, em dashes in visible text, images without `alt`, overrides of
 a waiting button not marked with `aria-busy`, a segmented control without its radio-group markup, a drawn mock-up
 with numbers and no caption, an unknown brand profile or one set off `<html>`, `.gw-header--float` off the header,
 words on the accent button below 4.5:1, breadcrumbs without their markup, a contents link to an id that is not on
-the page, a callout without its label, and patterns that repeat across pages (likely gaps). It does not replace looking at the page at 320px and 1366px.
+the page, a callout without its label, stars without their value in words, a rating or a testimonial without a link to
+its source, a footer fold without its heading in the summary or a wordmark a screen reader reads, and patterns that
+repeat across pages (likely gaps). It does not replace looking at the page at 320px and 1366px.
 
 ## 11. Upgrading the kit
 

package/CHANGELOG.md

@@ -4,6 +4,122 @@ Every release lists what changed for a site that uses the kit. A release that ad
 says so with `Closes gap #N` (the GitHub issue number), so `npx gemboss-website upgrade` can tell that site which
 stopgap (`kitgap-*`) it can now delete.
 
+## 0.7.0 (2026-10-25)
+
+The footer as gemboss.ai has it today (gap #71): the kit's footer, built on 24/10 from gemboss.ai, had fallen behind
+the site's. Every new part is optional, per site, and selects only its own markup: a page with the 0.6.0 footer looks
+exactly as before. The demo index (without its new link), `brand-profiles.html`, `article.html`, `blog.html`,
+`forms.html` and `theme-example.html` are pixel-identical to 0.6.0 at 390 and 1366px, light and dark.
+
+Closes #71
+
+- Ask AI `.gw-footer__ask` (+ `__ask-label`) in the brand block: "Ask AI about [Brand]" and four links (ChatGPT,
+  Claude, Perplexity, Google AI Mode) that open the assistant with one neutral question already typed, URL-encoded
+  after `?q=` (Google: `search?udm=50&q=`), as gemboss.ai builds them. Words, not the assistants' logos. 28px rows,
+  44px on touch; the row may run wider than the brand's sentence (four names on one line at 390px).
+- Columns that fold: each `.gw-footer__col` holds a `<details class="gw-footer__fold">` whose `<summary>` is the
+  column's `<h2 class="gw-footer__heading">`. Below 768px the columns are one track of 52px rows with a chevron,
+  folded, and the browser opens and closes them (no script needed); the open list's links are 44px. From 768px they
+  are the columns as before: the summary is only its heading (`display: contents`: no box, no Tab stop) and the list
+  shows even while the `<details>` is closed (`::details-content`, in a rule of its own so an older browser drops only
+  it). `website.js` sets `open` from 768px, takes the summary out of the Tab order there and ignores a click on it,
+  gives back the markup's state below 768px (again on every change of width), and is wired like every other part
+  (`data-gw-ready="fold"`, `init` once per element, `destroy` takes it back). From 1080px the brand's track is as
+  wide as gemboss.ai draws it beside five columns (193.5px at 1120px), whatever the number of columns, and the columns
+  share the rest: three to six fit. With the fold markup only; the 0.6.0 columns keep their 1.6fr.
+  Closes gap #40 (footer accordion on phones)
+- Product family `.gw-footer__family`: a `<nav aria-label>` holding a fold whose heading is the row's label, and a
+  list of products, name and one line each (`<b>` and `<i>`, a space between). Repeat it for a second family ("More
+  from GemBoss", "From the same team, on the Shopify App Store"). Two items a line on phones (one more folded row),
+  four from 768px, and from 1080px the label in the brand's track and the items starting where the first column
+  starts. Items take the action radius (12px in `soft`) and the soft ground on hover.
+- External links: `.gw-footer__ext`, a drawn ↗ after a link that leaves the site (aria-hidden). A link with
+  `target="_blank"` also carries `<span class="gw-visually-hidden"> (opens in a new tab)</span>`; one without it does
+  not. `.gw-visually-hidden` is new in `base.css`: words a screen reader hears and the page does not show.
+- Theme toggle in the bottom row: `.gw-theme-toggle.gw-footer__toggle` with `data-gw-theme-toggle`, wired by
+  `website.js` like the header's (both relabel together). A 32px square with one hairline and the action radius, a
+  40px hit area, 44px on touch; it pushes itself and the social links to the right. Below 768px the copyright and the
+  toggle share the first line, the legal and social links the second.
+- Wordmark `.gw-footer__wordmark` (`aria-hidden="true"`): the brand's mark (an inline SVG in `currentColor`) and name,
+  ink at 10%, at `--gw-display-wordmark` (`clamp(40px, 9vw, 128px)`, new in `system.json` `type.display`), the
+  display tracking, weight 700, centred, 48px under the bottom row. A name too long for the line is cut, never a
+  sideways scroll. Not shown below 480px, as gemboss.ai hides it on phones.
+- Spacing as measured on gemboss.ai and on the kit's scale: family rows 48px apart with 32px under their hairline,
+  32px from the last family row to the bottom row (24px on phones), headings 12px above their links, 32px link rows.
+- Templates: `templates/footer.html` is now the full footer, every optional part marked (Ask AI, the 0.6.0
+  newsletter, the family row, the toggle, the wordmark), five columns; `templates/page.html` uses the folding columns.
+  Demo: `demo/footer.html`, the gemboss.ai footer with gemboss.ai's words, and a switch to the same footer for a
+  GemPages-style brand (`data-gw-radius="soft"`, `data-gw-action="accent"`, the GemPages accent of
+  `docs/theming.md`, a family row listing GemBoss, GemX and GemUpsells, the newsletter instead of Ask AI), linked
+  from `demo/index.html`.
+- `check`: `footer-markup` (an error): a `.gw-footer__fold` that is not a `<details>`, has no `<summary>`, or whose
+  summary does not hold the `.gw-footer__heading`; a `.gw-footer__wordmark` without `aria-hidden="true"`.
+- `AGENTS.md`, the skill and the docs: the footer comes from `templates/footer.html`; a brand fills its rows and
+  never invents a footer part.
+- Budget: `website.min.css` is 65.8 KB, 11.4 KB gzipped (0.6.0: 59.3 KB, 10.5 KB), most of it the three drawn icons'
+  masks. `js/website.js` is 14.5 KB unminified, 4.7 KB gzipped (0.6.0: 13.8 KB, 4.5 KB), under the test's 15 KB and
+  5 KB.
+- Tests: `test/run.mjs` holds the 0.6.0 rules of `footer.css` byte for byte and every 0.7.0 rule to a 0.7.0 part, and
+  covers the folds in its fake DOM and the new rule; `test/browser.mjs` drives `demo/footer.html` in Chromium (folded
+  at 390px, open at 1366px, Tab, Enter and Space, a click on a desktop heading, resizing both ways, without the
+  script, the wordmark out of the accessibility tree, no sideways scroll at 320 and 390px, the toggle, the
+  GemPages-style switch light and dark, and the column widths measured on gemboss.ai).
+
+## 0.6.0 (2026-10-25)
+
+Forms and ratings: the fields a contact page, a sign-up or a footer newsletter needs, with their error state, and the
+proof a product site on the Shopify App Store shows (stars, a wall of short reviews, the store's rating badge). Markup
+that worked in 0.5.0 still works, and a page without the new parts looks exactly as before: the demo index (without its
+new link), `brand-profiles.html`, `article.html`, `blog.html` and `theme-example.html` are pixel-identical to 0.5.0 at
+390 and 1366px, light and dark, with and without reduced motion.
+
+- Fields `.gw-field` (`__label`, `__error`, `__hint`): the label above, the control, the error in words after an icon,
+  then the hint, 8px apart, tied with `for`/`id` and `aria-describedby` (the error first). Controls `.gw-input`,
+  `.gw-select` (a drawn caret that follows dark mode) and `.gw-textarea`: the dashboard's field family at the
+  website's sizes, as tall as a button (40px, 44px on touch), 16px words so a phone does not zoom, the action radius of
+  the site's profile, a 1px border that reaches 3:1. States by attribute: hover, focus (the accent ring and an ink
+  border), `readonly` (the soft ground), `disabled` (faded, its reason in the hint), `aria-invalid="true"` (the danger
+  border and tint, and the message in the danger colour with its icon: never the colour alone).
+  Closes gap #28 (form fields and the error state)
+- Choices `.gw-choices` (a `<fieldset>` and its `<legend>`), `.gw-check` and `.gw-radio` (the `<label>` is the row and
+  the target: 32px, 44px on touch; chosen, the box takes the accent and the mark `--gw-on-accent`), and a filter's
+  count `.gw-check__count`, for the template gallery filters the gempages.net research found.
+- One field and its button `.gw-form-inline` (one line from 480px, each a full line below it or in a narrow box), and
+  a short form's stack `.gw-form` (fields 24px apart, actions 32px below, 560px at most; on a card too).
+- Footer newsletter: `templates/footer.html` has an optional `<form class="gw-footer__newsletter">` in the brand block
+  (label, the inline row with a secondary button, a note that says how often and how to stop and links to the privacy
+  policy). Delete it unless it is wired to a list. Existing footers are unchanged.
+- `.gw-btn--danger` (the danger fill, `--gw-on-danger` words, hover and pressed one step towards the ink) for the action
+  of a page that destroys something, and `.gw-badge--danger` (a danger dot, ink words on the danger tint), as the gap
+  asked.
+- Tokens: `--gw-danger` (`#b42318`, dark `#ff6b5a`: the dashboard's `--gemboss-danger` family; 5.92:1 or more on every
+  ground, light, dark and in night bands), `--gw-danger-soft` (`#fff0e9`, dark `#2e1714`), `--gw-on-danger` (`#ffffff`,
+  dark `#0d0d12`; 6.57:1 and 6.92:1 on the fill) and `--gw-line-control` (`#85888e`, dark `#6a6d78`): a form control's
+  border, 3.20:1 or more on `bg`, `bg-soft` and `surface` and in night bands, where `--gw-line-strong` (1.28:1) is a
+  hairline. A brand does not change them.
+- Stars `.gw-stars`: a value from 0 to 5 in `style="--gw-stars: 4.9"`, drawn as five 16px ink stars with a partial
+  last one (a mask over a hard-stop gradient; system colours on a forced-colours screen), and heard as its name:
+  `role="img"`, `aria-label="4.9 out of 5"`.
+- Testimonial wall `.gw-testimonials` (one, two from 768px, three from 1080px; no masonry, a row's cards share its
+  height) of `.gw-card.gw-testimonial` (`__quote`, `__by` with the name, the store and the link to the review,
+  `__avatar` optional), and the rating badge `.gw-rating-badge` (an `<a>` to the store's review page: `__icon`,
+  `__score` with the stars, `__count`).
+  Closes gap #56 (testimonial wall with star rating, App Store rating badge)
+- Content rule (`AGENTS.md` sections 4 to 6, `docs/components.md`): every rating and testimonial links to the page it
+  comes from and copies only what it shows; no made-up review, no reworded quote, no score averaged by hand.
+- `check`: `stars-markup` (an error: `.gw-stars` without `role="img"` or its name, a value outside 0 to 5, a name that
+  does not carry the drawn number) and `rating-source` (a warning: a `.gw-rating-badge` or a `.gw-testimonial` without
+  a link). `--gw-stars` set on the element is an input, not a redefined token.
+- No script: the page owns validation (the kit ships no validator), so `website.js` only carries the new version.
+- Templates: `templates/sections/form.html` (a short form beside its reason: two fields and a choice) and
+  `templates/sections/testimonials.html` (the badge and the wall). Demo: `demo/forms.html` (every field state, the
+  choices, the inline row, the danger button, stars from 0 to 5, a short form, the badge and the wall with sample data,
+  the footer newsletter), linked from `demo/index.html`.
+- Budget: `website.min.css` is 59.3 KB, 10.5 KB gzipped (0.5.0: 50.5 KB, 9.1 KB). `js/website.js` is unchanged in size.
+- Tests: `test/run.mjs` covers the tokens and their contrast, the new CSS and the two `check` rules; `test/browser.mjs`
+  drives `demo/forms.html` in Chromium (Tab through a form, a label click, the error in the accessibility tree,
+  44px targets and the newsletter row at 390px, the stars' names, the soft and accent profiles).
+
 ## 0.5.0 (2026-10-25)
 
 The blog release: the parts around a long article and the blog index, so a blog (gempages.net's 1,290 posts first,

package/README.md

@@ -12,11 +12,11 @@ it. Made so that a team working with Claude Code, even without a designer, ships
 
 | | |
 |---|---|
-| `website.css`, `website.min.css` | toàn bộ kit trong một tệp (khoảng 68 KB, 51 KB bản min, 9 KB khi nén gzip): token sáng và tối, chữ, bố cục, nút (cả trạng thái nhấn và đang chờ), link, nhãn, chip, segmented control, badge, card (kèm ảnh trên đầu thẻ), khung cửa sổ kèm chú thích "Illustrative data.", bảng, FAQ, chữ bài dài (`.gw-prose`), bộ khung bài blog (breadcrumb, dòng tác giả và ngày, mục lục dính, hộp lưu ý, danh sách bài, phân trang), header + mega menu + menu điện thoại, footer, 14 section, 3 hồ sơ thương hiệu |
-| `js/website.js`, `js/website.mjs` | mega menu, menu điện thoại, đổi giao diện sáng/tối, hiện dần khi cuộn, đánh dấu trang hiện tại, segmented control, chặn bấm lần hai khi nút đang chờ, đánh dấu mục đang đọc trong mục lục bài viết, khung cuộn cho bảng trong bài; không phụ thuộc thư viện nào, khoảng 4,5 KB khi nén gzip. `website.js` là script thường (tự chạy khi trang tải xong), `website.mjs` là bản ES module cho app; cả hai có `init(root)` để gắn lại phần markup chèn sau (`docs/markup-contract.md`, mục "Script") |
+| `website.css`, `website.min.css` | toàn bộ kit trong một tệp (khoảng 92 KB, 66 KB bản min, 11,4 KB khi nén gzip): token sáng và tối, chữ, bố cục, nút (cả trạng thái nhấn, đang chờ và nút xoá), link, nhãn, chip, segmented control, badge, card (kèm ảnh trên đầu thẻ), khung cửa sổ kèm chú thích "Illustrative data.", bảng, FAQ, chữ bài dài (`.gw-prose`), bộ khung bài blog (breadcrumb, dòng tác giả và ngày, mục lục dính, hộp lưu ý, danh sách bài, phân trang), ô nhập và trạng thái lỗi (ô chữ, danh sách chọn, ô nhiều dòng, checkbox, radio, hàng một ô một nút cho newsletter), sao đánh giá, tường review, huy hiệu điểm App Store, header + mega menu + menu điện thoại, footer như gemboss.ai (cột gập lại trên điện thoại, hàng Ask AI, hàng sản phẩm cùng nhà, nút sáng/tối, wordmark; ô newsletter tuỳ chọn), 16 section, 3 hồ sơ thương hiệu |
+| `js/website.js`, `js/website.mjs` | mega menu, menu điện thoại, đổi giao diện sáng/tối, hiện dần khi cuộn, đánh dấu trang hiện tại, segmented control, chặn bấm lần hai khi nút đang chờ, đánh dấu mục đang đọc trong mục lục bài viết, khung cuộn cho bảng trong bài, cột footer gập/mở theo khổ màn; không phụ thuộc thư viện nào, khoảng 4,7 KB khi nén gzip. `website.js` là script thường (tự chạy khi trang tải xong), `website.mjs` là bản ES module cho app; cả hai có `init(root)` để gắn lại phần markup chèn sau (`docs/markup-contract.md`, mục "Script") |
 | `AGENTS.md` | luật mà Claude Code (và người) phải theo: 10 luật, cách dựng trang, điều cấm, chữ, khả năng truy cập, đổi thương hiệu, khi kit thiếu |
-| `templates/` | khung một trang và 14 section (hero, logos, stats, features, split, showcase, steps, quote, pricing, faq, cta, prose, article, post-list) |
-| `demo/` | mọi thành phần trên một trang; `theme-example.html` cho thấy một thương hiệu khác đổi màu nhấn; `brand-profiles.html` là một thương hiệu kiểu GemPages bật cả 3 hồ sơ; `article.html` là một bài blog trọn vẹn, `blog.html` là trang danh sách bài |
+| `templates/` | khung một trang, header, footer (`footer.html`: footer của gemboss.ai, mọi phần tuỳ chọn đều ghi rõ) và 16 section (hero, logos, stats, features, split, showcase, steps, quote, pricing, faq, cta, prose, article, post-list, form, testimonials) |
+| `demo/` | mọi thành phần trên một trang; `theme-example.html` cho thấy một thương hiệu khác đổi màu nhấn; `brand-profiles.html` là một thương hiệu kiểu GemPages bật cả 3 hồ sơ; `article.html` là một bài blog trọn vẹn, `blog.html` là trang danh sách bài; `forms.html` là mọi trạng thái của ô nhập, newsletter ở footer, tường review và huy hiệu điểm (dữ liệu mẫu); `footer.html` là footer đầy đủ như gemboss.ai, kèm nút chuyển sang bản kiểu GemPages |
 | `docs/` | danh mục class (`components.md`), đổi thương hiệu (`theming.md`), triết lý (`philosophy.md`), hợp đồng markup |
 | `system.json` | mọi giá trị của hệ thống (màu, khoảng cách, chữ, bo góc, bóng, khung): nguồn duy nhất |
 | CLI `gemboss-website` | `init`, `check`, `gap`, `upgrade` |
@@ -40,9 +40,9 @@ nó đọc `AGENTS.md` của kit trước, dựng từ mẫu, và chạy `check`
 **Site HTML tĩnh hoặc không có bước build:** dùng CDN của npm, ghim đúng phiên bản.
 
 ```html
-<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@gemboss/website-ui@0.5.0/website.min.css">
+<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@gemboss/website-ui@0.7.0/website.min.css">
 <link rel="stylesheet" href="/site.css">   <!-- CSS riêng của site, luôn SAU kit -->
-<script src="https://cdn.jsdelivr.net/npm/@gemboss/website-ui@0.5.0/js/website.js" defer></script>
+<script src="https://cdn.jsdelivr.net/npm/@gemboss/website-ui@0.7.0/js/website.js" defer></script>
 ```
 
 Chèn markup của kit sau khi trang đã tải (block của builder, bản xem trước CMS): gọi `gwWebsite.init(phầnMới)` ngay
@@ -113,7 +113,7 @@ viết hoa vẫn cấm. Công thức và các phép kiểm tương phản: `docs
 | lệnh | làm gì |
 |---|---|
 | `npx gemboss-website init` | nối luật của kit vào Claude Code của dự án (CLAUDE.md + skill) |
-| `npx gemboss-website check` | kiểm mọi `.html` và `.css` của site: màu, khoảng cách, chữ, bo góc ngoài thang, bóng, nút tự tô màu, nhãn viết hoa giãn chữ, đè class `gw-`, đổi token của kit, hồ sơ thương hiệu sai tên hoặc sai chỗ, chữ trên nút màu nhấn dưới 4,5:1, dấu gạch dài, ảnh thiếu `alt`, link mơ hồ… và gợi ý chỗ kit có thể đang thiếu |
+| `npx gemboss-website check` | kiểm mọi `.html` và `.css` của site: màu, khoảng cách, chữ, bo góc ngoài thang, bóng, nút tự tô màu, nhãn viết hoa giãn chữ, đè class `gw-`, đổi token của kit, hồ sơ thương hiệu sai tên hoặc sai chỗ, chữ trên nút màu nhấn dưới 4,5:1, dấu gạch dài, ảnh thiếu `alt`, link mơ hồ, sao thiếu giá trị bằng chữ, điểm hay review không có link nguồn, cột footer gập thiếu tiêu đề trong summary, wordmark không ẩn với trình đọc màn hình… và gợi ý chỗ kit có thể đang thiếu |
 | `npx gemboss-website gap` | báo một chỗ kit còn thiếu: mở GitHub Issue ở repo của kit (nếu `gh` đã đăng nhập và có quyền), không thì ghi `kit-gaps/<tên>.md` để gửi |
 | `npx gemboss-website upgrade` | so bản đang dùng với bản mới nhất, in thay đổi, gap đã có trong kit, và lệnh nâng cấp |
 
@@ -141,7 +141,7 @@ gemboss-www; mọi thay đổi đi qua PR, giá trị của hệ thống chỉ s
 cd packages/website-ui
 node scripts/build.mjs        # sinh css/tokens.css từ system.json, ghép website.css và website.min.css, sinh js/website.js từ js/website.mjs
 node test/run.mjs             # tự kiểm CLI, CSS và website.js (DOM giả)
-node test/browser.mjs         # bài viết demo trong Chromium thật: cuộn, Tab, mục lục gập, bảng (cần .ci của repo)
+node test/browser.mjs         # demo trong Chromium thật: bài viết (cuộn, Tab, mục lục, bảng), form, sao, review và footer (gập, Tab, nút sáng/tối) (cần .ci của repo)
 node scripts/gate-demo.mjs    # cổng thị giác và khoảng thở của gemboss.ai trên demo (cần .ci của repo)
 ```
 

package/bin/lib/check.mjs

@@ -139,6 +139,16 @@ export const RULES = {
     why: "A screen reader announces the trail from its markup: a <nav> with a name around an <ol>, the last item marked aria-current=\"page\". The kit draws the separators; a › or / typed between the links is read out as a word.",
     fix: "Copy the markup from docs/components.md (Breadcrumbs) or templates/sections/article.html: <nav class=\"gw-breadcrumbs\" aria-label=\"Breadcrumb\"><ol><li><a href=\"/blog\">Blog</a></li><li><a href=\"…\" aria-current=\"page\">This page</a></li></ol></nav>.",
   },
+  "stars-markup": {
+    level: "error", title: "Stars without their value in words",
+    why: "The kit draws .gw-stars from style=\"--gw-stars: N\" (a number from 0 to 5), and a screen reader hears only its name: role=\"img\" and aria-label=\"N out of 5\". Without them the stars are empty or silent, and a label that names another number than the drawing says two things at once.",
+    fix: "Write <span class=\"gw-stars\" role=\"img\" aria-label=\"4.9 out of 5\" style=\"--gw-stars: 4.9\"></span>: the same number in the style and in the label, from 0 to 5 (docs/components.md, Ratings).",
+  },
+  "footer-markup": {
+    level: "error", title: "Footer fold or wordmark without its markup",
+    why: "A footer column folds on phones as a <details class=\"gw-footer__fold\"> whose <summary> holds the column's heading (<h2 class=\"gw-footer__heading\">): the summary is the row a reader taps, and a screen reader names the row by that heading. The wordmark (.gw-footer__wordmark) repeats the brand's name as decoration; without aria-hidden=\"true\" a screen reader reads the name a second time.",
+    fix: "Copy the markup from templates/footer.html: <details class=\"gw-footer__fold\"><summary><h2 class=\"gw-footer__heading\">Product</h2></summary><ul>…</ul></details>, and <div class=\"gw-footer__wordmark\" aria-hidden=\"true\">.",
+  },
   "uppercase-text": {
     level: "warning", title: "Uppercase text",
     why: "Headings, buttons, labels and menu items are sentence case.",
@@ -154,6 +164,11 @@ export const RULES = {
     why: "A note, a tip and a warning differ by their tint, which a colour-blind reader, a screen reader and a printed page do not get. The kind has to be in words.",
     fix: "Start the callout with <p class=\"gw-callout__label\">Note</p> (Tip, Warning, or the same word in the page's language).",
   },
+  "rating-source": {
+    level: "warning", title: "Rating or testimonial without a link to its source",
+    why: "A score, a review count or a quote is a claim. Linked to the page it comes from (the store's review page, the review itself), a reader can check it; without the link it reads as made up, and a made-up review makes every other claim on the page doubtful.",
+    fix: "Make the .gw-rating-badge itself the <a href> to the review page, and give every .gw-testimonial a link to its review (in the byline: <a href=\"…\">Shopify App Store</a>). If there is no source to link, do not show the rating or the quote.",
+  },
   "possible-gap": {
     level: "note", title: "Possible kit gap: a site class used on several pages",
     why: "A site class styled in site CSS and used on 3 or more pages is often a reusable part the kit does not have yet.",
@@ -305,6 +320,7 @@ export function subjectOf(sel) {
 const ATTR_THEME = String.raw`\[\s*data-theme(?:\s*[~|^$*]?=\s*(?:"[^"]*"|'[^']*'|[\w-]+))?\s*\]`;
 const ROOTISH = new RegExp(`^(?::root|html)?(?:${ATTR_THEME}|:not\\(\\s*${ATTR_THEME}\\s*\\))*$`, "i");
 const isRootish = (sel) => splitTop(sel).every((s) => s && ROOTISH.test(s));
+const INPUTS = new Set(["--gw-stars"]); // set on one element in the markup (style="--gw-stars: 4.9"), read by the kit's CSS
 const THEMABLE = /^--gw-(?:accent(?:-[\w-]+)?|on-accent(?:-(?:light|dark))?|wash(?:-[\w-]+)?)$/; // docs/theming.md: the eight accent variables (-light/-dark) + wash
 
 const COLOR_PROPS = /^(?:color|background(?:-color|-image)?|border(?:-(?:top|right|bottom|left|block|inline)(?:-(?:start|end))?)?(?:-color)?|outline(?:-color)?|fill|stroke|text-decoration(?:-color)?|caret-color|accent-color|column-rule(?:-color)?|text-emphasis(?:-color)?|-webkit-text-fill-color|-webkit-text-stroke(?:-color)?|scrollbar-color|stop-color|flood-color|lighting-color)$/;
@@ -361,6 +377,8 @@ function checkRule(rule, ctx, add) {
     const where = { file: ctx.file, line: d.line, excerpt: excerptOf(sel, d) };
     if (d.prop.startsWith("--")) {
       if (d.prop.startsWith("--gw-")) {
+        // an input a component reads from its own markup (the stars' value), not a token: stars-markup checks it
+        if (INPUTS.has(d.prop)) continue;
         if (!(THEMABLE.test(d.prop) && rootish)) add("token-redefined", where);
       } else if (!ctx.svg && colorLiterals(value).length) add("color-literal", where);
       continue;
@@ -604,6 +622,35 @@ function analyzeHtml(file, text, out) {
     if (cls.includes("gw-callout") && !/\bclass\s*=\s*["'][^"']*\bgw-callout__label\b/i.test(inner())) {
       add("callout-label", where(`${m[0].replace(/\s+/g, " ").slice(0, 80)} ${decode(visible.slice(m.index, elementEnd(scanText, m.index, tag))).replace(/\s+/g, " ").trim().slice(0, 60)}`));
     }
+    if (cls.includes("gw-stars")) {
+      const v = (/(?:^|;)\s*--gw-stars\s*:\s*([^;]*)/.exec(decode(a.style || "")) || [])[1];
+      const n = v !== undefined && /^\s*\d+(?:\.\d+)?\s*$/.test(v) ? Number(v) : null;
+      const label = a["aria-label"] || "";
+      const said = [...label.replace(/(\d),(\d)/g, "$1.$2").matchAll(/\d+(?:\.\d+)?/g)].map((x) => Number(x[0]));
+      const missing = [
+        a.role !== "img" && 'role="img"',
+        !(label.trim() || a["aria-labelledby"]) && 'aria-label with the value in words ("4.9 out of 5")',
+        v === undefined ? 'style="--gw-stars: N"' : (n === null || n > 5) && `a value from 0 to 5 (--gw-stars: ${v.trim()})`,
+        n !== null && n <= 5 && label.trim() && !said.includes(n) && `the same number in aria-label as in --gw-stars (${n})`,
+      ].filter(Boolean);
+      if (missing.length) add("stars-markup", where(`${m[0].replace(/\s+/g, " ").slice(0, 100)}  missing: ${missing.join(", ")}`));
+    }
+    if (cls.includes("gw-footer__wordmark") && (a["aria-hidden"] || "").trim() !== "true") {
+      add("footer-markup", where(`${m[0].replace(/\s+/g, " ").slice(0, 80)}  missing: aria-hidden="true" (the wordmark is decoration)`));
+    }
+    if (cls.includes("gw-footer__fold")) {
+      const sum = /<summary\b[^>]*>([\s\S]*?)<\/summary\s*>/i.exec(inner());
+      const missing = [
+        tag !== "details" && `a <details> (the class is on <${tag}>)`,
+        !sum && "a <summary> as its first child",
+        sum && !/\bclass\s*=\s*["'][^"']*\bgw-footer__heading\b/i.test(sum[1]) && "the column's heading inside the <summary> (<h2 class=\"gw-footer__heading\">)",
+      ].filter(Boolean);
+      if (missing.length) add("footer-markup", where(`${m[0].replace(/\s+/g, " ").slice(0, 80)}  missing: ${missing.join(", ")}`));
+    }
+    if (cls.includes("gw-rating-badge") || cls.includes("gw-testimonial")) {
+      const linked = (tag === "a" && "href" in a) || /<a\b[^>]*\bhref\s*=/i.test(inner());
+      if (!linked) add("rating-source", where(`${m[0].replace(/\s+/g, " ").slice(0, 80)} ${decode(visible.slice(m.index, elementEnd(scanText, m.index, tag))).replace(/\s+/g, " ").trim().slice(0, 60)}`));
+    }
     if (cls.includes("gw-window")) {
       const end = elementEnd(scanText, m.index, tag);
       const body = end < 0 ? "" : scanText.slice(m.index, end);

package/css/base.css

@@ -91,6 +91,18 @@ h5, h6 { font-size: 16px; font-weight: 600; letter-spacing: 0; }
 }
 .gw-skip:focus { left: 16px; }
 
+/* words for a screen reader only (0.7.0): " (opens in a new tab)" in a link with target="_blank" */
+.gw-visually-hidden {
+  position: absolute;
+  width: 1px;
+  height: 1px;
+  padding: 0;
+  overflow: hidden;
+  clip-path: inset(50%);
+  white-space: nowrap;
+  border: 0;
+}
+
 /* scroll reveal: the script adds .is-in; the animation is a failsafe that shows it anyway after 2.5s */
 .gw-reveal {
   opacity: 0;

package/css/components.css

@@ -43,6 +43,11 @@
 .gw-btn--secondary:active { background: var(--gw-bg-soft); border-color: var(--gw-ink); }
 .gw-btn--ghost:active { background: var(--gw-line); }
 .gw-btn--on-night:active { background: var(--gw-on-night); opacity: 0.76; }
+/* destructive (0.6.0, gap #28): delete, cancel a plan, erase my data. The danger fill with on-danger words (6.5:1 or
+   more, light and dark); hover and pressed one step stronger (towards the ink: darker in light, lighter in dark). It is
+   the action of a page that destroys something, never a second primary beside .gw-btn. */
+.gw-btn--danger { background: var(--gw-danger); color: var(--gw-on-danger); }
+.gw-btn--danger:hover, .gw-btn--danger:active { background: color-mix(in srgb, var(--gw-danger) 84%, var(--gw-ink)); }
 /* loading: aria-busy="true" on the <button>. The label stays (it keeps the width and the accessible name) but is not
    painted; a 16px ring in the button's own ink turns in its place, the dashboard's spinner. ::before, because
    .gw-btn--sm draws its hit area with ::after. website.js ignores presses on a busy button (no double submit). */
@@ -171,6 +176,9 @@
 .gw-badge--success { background: var(--gw-success-soft); color: var(--gw-ink); }
 .gw-badge--success::before, .gw-badge--warning::before { content: ""; flex: none; width: 6px; height: 6px; border-radius: var(--gw-radius-chip); background: var(--gw-success); }
 .gw-badge--warning::before { background: var(--gw-warning); }
+/* an error (0.6.0, gap #28): the danger dot, ink words on the danger tint, as success's */
+.gw-badge--danger { background: var(--gw-danger-soft); color: var(--gw-ink); }
+.gw-badge--danger::before { content: ""; flex: none; width: 6px; height: 6px; border-radius: var(--gw-radius-chip); background: var(--gw-danger); }
 
 /* cards sit: white, 1px hairline, the card radius of the site's profile (12, 20 in soft), the dashboard's resting
    shadow (Chris 24/10/2026: one language with the app); no hover lift. A soft card is a tint and carries no shadow. */

package/css/footer.css

@@ -14,6 +14,9 @@
 .gw-footer__brand { grid-column: 1 / -1; max-width: 320px; }
 .gw-footer__brand p { margin-top: 16px; color: var(--gw-muted); }
 .gw-footer__heading { margin: 0 0 8px; color: var(--gw-ink); font-size: 13px; font-weight: 600; letter-spacing: 0; }
+/* an optional newsletter form in the brand block (0.6.0): label, the inline row (field and button), a note on what the
+   reader agrees to; only when the form is wired to a list that keeps the address */
+.gw-footer__newsletter { margin-top: 24px; }
 .gw-footer__col ul { margin: 0; padding: 0; list-style: none; }
 .gw-footer__col a { display: block; padding-block: 6px; color: var(--gw-muted); }
 .gw-footer__col a:hover { color: var(--gw-ink); }
@@ -51,3 +54,181 @@
 @media (max-width: 768px), (pointer: coarse) {
   .gw-footer__bottom a { min-height: var(--gw-tap-min); }
 }
+
+/* ---- 0.7.0: the footer as gemboss.ai has it (issue #71) ---------------------------------------------------------------
+   Every part below is optional, per site, and styles only its own markup: a 0.6.0 footer looks exactly as before.
+   In page order: the Ask AI row in the brand block, columns that fold on phones (gap #40), product-family rows, the
+   theme toggle in the bottom row, and the wordmark at the very end. Values measured on gemboss.ai on 25/10/2026 and
+   put on the kit's scales; the full markup is templates/footer.html. */
+
+/* Ask AI: a label and links that open an assistant with one neutral question already typed (a URL-encoded ?q=), so
+   the answer comes from what the web says, not from a claim the brand wrote. Words, not logos. 28px rows, 44px on
+   touch. */
+.gw-footer__ask { margin-top: 24px; }
+/* the row may run wider than the brand's sentence (four names on one line at 390px) */
+.gw-footer__brand:has(> .gw-footer__ask) { max-width: none; }
+.gw-footer__brand:has(> .gw-footer__ask) > :not(.gw-footer__ask) { max-width: 320px; }
+.gw-footer__ask > .gw-footer__ask-label { margin: 0; color: var(--gw-muted); font-size: 13px; }
+.gw-footer__ask > ul { display: flex; flex-wrap: wrap; gap: 0 16px; margin: 4px 0 0; padding: 0; list-style: none; }
+.gw-footer__ask a { display: block; padding-block: 4px; color: var(--gw-ink); line-height: 20px; }
+.gw-footer__ask a:hover { text-decoration: underline; text-decoration-thickness: 1px; text-underline-offset: 4px; }
+
+/* the mark after a link that leaves the site (↗, drawn), aria-hidden; the words "(opens in a new tab)" are a separate
+   .gw-visually-hidden span, only when the link has target="_blank" */
+.gw-footer__ext {
+  display: inline-block;
+  width: 12px;
+  height: 12px;
+  margin-left: 4px;
+  vertical-align: -1px;
+  background: var(--gw-muted);
+  -webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 12 12'%3E%3Cpath d='M3.5 8.5l5-5M4.5 3.5h4v4' fill='none' stroke='%23000' stroke-width='1.4' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E") center / 12px no-repeat;
+  mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 12 12'%3E%3Cpath d='M3.5 8.5l5-5M4.5 3.5h4v4' fill='none' stroke='%23000' stroke-width='1.4' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E") center / 12px no-repeat;
+}
+
+/* Folds: <details class="gw-footer__fold"> inside a .gw-footer__col (or a .gw-footer__family), its <summary> holding the
+   .gw-footer__heading, then the <ul>. Below 768px each is a 52px row with a chevron, folded unless the markup says
+   `open`; the browser opens and closes it, no script needed. From 768px it is the column as before: the summary is
+   only the heading (display: contents: no box, no Tab stop), and the list shows even while the <details> is closed
+   (::details-content; website.js also sets `open` there, for browsers without it). */
+.gw-footer__fold > summary { list-style: none; }
+.gw-footer__fold > summary::-webkit-details-marker { display: none; }
+.gw-footer__fold .gw-footer__heading { margin: 0; line-height: 20px; }
+.gw-footer__fold > ul { margin: 0; padding: 0; list-style: none; }
+.gw-footer__col > .gw-footer__fold a { line-height: 20px; }
+@media (min-width: 768px) {
+  .gw-footer__fold > summary { display: contents; }
+  .gw-footer__col > .gw-footer__fold .gw-footer__heading { margin-bottom: 12px; }
+}
+@media (min-width: 768px) {
+  .gw-footer__fold::details-content { content-visibility: visible; }
+}
+@media (max-width: 767px) {
+  .gw-footer__grid:has(> .gw-footer__col > .gw-footer__fold) { grid-template-columns: minmax(0, 1fr); row-gap: 0; }
+  .gw-footer__grid:has(> .gw-footer__col > .gw-footer__fold) > .gw-footer__brand { padding-bottom: 24px; }
+  .gw-footer__col:has(> .gw-footer__fold),
+  .gw-footer__family { border-bottom: 1px solid var(--gw-line); }
+  .gw-footer__brand + .gw-footer__col:has(> .gw-footer__fold) { border-top: 1px solid var(--gw-line); }
+  .gw-footer__fold > summary {
+    display: flex;
+    align-items: center;
+    justify-content: space-between;
+    gap: 16px;
+    min-height: var(--gw-tap-min);
+    padding-block: 16px;
+    cursor: pointer;
+  }
+  .gw-footer__fold > summary::after {
+    content: "";
+    flex: none;
+    width: 16px;
+    height: 16px;
+    background: var(--gw-muted);
+    -webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M2.5 5.5L8 11l5.5-5.5' fill='none' stroke='%23000' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E") center / 16px no-repeat;
+    mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M2.5 5.5L8 11l5.5-5.5' fill='none' stroke='%23000' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E") center / 16px no-repeat;
+    transition: transform 0.18s var(--gw-ease);
+  }
+  .gw-footer__fold[open] > summary::after { transform: rotate(180deg); }
+  .gw-footer__fold > ul { padding-bottom: 12px; }
+  .gw-footer__col > .gw-footer__fold a { display: flex; align-items: center; min-height: var(--gw-tap-min); }
+}
+/* desktop: the brand's track is as wide as gemboss.ai draws it beside five columns (1.2 parts of 6.2, after five 24px
+   gaps), whatever the number of columns, so a family row can line up with it; the columns share the rest */
+@media (min-width: 1080px) {
+  .gw-footer__grid:has(> .gw-footer__col > .gw-footer__fold) { grid-template-columns: minmax(0, calc((100% - 120px) * 6 / 31)); }
+}
+
+/* Product family: a labelled row of products, name and one line each (<b> and <i>), as many rows as the brand needs
+   ("More from GemBoss", "From the same team, on the Shopify App Store"). A <nav aria-label> holding a fold whose
+   heading is the label. Two items a row on phones, four from 768px; from 1080px the label sits in the brand's track and
+   the items start where the first column starts. */
+.gw-footer__family .gw-footer__heading { color: var(--gw-muted); font-weight: 500; }
+.gw-footer__family .gw-footer__fold > ul { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 8px; }
+.gw-footer__family a {
+  display: flex;
+  flex-direction: column;
+  justify-content: center;
+  gap: 2px;
+  min-height: var(--gw-tap-min);
+  padding: 8px 12px 8px 0;
+  border-radius: var(--gw-radius-action);
+  color: var(--gw-ink);
+}
+.gw-footer__family a:hover { background: var(--gw-bg-soft); }
+.gw-footer__family b { font-size: 14px; font-weight: 600; line-height: 20px; }
+.gw-footer__family i { color: var(--gw-muted); font-size: 13px; font-style: normal; line-height: 18px; }
+@media (min-width: 768px) {
+  .gw-footer__family { margin-top: 48px; padding-top: 32px; border-top: 1px solid var(--gw-line); }
+  .gw-footer__family .gw-footer__heading { margin-bottom: 12px; }
+  .gw-footer__family .gw-footer__fold > ul { grid-template-columns: repeat(4, minmax(0, 1fr)); gap: 4px 16px; margin-left: -12px; }
+  .gw-footer__family a { min-height: 0; padding: 8px 12px; }
+  .gw-footer__family + .gw-footer__bottom { margin-top: 32px; }
+}
+@media (min-width: 1080px) {
+  .gw-footer__family { display: flow-root; }
+  .gw-footer__family .gw-footer__heading { float: left; width: calc((100% - 120px) * 6 / 31); margin: 8px 0 0; }
+  .gw-footer__family .gw-footer__fold > ul { margin-left: calc((100% - 120px) * 6 / 31 + 12px); }
+}
+
+/* The theme toggle in the bottom row (.gw-theme-toggle with data-gw-theme-toggle, wired like the header's): a 32px
+   square with one hairline, its hit area 40px, 44px on touch. It pushes itself and the social links to the right.
+   Below 768px the copyright and the toggle share the first line, legal and social links the second. */
+.gw-footer__toggle {
+  position: relative;
+  width: 32px;
+  height: 32px;
+  margin-inline: auto 16px;
+  border: 1px solid var(--gw-line-strong);
+  background: var(--gw-surface);
+}
+.gw-footer__toggle::after { content: ""; position: absolute; inset: -5px; }
+.gw-footer__toggle svg { width: 18px; height: 18px; }
+@media (max-width: 768px), (pointer: coarse) {
+  .gw-footer__toggle { width: var(--gw-tap-min); height: var(--gw-tap-min); }
+}
+@media (max-width: 767px) {
+  .gw-footer__bottom:has(> .gw-footer__toggle) { column-gap: 16px; }
+  .gw-footer__bottom:has(> .gw-footer__toggle) > :first-child { flex: 1 1 calc(100% - var(--gw-tap-min) - 16px); }
+  .gw-footer__bottom > .gw-footer__toggle { order: 1; margin: 0; }
+  .gw-footer__bottom:has(> .gw-footer__toggle) > ul { order: 2; }
+  .gw-footer__family + .gw-footer__bottom,
+  .gw-footer__grid:has(> .gw-footer__col > .gw-footer__fold) + .gw-footer__bottom { margin-top: 24px; }
+}
+
+/* The wordmark: the brand's mark and name, large and faint, the footer's last line. Decoration (aria-hidden="true"):
+   the name is already in the brand block. Its size follows the viewport (--gw-display-wordmark) and it never makes the
+   page scroll sideways: a name too long for the line is cut. The mark is drawn in currentColor (an inline SVG); an
+   <img> mark keeps its own colours, so leave it out and keep the name. Not on phones, as on gemboss.ai. 24px more room
+   under it than gemboss.ai gives: the kit's footer is a painted band (white like the page), and the breathing gate
+   wants half the letters' size between them and its edge (67px under 123px letters at 1366px). */
+.gw-footer__wordmark {
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  gap: 24px;
+  padding-block: 48px 24px;
+  color: color-mix(in srgb, var(--gw-ink) 10%, transparent);
+  font-size: var(--gw-display-wordmark);
+  font-weight: 700;
+  letter-spacing: var(--gw-display-tracking);
+  line-height: 1;
+  white-space: nowrap;
+  user-select: none;
+}
+.gw-footer__wordmark > svg,
+.gw-footer__wordmark > img { flex: none; width: auto; height: 0.9em; }
+.gw-footer__wordmark > span { min-width: 0; overflow-x: clip; }
+@media (max-width: 767px) { .gw-footer__wordmark { gap: 16px; } }
+@media (max-width: 479px) { .gw-footer__wordmark { display: none; } }
+
+@media (max-width: 768px), (pointer: coarse) {
+  .gw-footer__ask a { display: flex; align-items: center; min-height: var(--gw-tap-min); padding-block: 0; }
+}
+@media (prefers-reduced-motion: reduce) {
+  .gw-footer__fold > summary::after { transition: none; }
+}
+/* a forced-colours screen drops backgrounds: draw the chevron and the ↗ in its text colour */
+@media (forced-colors: active) {
+  .gw-footer__ext,
+  .gw-footer__fold > summary::after { forced-color-adjust: none; background: CanvasText; }
+}