Oracle — Oracle's next-generation UX language, rolled out across its Fusion Cloud Applications rather than published as a standalone product.
Oracle introduced the Redwood design language at Oracle OpenWorld in September 2019 as the successor to the ADF-based "Responsive UI" generation. It is built on Visual Builder Studio and Oracle JET components, and Oracle has stated a goal of migrating all Oracle Cloud Applications to Redwood UX.
Redwood is Oracle's own UX design organization's output, not a community-governed system — there is no public contribution model or RFC process. Oracle states its internal product teams use the same Redwood UX resources published to customers.
The identity-bearing decisions, rendered. Names and values are illustrative — refer to the system's official tokens reference for the canonical, current set.
--oj-core-spacing-4x
Base spacing unit (4× the core step)
--oj-core-border-radius-md
Default corner radius for controls/cards
--oj-typography-body-md-font-size
Default body text size
--oj-typography-heading-2xl-font-size
Large heading size
--oj-animation-duration-medium
Default UI transition duration
--oj-core-text-color-danger
Destructive/error text and icon color
Exactly what ships in oracle-redwood-design.md — plus the same token snapshot restated as CSS custom properties. Copy either, or feed the Markdown straight to an AI coding tool as styling context.
# Redwood — Design Style Reference > **Unofficial, community-authored reference.** Compiled by [designsystems.one](https://www.designsystems.one). Not affiliated with, endorsed by, or sponsored by Oracle. "Redwood" and related marks belong to their respective owners. This document describes publicly observable style attributes in original words — it contains no copied documentation, logos, icon artwork, or original token files. Always defer to the official source for canonical, current values. **System:** Redwood **Owner:** Oracle **Official documentation:** https://docs.oracle.com/en/cloud/saas/readiness/redwood-adoption/ --- ## Summary Oracle's next-generation UX language, rolled out across its Fusion Cloud Applications rather than published as a standalone product. ## Design tokens (illustrative) | Token | Value | Role | | --- | --- | --- | | `--oj-core-spacing-4x` | `1rem` | Base spacing unit (4× the core step) | | `--oj-core-border-radius-md` | `.25rem` | Default corner radius for controls/cards | | `--oj-typography-body-md-font-size` | `1rem` | Default body text size | | `--oj-typography-heading-2xl-font-size` | `2.5rem` | Large heading size | | `--oj-animation-duration-medium` | `0.2s` | Default UI transition duration | | `--oj-core-text-color-danger` | `#B3311F` | Destructive/error text and icon color | ## Origin Oracle introduced the Redwood design language at Oracle OpenWorld in September 2019 as the successor to the ADF-based "Responsive UI" generation. It is built on Visual Builder Studio and Oracle JET components, and Oracle has stated a goal of migrating all Oracle Cloud Applications to Redwood UX. ## Governance Redwood is Oracle's own UX design organization's output, not a community-governed system — there is no public contribution model or RFC process. Oracle states its internal product teams use the same Redwood UX resources published to customers. ## Known for - Hundreds of published CSS custom properties (--oj-* variables) in the Redwood theme, unusually transparent for an enterprise SaaS design language. - A unified visual language deliberately spanning wildly different product surfaces — ERP, HCM, and Supply Chain — under one component set. - Deep integration with Oracle's low-code tooling: Redwood is the default theme for every new Oracle JET and Visual Builder app. ## Underrated - The theme is a real, working open-source artifact — you can read its actual token values in the oracle/oraclejet GitHub repo rather than trusting marketing screenshots, which is rare for a proprietary enterprise design system. - Components like oj-waterfall-layout and oj-stream-list solve fairly specific enterprise data-density problems (masonry card grids, activity feeds) that most public systems don't bother documenting. ## Watch out for - Redwood's design guidance and patterns are Oracle-internal, exposed only through Oracle's own SaaS product docs — there's no authoritative pattern library outside Oracle's ecosystem the way there is with Carbon or Polaris. - It is built on Oracle JET, a comparatively niche framework outside the Oracle ecosystem — adopting Redwood's actual component set means adopting JET, not just its visual style. ## Components worth studying - **oj-waterfall-layout** — Displays a DataProvider as cards in a masonry-style grid with equal-width, variable-height columns. - **oj-stream-list** — Renders a DataProvider as an activity/timeline feed. - **oj-navigation-list** — The persistent side-navigation list component used across Redwood application shells. ## When to choose Redwood Not really adoptable outside Oracle's own SaaS suite the way an open design system is — most people encounter Redwood as the theme of an Oracle Fusion Cloud product they're implementing. Worth studying its token architecture if you want a real-world example of a hundreds-of-variables enterprise theme; not a realistic pick if you need public pattern documentation for a governance decision. ## Apply this style with an AI tool Paste this into your AI coding assistant as a direction, then iterate: > Design in the spirit of Redwood by Oracle — Oracle's next-generation UX language, rolled out across its Fusion Cloud Applications rather than published as a standalone product. Lean into what it's known for: Hundreds of published CSS custom properties (--oj-* variables) in the Redwood theme, unusually transparent for an enterprise SaaS design language. Match the intent, not the pixels; adapt it to my product rather than cloning it. ## Official references - [Redwood adoption docs](https://docs.oracle.com/en/cloud/saas/readiness/redwood-adoption/) - [Oracle JET on GitHub](https://github.com/oracle/oraclejet) - [Redwood theme CSS source](https://github.com/oracle/oraclejet/blob/master/dist/css/redwood/oj-redwood-notag.css) --- _Generated by [designsystems.one](https://www.designsystems.one/design-systems/oracle-redwood) — a catalogue of public design systems. Style facts are reported for reference and education; adapt them to your own product. Report issues or takedown requests via the site._
If you're evaluating this system
Not really adoptable outside Oracle's own SaaS suite the way an open design system is — most people encounter Redwood as the theme of an Oracle Fusion Cloud product they're implementing. Worth studying its token architecture if you want a real-world example of a hundreds-of-variables enterprise theme; not a realistic pick if you need public pattern documentation for a governance decision.
Where next