## 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/loqua/e5cf041a-edc7-487a-b4b8-8f4d563da4de-1789192875-8.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/loqua/e5cf041a-edc7-487a-b4b8-8f4d563da4de-1789192838731-full.webp
- Component on Kage: https://kage.design/component/loqua-cta

## Before you start
Ask what the founder or team believes about the user's product category and which next step should follow for developers or prospective collaborators. Use their authentic voice.

Create a light editorial closing section on warm ivory. Constrain the content to a readable text column around 330–390px wide. Start with an italic or serif heading, then a large relaxed paragraph in an editorial serif style with 1.7–1.9 line-height, followed by a short attribution. Add a softly tinted horizontal CTA card below (`#f3efe4`) with a bold one-line invitation, a tiny supporting line, and a black rounded arrow/button on the right. Keep the layout calm, with 80–120px spacing between the manifesto and CTA, and use a dotted or abstract accent only if it supports the brand.

Never:
- use logos, product names, copy, illustrations, or imagery from the reference
- imitate a founder voice without supplied source material
- turn the editorial note into a second hero