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

cti-design

v0.5.9

Published

CTI Design is a Components Library made for creating consistent, usable and accessible communication platforms in the browser.

Downloads

9

Readme

CTI Design

CTI Design is a Components Library made for creating consistent, usable and accessible communication platforms in the browser.

ANALYSIS STEPS

  • Apply the Atomic Design concepts
  • Start from Atoms
  • Analize the old UI and get screens of the elments
  • Create boards categorize elements and merge them
  • Repeat for Molecules -> Organisms -> Templates -> Pages

DESIGN STEPS

  • Create the design inside the Figma design file
  • Validate the design with the team members
  • Implement the designed component
  • The components already made can be very usefull as inspiration

REPO STRUCTURE

  • The components are in src/components each one inside a specific directory
  • Files can have .jsx or .tsx extensions for JS/React files
  • The same rules are applied to templates but they are in src/templates
  • In conclusion components, stories and tests are in the same directory
  • The other files and directories in the repository are for configuration an build steps

DEVELOPMENT STEPS

  • Start development with Storybook:
npm run storybook
  • After the analisys steps it’s time to merge elements creating components and templates
  • Components are base components and templates are more complex components
  • All components logic is implemented using React
  • The components development follows the CDD approach driven by Storybook

CREATING A COMPONENT

  • Add a new directory named Component in src/components
  • Create a Component.tsx/.jsx file for the logic with React
  • Create a Component.stories.tsx/.jsx file for Storybook stories
  • Create a Component.test.tsx/.jsx file for Unit Tests with Jest and React Testing Library
  • Do the same things in templates for a new template
  • Add examples and code snippets to the CTI Design Site

TESTING A COMPONENT

  • Test that the component renders without crash
  • Test that the component renders correctly the props

COMPONENT DOCS

  • Document how the component can be used
  • Document the properties of the component with types

BUILD & RELEASE STEPS

  • Build the library:
npm run build
  • Publish the library on npm using the np command and cli
  • Ensure that you are logged in on npm and your account is inside collaborators

To see all the npm scripts available check the package.json.