Introduction
What Oratiq is, what it isn't, and why it exists.
What is Oratiq?
Oratiq is a component distribution, not a component dependency. The CLI copies accessible, themeable components — built on Radix behaviour and Tailwind CSS v4 — into your repository. From that moment the code is yours: every line is editable, every update is an explicit, reviewable diff.
Why another one?
One reason, taken seriously: the web reads in two directions.
Roughly a billion people read right-to-left — Arabic, Hebrew, Persian, Urdu. Most component libraries treat that as a patch: a wrapper here, an override there, a broken calendar everywhere. Oratiq inverts the priority. Logical CSS properties, bidi isolation, direction-aware behaviour, and mirrored iconography are the default — you write one codebase and it reads correctly both ways.
Copy-in ownership
shadcn's distribution model: your repo, your code, no lock-in.
Radix behaviour
Focus traps, keyboard navigation, and ARIA come from battle-tested primitives.
RTL-first styling
The part nobody else does: measured zero physical direction classes.
What Oratiq is not
- Not an npm component package. You never
importUI from@oratiq-js/ui— that package is only the CLI. Components live in your repo. - Not a design straitjacket. Every colour, radius, and shadow reads a semantic token — re-branding is a CSS override, never a component edit.
- Not a fork of shadcn/ui. Same architecture family, independently written — with RTL, bidi safety, and direction-aware behaviour as first-class requirements.
Where to go next
- Installation — running in sixty seconds.
- Direction — how LTR/RTL actually works here.
- Theming — make it yours.
Built with itself