> For the complete documentation index, see [llms.txt](https://docs.usefarlight.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usefarlight.com/resources/brand.md). # Brand and channels Farlight's official channels, how the name is written, and the visual system of colour tokens, typefaces, the mark, ornament, imagery and motion. ## Official channels | Channel | Address | | ------- | ------------------------------------------ | | Website | [usefarlight.com](https://usefarlight.com) | | X | [@usefarlight](https://x.com/usefarlight) | | Email | | Nothing else speaks for Farlight, whatever a domain or handle may claim. Contract addresses appear in exactly two places: these docs and the website. ## Writing the name Farlight is one word with a capital F. It is never set in all capitals in running text; only the wordmark is. ## The mark The mark is a spacecraft drawn in fine engraved lines, banking upward and to the right. It is drawn in one colour, white on a dark ground and ink on Paper, and it stays legible at 16 px.
Farlight mark
### Colour | Token | Hex | Use | | ------------ | --------- | ------------------------------------------------------------------------------ | | Void | `#05070d` | Page ground | | Deep | `#0b1020` | Section and panel ground | | Hull | `#121a2e` | Raised panels and cards | | Hairline | `#223052` | Borders, rules and grid lines | | Starlight | `#e8eef9` | Primary text | | Dust | `#9aa8c4` | Secondary text | | Faint | `#5f6d8a` | Muted labels and captions | | Beacon | `#7fd3ff` | Primary accent: actions, links, the mark, live indicators | | Beacon, deep | `#1d8fd1` | The accent on light surfaces | | Signal | `#f2b544` | Warnings and margin calls | | Verdant | `#4fd38a` | Healthy figures | | Flare | `#ff5c5c` | Liquidation and loss | | Paper | `#f4f7fc` | The light surface for documents and long reading, with Deep as its text colour | Gradients are never used as decoration. A single soft glow is permitted on the mark and on live indicators, and nowhere else. ### Typefaces * Sora for headings, labels and buttons * Instrument Sans for body copy * Geist Mono for every number, address and hash, always set tabular ### Ornament The only ornament is structural: hairline frames, crosshair ticks at panel corners, fine grid lines, orbit arcs and trajectory curves. Corners are squared or lightly rounded, never pills. ### Imagery and motion Imagery means rendered spacecraft and orbital scenes with photographic lighting, long-exposure star trails, planet limbs and terminators. Photography or clean 3D only. Motion is slow parallax star drift, instruments counting up on load and telemetry ticking. Nothing bounces and nothing flashes. ### Rules for the mark * Set it in white on a dark ground or in ink on Paper. Do not place it on any other colour. * Never recolour it beyond those two settings, and add no effect beyond the single soft glow the system allows. * Keep clear space of at least half its width on every side. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.usefarlight.com/resources/brand.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.