open-index/open-npm huggingface dataset:
npm package: @lrnwebcomponents/gene-crossover
Description: Some gene animations
Author: btopro
Latest version: 2.3.1

# &lt;gene-crossover&gt;

Crossover
> genes

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing module / web component */
import '@lrnwebcomponents/gene-crossover/gene-crossover.js';
/* At top of an application */
<script type="module" src="node_modules/@lrnwebcomponents/gene-crossover/gene-crossover.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/gene-crossover/gene-crossover.js';

  import {GeneCrossover} from '@lrnwebcomponents/gene-crossover/gene-crossover.js';
</script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone git@github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Crossover (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/git-corner
Description: display a quick link with styling to a repo to help with contributions
Author: haxtheweb
Latest version: 8.0.2

# &lt;git-corner&gt;

Corner
> display a quick link with styling to a repo to help with contributions

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/git-corner/git-corner.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/git-corner/git-corner.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/git-corner/git-corner.js';
  // imperative form
  import {GitCorner} from '@lrnwebcomponents/git-corner';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/git-corner/git-corner.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/git-corner/git-corner.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Corner (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/github-preview
Description: A simple element that displays information about a github repository.
Author: haxtheweb
Latest version: 8.0.2

# &lt;github-preview&gt;

Preview
> A simple element that displays information about a github repository.

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/github-preview/github-preview.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/github-preview/github-preview.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/github-preview/github-preview.js';
  // imperative form
  import {GithubPreview} from '@lrnwebcomponents/github-preview';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/github-preview/github-preview.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/github-preview/github-preview.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Preview (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[MIT License](http://opensource.org/licenses/MIT)
npm package: @lrnwebcomponents/glossary-term
Description: Glossary element that connects to the glossary service.
Author: heyMP
Latest version: 4.1.0

# &lt;glossary-term&gt;

## UNDER DEVELOPMENT

Term
> Glossary element that connects to the glossary service.

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/glossary-term/glossary-term.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/glossary-term/glossary-term.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/glossary-term/glossary-term.js';
  // imperative form
  import {GlossaryTerm} from '@lrnwebcomponents/glossary-term';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/glossary-term/glossary-term.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/glossary-term/glossary-term.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Term (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/grade-book
Description: A headless gradebook that supports multiple backends with rubrics
Author: haxtheweb
Latest version: 8.0.2

# &lt;grade-book&gt;

Book
> A headless gradebook that supports multiple backends with rubrics

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/grade-book/grade-book.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/grade-book/grade-book.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/grade-book/grade-book.js';
  // imperative form
  import {GradeBook} from '@lrnwebcomponents/grade-book';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/grade-book/grade-book.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/grade-book/grade-book.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Book (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/grafitto-filter
Description: Start of grafitto-filter fork
Author: haxtheweb
Latest version: 8.0.2

# &lt;grafitto-filter&gt;

Filter
> Start of grafitto-filter fork

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing module / web component */
import '@lrnwebcomponents/grafitto-filter.js';
/* At top of an application */
<script type="module" src="grafitto-filter.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/grafitto-filter.js';

  import {GrafittoFilter} from '@lrnwebcomponents/grafitto-filter';
</script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone git@github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Filter (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/grid-plate
Description: a grid element with 1 to 4 columns via slots
Author: haxtheweb
Latest version: 8.0.2

# &lt;grid-plate&gt;

Plate
> a grid element with 1 to 4 columns via slots

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing module / web component */
import '@lrnwebcomponents/grid-plate/grid-plate.js';
/* At top of an application */
<script type="module" src="node_modules/@lrnwebcomponents/grid-plate/grid-plate.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/grid-plate/grid-plate.js';

  import {GridPlate} from '@lrnwebcomponents/grid-plate/grid-plate.js';
</script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone git@github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Plate (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/h-a-x
Description: Single tag to transform authoring
Author: haxtheweb
Latest version: 8.0.2

# &lt;h-a-x&gt;

A
> Single tag to transform authoring

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/h-a-x/h-a-x.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/h-a-x/h-a-x.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/h-a-x/h-a-x.js';
  // imperative form
  import {HAX} from '@lrnwebcomponents/h-a-x';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/h-a-x/h-a-x.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/h-a-x/h-a-x.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

A (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/h5p-element
Description: h5p wrapper for loading and presenting .h5p files
Author: haxtheweb
Latest version: 8.0.2

# &lt;h5p-element&gt;

5
> h5p wrapper for loading and presenting unpacked .h5p file directories

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/h5p-element/h5p-element.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/h5p-element/h5p-element.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/h5p-element/h5p-element.js';
  // imperative form
  import {H5PElement} from '@lrnwebcomponents/h5p-element';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/h5p-element/h5p-element.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/h5p-element/h5p-element.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

5 (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/hal-9000
Description: Robot assistant tag, hopefully not evil
Author: haxtheweb
Latest version: 8.0.2

# &lt;hal-9000&gt;

9000
> Robot assistant tag, hopefully not evil

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/hal-9000/hal-9000.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/hal-9000/hal-9000.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hal-9000/hal-9000.js';
  // imperative form
  import {Hal9000} from '@lrnwebcomponents/hal-9000';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/hal-9000/hal-9000.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/hal-9000/hal-9000.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

9000 (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/hax-cloud
Description: Turn any website into authorware with one tag and a computer
Author: haxtheweb
Latest version: 8.0.2

# &lt;hax-cloud&gt;

Cloud
> Turn any website into authorware with one tag and a computer

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/hax-cloud/hax-cloud.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/hax-cloud/hax-cloud.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hax-cloud/hax-cloud.js';
  // imperative form
  import {HaxCloud} from '@lrnwebcomponents/hax-cloud';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/hax-cloud/hax-cloud.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/hax-cloud/hax-cloud.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
yarn start
```

## Test

```bash
yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Cloud (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[ License](http://opensource.org/licenses/)
npm package: @lrnwebcomponents/hax-iconset
Description: HAX-specific icons
Author: haxtheweb
Latest version: 8.0.2

# &lt;hax-iconset&gt;

Iconset
> HAX-specific icons

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/hax-iconset/hax-iconset.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/hax-iconset/hax-iconset.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hax-iconset/hax-iconset.js';
  // imperative form
  import {HaxIconset} from '@lrnwebcomponents/hax-iconset';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/hax-iconset/hax-iconset.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/hax-iconset/hax-iconset.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Iconset (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/hax-logo
Description: logo element for hax, obviously as a hax capable element.
Author: haxtheweb
Latest version: 8.0.2

# &lt;hax-logo&gt;

Logo
> logo element for hax, obviously as a hax capable element.

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/hax-logo/hax-logo.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/hax-logo/hax-logo.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hax-logo/hax-logo.js';
  // imperative form
  import {HaxLogo} from '@lrnwebcomponents/hax-logo';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/hax-logo/hax-logo.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/hax-logo/hax-logo.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Logo (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/hax-text-editor
Description: rich-text-editor configured for HAX
Author: nikkimk
Latest version: 3.0.6

# &lt;hax-text-editor&gt;

Text
> rich-text-editor configured for HAX

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/hax-text-editor/hax-text-editor.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/hax-text-editor/hax-text-editor.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hax-text-editor/hax-text-editor.js';
  // imperative form
  import {HaxTextEditor} from '@lrnwebcomponents/hax-text-editor';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/hax-text-editor/hax-text-editor.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/hax-text-editor/hax-text-editor.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Text (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/haxcms-elements
Description: HAX CMS series of elements to provide a full on CMS
Author: btopro
Latest version: 8.0.0

# &lt;haxcms-elements&gt;

Elements
> HAX CMS series of elements to provide a full on CMS

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing module / web component */
import '@lrnwebcomponents/haxcms-elements/haxcms-elements.js';
/* At top of an application */
<script type="module" src="node_modules/@lrnwebcomponents/haxcms-elements/haxcms-elements.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/haxcms-elements/haxcms-elements.js';

  import {HaxcmsElements} from '@lrnwebcomponents/haxcms-elements/haxcms-elements.js';
</script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone git@github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Elements (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/haxor-slevin
Description: Tech blogger theme
Author: haxtheweb
Latest version: 8.0.2

# &lt;haxor-slevin&gt;

Slevin
> Tech blogger theme

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/haxor-slevin/haxor-slevin.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/haxor-slevin/haxor-slevin.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/haxor-slevin/haxor-slevin.js';
  // imperative form
  import {HaxorSlevin} from '@lrnwebcomponents/haxor-slevin';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/haxor-slevin/haxor-slevin.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/haxor-slevin/haxor-slevin.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Slevin (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/haxschema-builder
Description: dynamically build and visualize HAXschema
Author: haxtheweb
Latest version: 8.0.2

# &lt;haxschema-builder&gt;

Builder
> dynamically build and visualize HAXschema

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/haxschema-builder/haxschema-builder.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/haxschema-builder/haxschema-builder.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/haxschema-builder/haxschema-builder.js';
  // imperative form
  import {HaxschemaBuilder} from '@lrnwebcomponents/haxschema-builder';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/haxschema-builder/haxschema-builder.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/haxschema-builder/haxschema-builder.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Builder (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/hero-banner
Description: The evil yet always requested hero banner
Author: btopro
Latest version: 4.0.4

# &lt;hero-banner&gt;

Banner
> The evil yet always requested hero banner

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing module / web component */
import '@lrnwebcomponents/hero-banner/hero-banner.js';
/* At top of an application */
<script type="module" src="node_modules/@lrnwebcomponents/hero-banner/hero-banner.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hero-banner/hero-banner.js';

  import {HeroBanner} from '@lrnwebcomponents/hero-banner/hero-banner.js';
</script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone git@github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Banner (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)
npm package: @lrnwebcomponents/hex-picker
Description: Choose a color by hex or rgba code
Author: haxtheweb
Latest version: 8.0.2

# &lt;hex-picker&gt;

Picker
> Choose a color by hex or rgba code

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/hex-picker/hex-picker.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/hex-picker/hex-picker.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hex-picker/hex-picker.js';
  // imperative form
  import {HexPicker} from '@lrnwebcomponents/hex-picker';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/hex-picker/hex-picker.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/hex-picker/hex-picker.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone https://github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Picker (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[MIT License](http://opensource.org/licenses/MIT)
npm package: @lrnwebcomponents/hexagon-loader
Description: a simple VJS element that is for showing something is loading
Author: haxtheweb
Latest version: 8.0.2

# &lt;hexagon-loader&gt;

Loader
> 

## Usage
To use this web component in your project you can utilize one of the following styles of syntax.

```js
/* In an existing JS module / web component */
import '@lrnwebcomponents/hexagon-loader/hexagon-loader.js';
/* At top of an application with build routine */
<script type="module" src="@lrnwebcomponents/hexagon-loader/hexagon-loader.js"></script>
/* Alternatives for top of application */
<script type="module">
  import '@lrnwebcomponents/hexagon-loader/hexagon-loader.js';
  // imperative form
  import {HexagonLoader} from '@lrnwebcomponents/hexagon-loader';
  // if you don't have a build routine and need to reference directly
  import './node_modules/@lrnwebcomponents/hexagon-loader/hexagon-loader.js';
</script>
// via unpkg CDN (good for testing)
<script type="module" src="https://unpkg.com/@lrnwebcomponents/hexagon-loader/hexagon-loader.js"></script>
```

## Develop / Demo
Run `yarn start` will start a local development server, open your default browser to display it, open your finder to the correct window and start watching the `/src` directory for changes and automatically rebuilding the element and documentation site for the demo.
```bash
$ yarn start
```

## Test

```bash
$ yarn run test
```

## Build
Builds ensure that wcfactory can correctly compile your web component project to
work on the maximum number of browsers possible.
```bash
$ yarn run build
```

## Contributing

1. Fork it! `git clone git@github.com/elmsln/lrnwebcomponents.git`
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Code style

Loader (and all lrnwebcomponents) use [Prettier][prettier] to auto-format JS and JSON.  The style rules get applied when you commit a change.  If you choose to, you can [integrate your editor][prettier-ed] with Prettier to have the style rules applied on every save.

[prettier]: https://github.com/prettier/prettier/
[prettier-ed]: https://github.com/prettier/prettier/#editor-integration
[polyserve]: https://github.com/Polymer/polyserve
[web-component-tester]: https://github.com/Polymer/web-component-tester

## License
[Apache-2.0 License](http://opensource.org/licenses/Apache-2.0)