Onyx Overview
Onyx brings together four persistent ideas:
- Access that belongs to the user relationship
- Connectivity that stays legible across borders
- Messaging that keeps people, context, and action closer together
- Payments that move without unnecessary friction
Continuity remains the outcome: the product should feel like one system rather than disconnected utilities.
The public website is part of that same system. It should feel connected to the product instead of detached from it.
What the public site does
The website is meant to do a small number of things clearly:
- orient a new visitor
- move them into the app with confidence
- explain the product system without noise
- expose technical documentation in a clear format
Why the site and product stay close
The Onyx website stays close to the product so that:
- motion and layout can be owned precisely in code
- content can stay versioned in the repo
- editing can later flow through the Copy Studio
- public surfaces do not drift away from product truth
Current public site
The first public tranche includes:
- the homepage hero
- the cinematic narrative sequence
- this docs foundation
Later updates expand into product landing pages and deeper documentation.