Start a new site
true
router:new-site, position:1
Migrate an existing site
true
router:migrate, position:2
Browse the block library
true
router:blocks, position:3
Get support
true
router:support, position:4
Why teams pick RHEA
A shared foundation means your site launches faster, stays accessible, and passes performance budgets on day one.
Performance by default
One system, every brand
Launch in weeks, not quarters
How It Works
Content Authoring
Authors create content in familiar tools like Google Docs or Microsoft Word. No special software needed. Content syncs automatically to AEM, where blocks are rendered based on simple table structures.
Each block is defined by a table in your document. The first row contains the block name, and subsequent rows contain the content. It's that simple.
For example, a CTA block might look like:
- Row 1: "CTA"
- Row 2: "Get Started"
- Row 3: "/getting-started"
The system handles the rest—styling, responsiveness, and accessibility are built in.
Block Architecture
Each block is self-contained with its own JavaScript, SCSS, and JSON model. This modular approach means:
- Easy maintenance: Update one block without affecting others
- Clear ownership: Each block has defined inputs and outputs
- Simple debugging: Issues are isolated to specific components
Blocks automatically receive design tokens as CSS custom properties, ensuring consistent styling without manual configuration.
Design Token System
The design token system follows a three-tier hierarchy:
- Common Tokens: Raw values like colors (#492728), spacing (16px), and typography (Roboto)
- Semantic Tokens: Contextual meanings like "primary-text-color" or "default-spacing" that reference common tokens
- Block Tokens: Component-specific overrides that reference semantic tokens
This hierarchy ensures that changing a brand color in one place updates it everywhere. Light and dark themes are built in—just add a data-theme="dark" attribute to any container.
Build & Deploy
Development is straightforward:
- Run "npm start" to launch the dev server with hot reload
- SCSS compiles automatically when you save
- Token changes trigger a full rebuild to keep everything in sync
For production, "npm run build:prod" optimizes everything:
- CSS is minified and autoprefixed
- Unused styles are removed
- Assets are optimized for delivery
Deploy through GitHub and Edge Delivery Services handles the rest—global CDN, automatic HTTPS, and instant cache invalidation.