@vonage/vivid

Vivid UI

Essential UI web components for building modern web applications, bound to provide a safe, simple and intuitive interface.

Installation

To integrate Vivid components into your project, run:

npm install @vonage/vivid # or yarn add @vonage/vivid

Usage

Import components in your project via side effect imports:

import '@vonage/vivid/button';

And include in HTML:

<vwc-button label="Click me"></vwc-button>

For a full list of components and API, explore the components docs 📚.

Tokens (Prerequisite)

The Vivid components library rely on a set of design tokens (in the form of css custom properties).

Tokens should not affect the look of the application rather just provide a common set of identities (such as colors, typography, spacing etc') to be used by the components to look as intended.

As the task of loading css is not trivial, and may vary from project to project, this library does not provide any way to load the css. It is up to the author to load the css in the most appropriate manner for their project.

To include the tokens, its css files must be loaded into the project from the node_modules/@vonage/vivid/styles/tokens folder and require a vvd-root class selector to be present on a wrapping element (advisably the :root).

Tokens folder contains the following files:

• theme-light.css - Light theme

• theme-dark.css - Dark theme

Only one theme is required to be loaded.

Fonts (Prerequisite)

• node_modules/@vonage/vivid/styles/fonts/spezia.css - Loads the Spezia variable font and defines its font face values. Spezia is Vonage's branded font and is required by most Vivid components. folder also contains the font files.

Note that font files are not included within the css file, and must be copied to application assets separately (within the same parsed css folder). This is to allow the author to choose the most appropriate way to load the font files based on their project.

Core (Optional)

In Addition, this library provides a set of styles (combined with the tokens and fonts) that can be used to embody the Vivid design system into an application.

These styles are not required by vivid components directly. however, native HTML tags do.

These core styles rely on the tokens and fonts 👆 to be loaded.

To include the core styles, its css files must be loaded into the project from the node_modules/@vonage/vivid/styles/core folder and require a vvd-root class selector to be present on a wrapping element (advisably the :root. When set on the :root (html element), typeface sizes are able to descend from the root font-size, thus comply with the WCAG 1.4.4).

• theme.css - Sets theme related styles

• typography.css - Sets typography related styles

• all.css - Sets all the above styles

Note: scss users can simply forward the styles to their scss project:

@forward 'node_modules/@vonage/vivid/styles/[path to file].css';

Advanced Usage

Scoped Elements

Custom elements, by browsers limitations, are registered globally, and thus may conflict when multiple versions of the library are used in the same application as all custom elements register under the same namespace.

This burdens micro frontend architecture and updates to outdated versions of the Vivid, enforcing a single version of the library to be used. Meaning, any update to the library will require a full application update.

To avoid this bottleneck, Vivid provides a way for authors' to scope each custom element namespace by setting a prefix query parameter to their import call.

The following example will register badge custom element as dashboard-badge:

import '/node_modules/@vonage/vivid/badge/index.js?prefix=dashboard';

then use it as:

<dashboard-badge text="I'm a custom prefixed badge"></dashboard-badge>

Even though the custom elements are registered under different namespaces, npm packages version range handling can still be used for multiple versions saving.

Support

This library is open source, developed and maintained by the Vonage Vivid team.

For any questions, please open a bug report or feature request.

Roadmap

• View components status

• What's on our plate

• See the open issues for a full list of proposed features (and known issues).

We publish a next release on every successful merge to main, so you never need to wait for a new stable version to make use of any updates.

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the versions available, see the npm page.

Authors

See also the list of contributors who participated in this project.

License

This project is licensed under the Apache 2.0 License - see the LICENSE.md file for details

Built With

• Fast - to extend element classes and compile code to native web components
• Typescript - for ergonomic and type-safe code
• Sass - for styles authoring extensibility and consistency

Quickstart

Global content delivery networks can help quickly integrate content within html pages, fetching content from an URL, skipping local builds entirely. Such practice is often used when working on POCs or reproduction environments. Tools like UNPKG, jsDeliver, Skypack etc' are bound to deliver any content registered in the npm registry.

The following snippet fully renders a Vivid button component

<!-- import spezia font -->
<link rel="stylesheet" href="https://unpkg.com/@vonage/vivid@next/styles/fonts/spezia.css">

<!-- import light theme style tokens -->
<link rel="stylesheet" href="https://unpkg.com/@vonage/vivid@next/styles/tokens/theme-light.css">

<!-- import Vivid button component -->
<script type="module" src="https://unpkg.com/@vonage/vivid@next/button/index.js"></script>

<!-- Part of the app (or a whole app) that contains vivid components -->
<div class="vvd-root">
  <vwc-button label="Click me" appearance="filled" connotation="cta"></vwc-button>
</div>