Website · Fundamentals · Guides · Components · Blog
Lion is a set of highly performant, accessible and flexible Web Components.!
They provide an unopinionated, white-label layer that can be extended to your own layer of components.
- High Performance: Focused on great performance in all relevant browsers with a minimal number of dependencies.
- Accessibility: Aimed at compliance with the WCAG 2.2 AA standard to create components that are accessible for everybody.
- Flexibility: Provides solutions through Web Components and JavaScript classes which can be used, adopted and extended to fit all needs.
- Modern Code: Lion is distributes as pure es modules.
- Exposes functions/classes and Web Components: Ships a functionality in it's most appropriate form.
Note: Our demos may look a little bland but that is on purpose. They only come with functional stylings. This makes sense as the main use case is to extend those components and if you do you do not want to override existing stylings.
npm i @lion/ui
This is the main use case for lion. To import component classes, and extend them for your own design system's components.
import { css } from 'lit';
import { LionInput } from '@lion/ui/input.js';
class MyInput extends LionInput {
static get styles() {
return [
super.styles,
css`
/* your styles here */
`,
];
}
}
customElements.define('my-input', MyInput);
There's a couple of "systems" in lion which have a JavaScript API. Examples are localize
, overlays
, ajax
, etc.
<script type="module">
import { ajax } from '@lion/ui/ajax.js';
ajax
.fetch('data.json')
.then(response => response.json())
.then(data => {
// do something with the data
});
</script>
You can also use the lion elements directly, although this is likely not a common use case.
<script type="module">
import '@lion/ui/define/lion-input.js';
</script>
<lion-input name="firstName"></lion-input>
If you encounter an issue with any of the packages we are offering please open a new bug issue. Be sure to include a description of the expected and the current behavior - additional adding a reproduction always helps.
When you have an idea on how we could improve, please check our discussions to see if there are similar ideas or feature requests. If there are none, please start your feature request as a new discussion topic. Add the title [Feature Request] My awesome feature
and a description of what you expect from the improvement and what the use case is.
Name | version | description |
---|---|---|
@lion/ui | Set of components | |
@lion/ajax | A small wrapper around fetch | |
Singleton-manager | A singleton manager provides a way to make sure a singleton instance loaded from multiple file locations stays a singleton. Primarily useful if two major version of a package with a singleton is used. | |
Babel plugin extend docs | A plugin which rewrites imports and templates according to a configuration. This enables the reuse of existing documentation from source packages while still using your extensions code. | |
Providence analytics | Providence is the 'All Seeing Eye' that generates usage statistics by analyzing code. It measures the effectivity and popularity of your software. With just a few commands you can measure the impact for (breaking) changes, making your release process more stable and predictable. | |
Publish docs | A tool that copies and processes your documentation (in a monorepo) so it can be published/shipped with your package. | |
Remark extend | A plugin for remark to extend markdown by importing from source files. | |
Rocket preset extend lion docs | When maintaining your own extension layer of lion you most likely want to maintain a similar documentation. Copying and rewriting the markdown files works, but whenever something changes you need copy and rewrite again. To do this automatically you can use this preset for rocket. |
Lion Web Components aims to be future-proof and use well-supported proven technology. The stack we have chosen should reflect this.
- lit
- npm
- Open Web Components
- Modern Web
- Mocha
- Chai
- ESLint
- prettier
- ES modules
- Lots and lots of tests
We know from experience that making high quality, accessible UI components is hard and time consuming: it takes many iterations, a lot of development time and a lot of testing to get a generic component that works in every context, supports many edge cases and is accessible in all relevant screen readers.
Lion aims to do the heavy lifting for you. This means you only have to apply your own Design System: by delivering styles, configuring components and adding a minimal set of custom logic on top.
Check out our coding guidelines for more detailed information.
Please note: This project uses Npm Workspaces. If you want to run all demos locally you need to get at least npm 7+ and install all dependencies by executing npm install
.
Lion Web Components are only as good as its contributions. Read our contribution guide and feel free to enhance/improve Lion. We keep feature requests closed while we're not working on them.
Feel free to create a github issue for any feedback or questions you might have.