EBRAINS UI Ecosystem
The ebrains-ui-ecosystem repository is where EBRAINS builds its web interfaces. It holds the EBRAINS Design System (tokens, styles and components) together with the applications that use it, in one Nx monorepo.
Why one repository
- One source of truth. Tokens, components and apps live side by side, so a design change reaches every app in one merge request, and an app always builds against the current design system.
- Shared tooling. Every app gets the same Tailwind configuration, linting, tests and release process without setting them up.
- Fast to start. A new app is one generator command away, with the design system already available and no packages to install.
- Faster, safer builds. Nx knows which projects depend on which: it builds the design system before the apps that need it, and caches and skips work that hasn’t changed.
Apps in their own repositories use the design system from npm instead: follow Build an App with Vite and React, or compare the setups in How to Integrate the Design System.
Learn step by step
Each tutorial builds on the previous one, using the same app.
Set up the monorepo
Configure Monorepo: clone, use the right Node version, install, and serve an app. 10 minutes.
Create an app
Build Your First Application: generate a React app with Nx, run it, test it, build it and commit it. 45 minutes.
Add the design system
Add the Design System to Your App: wire in the stylesheet, the Tailwind configuration and the components, and use your first ones. 30 minutes.
Build a real page
Build an EBRAINS Dashboard: lay out a complete Workflows dashboard with the layout primitives and components: header, hero, grid, chart, table, tabs, form and dialog. 45–60 minutes.
Working in Vue or Angular? Follow the same path, then see Build Inside the Monorepo for what changes. All three versions of the dashboard are in the repository: apps/live/sandbox (Vue), apps/live/react-sandbox and apps/live/angular-sandbox.
Look things up
- How to Integrate the Design System: which setup for which app
- Customise Your App’s Tailwind Config: content paths, extensions, safelist
- Tailwind Factory API and Tailwind Class Reference
- npm and Git command references
What’s in the repository
Libraries
Published to npm under @ebrains, and used from source inside the monorepo.
Applications
The monorepo isn’t limited to front ends: APIs, services and docs sites build, test and release with the same tooling.
Contribute
Found a problem in a component, or need one that doesn’t exist? See For contributors on the Design System page.