Vivid philosophy favors lock-down over white labeling strategy, utilizing high-level design tokens to customize UI systematically rather than permuting components directly (to a balanced degree). This guideline help keep integration processes ergonomic and the UI consistent.
Follow our API planning on the Vivid project components' view
Tagged (next) release is published on every successful merge to main, so you never need to wait for a new stable version to make use of any updates.
See the open issues for a full list of proposed features (and known issues).
Contributions, issues and feature requests are welcome! Feel free to check issues page. You can also take a look at the contributing guide.
npx nx g @vonage/nx-vivid:component my-component
Will generate a new component in libs/componnts/src/lib/my-component
npm run test components will run unit tests for the components
See the ui-tests docs for how to run visual tests.
Give a ⭐️ if this project helped you!
This project is Apache 2.0 licensed.