getpolyglot.io
Design analysis
A second editorial product section pairs a workflow explanation with a large files-management interface preview and a follow-up action.
Prompt preview
## Reference images Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language. - Component: https://kage-design-assets.t3.tigrisfiles.io/components/polyglot/16feff4e-ce5f-4860-8cf6-49c37e8ed17f-1790402684-5.webp - Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/polyglot/16feff4e-ce5f-4860-8cf6-49c37e8ed17f-1790402570740-full.webp - Component on Kage: https://kage.design/component/polyglot-feature-grid-3 ## Before you start Ask what the user's product is, who it serves, and what brand personality and visual identity it should use. Apply these principles to that product rather than copying the reference. Design a product workflow section with an eyebrow, a large two-line heading on the left, and supporting copy on the right. Under the text, show a wide rounded preview frame with a soft, abstract blue-violet glow behind a dark application window; the UI should communicate organized projects, files, filtering, and grouped work without copying any specific interface. Add a compact CTA below the preview aligned to the left and a quiet supporting note aligned to the right. Use #080808 page background, #1b1b1b preview surfaces, #ad8cff action color, 20–28px radii, and generous 80–120px vertical section padding. Ensure the UI frame scales fluidly on mobile. Never use logos, product names, copy, illustrations, or imagery from the reference.
kage