## 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/relic/11197dbe-e39c-44cc-b0a1-5cdca0c05213-1789279383-10.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/relic/11197dbe-e39c-44cc-b0a1-5cdca0c05213-1789279305759-full.webp
- Component on Kage: https://kage.design/component/relic-feature-grid-4

## Before you start
Ask what users need help learning first and how the product's documentation is organized. Create a guide hub that makes the next step obvious.

Design a documentation-support section with a two-column heading area: a bold statement on the left and explanatory copy plus a dark CTA on the right. Below, place five small white topic cards in a horizontal row that wraps on smaller screens. Each card needs a topic title, one-line description, and a small text link with an arrow. Use `#f5efe3`, `#fffdf8`, `#171714`, `#686257`, and amber `#d69a18`; use 14–18px radii, 16px gaps, 20px padding, and clear hover elevation. Keep the hierarchy lighter than the pricing section and make every card keyboard-accessible.

Never use logos, product names, copy, illustrations, or imagery from the reference.