npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@carbon/ibm-products-community

v0.13.0

Published

Carbon for IBM Products Community package

Downloads

220

Readme

Carbon for IBM Products Community

About

The Community package has two primary goals in mind: to host experimental components / patterns and to enable teams to share code that may not be officially supported or documented through the design system guild.

Traditionally, components and patterns are defined by design, approved via DSAG, developed by the C4P team, and then added to the core library. The Community package represents a different approach to this system. If a product team or developer believes they have organically developed a new pattern or noticed a recurring design that hasn't been defined as an official pattern and wants to share it with the larger Carbon for IBM Products community, they can contribute it for others to leverage even as the design use cases are being defined.

One of the biggest concerns with design-driven development is that there are some limitations to the design process that are not immediately clear until it reaches the development phase. Accessibility is one of the biggest concerns in modern UI development. While design tools may allow for some accessibility checks out of the box, such as color contrast or font size, some components and patterns have far more complex accessibility concerns that a designer may not be able to take into account. Issues with focus and keyboard navigation do not become noticeable until you can interact with code in the browser. By allowing development to happen in tandem with design, these limitations are discovered far more quickly in the design cycle and can be fixed much more quickly. The Community package can act as a prototyping environment where development and design can work together simultaneously to improve these kinds of UX concerns.