
NO. 166 · 2026-10-26
The Asset Panel
A design editor's canvas as the page: a mixed asset tree, framed sections with name tabs on grape violet contours, a live inspector.
Build a SaaS feature launch page laid out as the product's own design editor: three panes, with the page's sections as frames on a canvas.
View the visual result: One Framer folder can now hold a component, a color and a curve
Read the full prompt and reusable template
Build a SaaS feature launch page laid out as the product's own design editor: three panes, with the page's sections as frames on a canvas. 1. Layout: a 52px dark toolbar (brand, centred file name, three nav links). Below it a three-column grid: a 252px sticky asset tree on the left, a canvas in the middle, a 264px sticky inspector on the right. Both side panes are full-height, dark (#1C1427), scroll on their own and use a monospace face at 13-14px. 2. Canvas: a flat saturated grape violet field (#4B2A78) with faint topographic contour lines in pale lavender at about 17 percent opacity as an SVG background. No gradients, no glow. Each section is a frame: an off-white board (#F6F2EA, 4px radius, 48px by 56px padding, max 760px wide) with a small tab above its top-left corner holding a number, the frame name and a kind word. The hero frame runs wider (960px): a full-width headline, then two columns of deck, an inline byline sentence (issue number, weekday, date, read time) and two actions beside a 3:2 illustration. 3. Asset tree: native details/summary folders, one per section, open by default. Inside each folder, rows of mixed kinds link to anchors on the page. Every row is a grid of an 18px kind glyph, a name and a small kind word (Text, Color, Component, Code, Vector, Image). Glyphs: a rotated square outline for components, a filled circle in the real color for colors, "Aa" for text styles, braces for code, a short curve for vectors. 4. Inspector: a dl for the current frame (name, source link, date, kind) plus a kinds legend. A small IntersectionObserver marks the frame in view: its board gets a 2px chartreuse (#D4EC4A) outline offset 6px, its tab turns chartreuse with ink text, its tree folder highlights and the inspector updates. 5. Type: Chivo Mono 700 for the headline, 500 for section heads, 400 for labels and UI; Piazzolla for reading at 19px, line-height 1.7, about 66 characters per line. Italic Piazzolla in deep violet (#5B3594) for emphasis and one pullquote under a 2px violet rule. 6. One inverted dark frame holds the reusable pattern with a live By job / By kind segmented control (two radio inputs, switched with :has()) that re-sorts the same seven assets. 7. Below 1280px drop the inspector; below 1024px hide the tree and show a sticky horizontal strip of section links; below 760px stack every two-column block, with the hero image between headline and deck. 8. Guardrails: body text never under 18px, line-height at least 1.6, WCAG AA contrast for every label on its actual surface, no fake search fields or dead toggles, no pill-shaped everything, no neon or glow, no purple-blue gradients, no readable text inside images, hover and focus states at 150ms with a prefers-reduced-motion guard, and a print stylesheet that hides the panes.
Design a single web page for [your topic] using the The Asset Panel art direction. Purpose: adapt this visual system to [your product, article, interface, or client brief]. Keep the layout grammar and visual lesson, but replace all story-specific references with your own content. Visual system: A design editor's canvas as the page: a mixed asset tree, framed sections with name tabs on grape violet contours, a live inspector. Starting point: Build a SaaS feature launch page laid out as the product's own design editor: three panes, with the page's sections as frames on a canvas. Palette: paper: #4B2A78, primary: #1C1427, secondary: #F6F2EA, accent: #D4EC4A, muted: #5B3594. Type: Chivo Mono + Piazzolla. Keep running text readable, with clear hierarchy between display type, body copy, labels, and source or metadata marks. Layout: preserve the original archetype's structural idea, then map it to your content. Define the hero, metadata, primary content sections, supporting image or artifact, prompt or CTA area, and source/reference area before styling individual cards. Imagery: create or choose one integral visual artifact that teaches the pattern. It should be visible near the top of the page and work in both a wide social crop and a portrait cover crop. Avoid logos, watermarks, and fake readable text inside images. Guardrails: avoid generic SaaS sections, purple-blue gradients, glass cards, fake controls, stock people, emoji decoration, pill-shaped everything, and identical feature cards. Build visible focus states, real links/buttons, responsive crop behavior, and a reduced-motion fallback.




































































































































































