Preview visual review matrix — 2026-08-21
Preview visual review matrix — 2026-08-21
This records an AI-assisted visual and browser-layout review of the live Material and Monospace demos. It supplements Rufus's earlier fidelity review; it is not approval to promote or release either theme.
Matrix
Each theme was rendered across all 20 combinations below (40 renders total):
| Dimension | Values |
|---|---|
| Viewport | desktop (1280 × 900), mobile (390 × 844) |
| Mode | light, dark |
| Surface | home/navbar/sidebar, kitchen sink, blog list, blog post, landing |
For every combination, a headless Chrome audit confirmed that the requested mode was active and the document width equalled the viewport width. Full-page captures were then inspected for layout, typography, contrast, component styling, wrapping, and responsive behavior. The local kitchen-sink image was scrolled into view and confirmed loaded in both themes.
Live artifacts:
Findings resolved during the review
- code.storage's non-wrapping ASCII pricing tables expanded the mobile document beyond its 390 px viewport. Intrinsic-width guards and contained horizontal scrolling now keep every route at the viewport width.
- Material's footer used a foreground shade that reversed in dark mode, producing a pale footer behind low-contrast white text. It now uses a stable dark Material surface in both modes.
- The kitchen-sink image depended on an external random-image service and
rendered as a blank review surface. It now uses the repository-owned
_demo-content/assets/demo-image.svgfixture.
Owned landing fixture review
After the published landing fixtures were rewritten with Flowershow-owned copy and visuals, a focused addendum rendered both changed pages at desktop and mobile sizes in light and dark modes: eight renders total.
| Theme specimen | Viewport | Mode | Result |
|---|---|---|---|
| Material-inspired | 1280 × 900 | light | pass |
| Material-inspired | 1280 × 900 | dark | pass |
| Material-inspired | 390 × 844 | light | pass |
| Material-inspired | 390 × 844 | dark | pass |
| Monospace | 1280 × 900 | light | pass |
| Monospace | 1280 × 900 | dark | pass |
| Monospace | 390 × 844 | light | pass |
| Monospace | 390 × 844 | dark | pass |
For every render, headless Chrome confirmed HTTP 200, the requested active
data-theme, a visible data-owned-fixture marker with Preview status, visible
fixture links to home, kitchen sink, and blog, and document width exactly equal
to viewport width. It also confirmed the removed upstream identities and
headlines were absent.
Full-page captures were manually inspected. The Material-inspired page retains its gradient hero, strong hierarchy, alternating dark/light sections, feature grid, spotlights, and calls to action while reading clearly as Flowershow. The monospace page retains its bracketed navigation, compact type, code, CSS-only blob/node composition, long-form sections, and ASCII matrix while reading as a theme lab rather than a service offer. Neither page could be mistaken for its upstream visual reference.
The first monospace dark-mode capture exposed a generated syntax-highlighting background that striped the configuration example. A landing-scoped override now keeps the generated code wrapper transparent and block-level. Configuration code stayed readable in the repeated desktop/mobile and light/dark runs.
Independent review then caught three structural defects: the landing calls to
action used a nonexistent /kitchen-sink route, the monospace landing CSS had
one unmatched closing brace, and the Material-inspired page used section
headings as additional h1 elements. The links now use the live
/docs/kitchen-sink route, the CSS is balanced, and each landing has one h1
with nested section headings. A repeated eight-render audit confirmed the
linked specimen responds HTTP 200 and the corrected pages retain their visual
hierarchy in both modes and viewports.
Restrained Monospace homepage correction
The first product-homepage migration made Monospace look like a generic
marketing template: display-sized headings, use-case cards, a dark benefit
band, boxed publishing steps, and an oversized call to action overrode the
theme's compact technical character. That review is superseded by the
theme-specific correction at 5ae23a2.
Monospace now owns monospace/demo-showcase.template.md. The page keeps
the real Flowershow navbar and a two-column opening, but its content is a
restrained linear document: ordinary paragraphs, lists, code, links and
hairline section rules. The H1 and section headings use visible Markdown
markers. There is no landing-owned <header> or <nav>, card grid, dark promo
section, boxed step layout, or oversized CTA.
The focused live audit covered /, /landing, /docs/kitchen-sink, /blog,
and /blog/first-post at 1280 × 900 and 390 × 844 in light and dark: 20 renders.
Headless Chrome confirmed HTTP 200, the requested active mode,
viewport-width containment, one homepage H1, a visible Preview marker, an
18px computed H1, 16px computed H2, two desktop columns, and one text-first
mobile column. Root and /landing render the same source.
Full-page captures of all homepage combinations plus representative kitchen sink and blog pages were manually inspected. The compact hierarchy, quiet CSS-authored node/orbit visual, light/dark contrast, mobile reading order and internal theme surfaces remain coherent. Flowershow's hosted “Built with” badge remains a platform overlay and appears on internal pages as well; it is not generated by the homepage.
Still unavailable or pending
- The shared demo requests search with
enableSearch: true, but these preview sites do not have the Flowershow Search feature entitlement and render no.search-button. Search therefore remains explicitly unreviewed rather than being counted as a visual pass. - This matrix does not approve final names, canonical gallery/dashboard integration, release metadata, or a release tag.
Result
Desktop/mobile and light/dark review is recorded for every currently rendered surface. Material remains Preview and Monospace is Official following Rufus's explicit 2026-08-21 promotion decision. Search is not reviewable in these demos and remains tracked in flowershow/flowershow#1370. The landing-fixture provenance actions are complete and recorded separately.