jurniti.com
Design analysis
The observability section combines an explanation with two large cards and a centered third-party-style callout. The layout communicates extensibility while keeping the main product promise prominent.
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/jurniti/cfab9c3f-60ef-4e80-9a31-cc939c39468c-1789538635-8.webp - Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/jurniti/cfab9c3f-60ef-4e80-9a31-cc939c39468c-1789538542122-full.webp - Component on Kage: https://kage.design/component/jurniti-feature-grid-7 ## Before you start Ask what monitoring, analytics, or visibility tools the user's product supports and what brand language should be used. Design an original observability section with the following structure. ### Design language - Center a short eyebrow, a 36–48px two-line heading, and a readable explanatory paragraph. - Use two wide cards side by side on desktop and stacked on mobile. Make them warm peach #fbe8df with 1px border #ecd3c8, 10px radius, and 24px padding. - Include a small tool icon, an optional pale badge, 16px title, and 13–14px description. Keep the cards visually substantial but not dense. - Add a narrower centered callout below with a light pink surface, thin border, 10px radius, and one concise statement plus a link/action. - Use subtle dividers and muted text rather than heavy shadows. ### Never - Never use logos, product names, copy, illustrations, or imagery from the reference.
kage