This web component library is designed to be used with any frontend framework and is based on custom webcomponents with litJS.
To get started with the DÁP Design System, follow these steps:
Install the library using your preferred package manager or load it directly from a CDN:
Package manager (npm)
npm install dap-design-system
yarn add dap-design-system
pnpm add dap-design-system
CDN
<script type="module" src="https://cdn.jsdelivr.net/npm/dap-design-system" />
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/dap-design-system/dist/light.theme.css" />
Start using the components in your application:
<dap-ds-button>My first button!</dap-ds-button>
<dap-ds-button>My first button!</dap-ds-button>
That's it! You're now ready to start building beautiful web applications with the DÁP Design System Component Library.
Web components are a set of web platform APIs that allow you to create new custom, reusable, encapsulated HTML tags to use in web pages and web apps. Custom components and widgets build on the Web Component standards, will work across modern browsers, and can be used with any JavaScript library or framework that works with HTML.
Custom elements in HTML are a way to define your own elements along with their behavior. You can use custom elements to create reusable components that can be used in web pages and web apps. Read more about web components here.
Web components are supported by all modern browsers, including Chrome, Firefox, Safari, and Edge. For more information on browser support, see Can I Use.
The DÁP Design System Component Library is built using the following technologies and libraries:
- Components are built with litJS
- Component metadata is generated by the Custom Elements Manifest Analyzer
- Icons are from the Remix icons library
- Positioning of dropdowns, tooltips is handled by Floating UI
- CDN hosting is provided by jsDelivr
- Development and production tooling is provided by Vite
- Storybook is used for component development and documentation
- Sass CSS preprocessor is used for styling
- Versioning is handled by Semantic Release and Conventional Commits
- No styling framework is used, all styles are custom