custom-elements-manifest
api-viewer-element
Our great sponsors
| custom-elements-manifest | api-viewer-element | |
|---|---|---|
| 4 | 2 | |
| 334 | 260 | |
| 3.0% | 2.7% | |
| 1.5 | 6.5 | |
| 3 days ago | 24 days ago | |
| TypeScript | TypeScript | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
custom-elements-manifest
-
The Block Protocol
The Web Components Community Group is developing such a format to describe the types of components here: https://github.com/webcomponents/custom-elements-manifest
People have already built tools that generate wrappers based on it.
-
Reactifying Custom Elements using a Custom Elements Manifest
TL;DR: A Custom Elements Manifest is a JSON file that contains all metadata about the custom elements in your project. You can read all about it here.
-
Introducing: Custom Elements Manifest
Custom Elements Manifest is a file format that describes the custom elements in your project. This format will allow tooling and IDEs to give rich information about the custom elements in a given project. A custom-elements.json contains metadata about the custom elements in your project; their properties, methods, attributes, inheritance, slots, CSS Shadow Parts, CSS custom properties, and a modules exports. If you're interested in following the specification of the schema, or contributing to it, you can find the repository here: webcomponents/custom-elements-manifest.
api-viewer-element
-
A Retrospective of My Year as a Full Stack Developer and Indie Game Developer
Documentation generated with api-viewer web component, using my plugin to generate the manifest!
-
Introducing: Custom Elements Manifest
Using a custom-elements.json file, it would be easy to generate or display demos for your component using tools such as api-viewer-element, or automatically generate Storybook knobs for your components. 11ty plugins could be created to automatically create your documentation sites for you.
What are some alternatives?
catalyst - Catalyst is a set of patterns and techniques for developing components within a complex application.
webcomponents - Web Components specifications [Moved to: https://github.com/WICG/webcomponents]
open-wc - Open Web Components: guides, tools and libraries for developing web components.
cem-plugin-template - Starter repo for developing custom element analyzer plugins
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
HighScore - 🏆 An open-source leaderboard for indie game developers
custom-elements-manifest
eleventy 🕚⚡️ - A simpler site generator. Transforms a directory of templates (of varying types) into HTML.
custom-elements-manifest - Custom Elements Manifest is a file format that describes custom elements in your project.
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.