Logo

Getting Started

Clear about the job this library is meant to do

The goal is not to be everything. It is to be a strong Angular-native component library with a clear boundary around where it helps most.

What this library is

A component foundation for Angular apps

  • 01 An Angular component library for building product UI from composable primitives and reusable patterns.
  • 02 A token-first styling foundation that makes theming and scoped component overrides practical.
  • 03 A growing component set designed around modern Angular and Angular CDK-powered interaction behavior.

What this library is not

Complete Design System

  • 01 Not an all-in-one CSS framework. It is meant to complement tools like Tailwind CSS or Bootstrap rather than replace them.
  • 02 Not a complete FrameUI out of the box. Teams still bring their own brand, content, and product-specific guidance.

Project status

Work in progress

The library is already useful, but it is still actively evolving. APIs, polish, and documentation will continue to improve.

Help appreciated

Feedback, bug reports, accessibility review, implementation suggestions, and contributions are all welcome.

Organized around practical building blocks

These themes capture the current direction of the project and where it is strongest today.

Angular component library

A dedicated UI component library for Angular teams, designed to support real product interfaces instead of isolated visual demos.

Inspired by shadcn

The API leans into composable primitives and familiar patterns, while still staying idiomatic to Angular.

Built for modern Angular

The foundation targets current Angular practices and is aligned with Angular 21+ era tooling, patterns, and ergonomics.

CSS variables first

Design tokens and custom properties are the primary styling contract, making theming and scoped overrides straightforward.

Highly customizable

Consumers can adapt visual language and local component behavior through overrides without reworking the whole library.

Angular CDK integration

Where interaction complexity matters, the library builds on Angular CDK for accessibility, overlays, keyboard support, and structure.

Next step

Explore the component catalog

The docs already include a growing component overview and usage examples. That is the best place to continue once you have the high-level picture.

Open components