One system.
Every RAGT digital product.
This is the shared design language for RAGT's digital products.
It exists so that every screen RAGT ships, whoever builds it, starts from the same foundations: the same tokens, the same components, the same decisions.
Why this exists
Without a shared reference, every project ends up re-solving the same choices around spacing, color or button states, slightly differently each time.
The cost is time spent re-litigating the same decisions, and small inconsistencies that quietly add up until they show.
This design system isn't here to limit creativity. It's here to give every project a solid starting point: tokens for color, type, spacing and radius, and a documented component library built from them.
The goal isn't decoration for its own sake. It's speed, consistency, and an experience people recognize as RAGT, whichever screen or team built it.
Who this is for
This document is first and foremost for RAGT's internal teams: it's the reference to check as soon as a new screen or feature is on the table, so nobody has to start from scratch each time.
It's also for partner agencies and freelance contributors briefed on a RAGT project. It gives them what they need to design and build in line with our standards from day one, without a long onboarding.
How to use this document
If a component doesn't cover your case, that isn't a reason to improvise a one-off style on your own.
Flag it to the design system team instead, so it can be added to the library and published. The system grows by addition, never by exception — that's what keeps it useful for everyone, over time.
Principles
Four simple markers guide every decision in the system.
Token detail (color, typography, layout) lives under Design language; the living components under Components.