Typed Ruby components
Closed Phlex APIs make component vocabulary explicit and verifiable.
Product landing
A directly composed public landing page with announcement, proof, long-content, and mobile states.
Product landing page
Default, announcement, customer proof, long-content, and narrow public states.
Complete screen
A UI kit Rails applications and agents can understand
See how application teams use one component vocabulary across people, agents, and production Rails code.
- Stock components
- 40
- Typed, direct Phlex APIs
- Layout primitives
- 3
- Flex, Grid, and Container
- Required CSS classes
- 0
- Self-describing data contracts
Static, themeable CSS
Gem-owned styles use documented custom properties without runtime compilation.
Rails-native forms
Model values, errors, names, multipart behavior, and submission semantics stay intact.
Built with application teams
Teams use the same typed vocabulary across engineers, coding agents, and production Rails code.
| Organization | Outcome | Detail |
|---|---|---|
| Analytical Engines | 42% fewer interface regressions | A single typed vocabulary replaced six project-specific component wrappers. |
| Orbital Research | 18 production journeys verified | Agents compose Rails screens from the same documented components engineers review. |
| North Sea Systems | Zero runtime styling dependencies | Static CSS ships with the gem and adapts through organization theme variables. |
Viewport
Ruby
test/dummy/app/components/gallery/compositions/landing_page.rbworkspace_surface do
render_header
render_announcement if state == "announcement"
render_results
render_feature_summary
render_customer_proof if state == "customer-proof"
end