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

@latinum-network/mosaic

v1.18.0

Published

Mosaic is a design system library created for Collage Group, built with Storybook, CRA, Typescript, and Material UI as its foundation. It provides customizable, pre-built React components that can be combined to create modern and responsive user interface

Downloads

534

Readme

Mosaic - Collage Group's Design System

Mosaic is a design system library created for Collage Group, built with Storybook, CRA, Typescript, and Material UI as its foundation. It provides customizable, pre-built React components that can be combined to create modern and responsive user interfaces.

Getting Started

Clone the repository.

git clone [email protected]:LatinumNetwork/mosaic.git

Install dependencies

npm install

Run Storybook

npm run storybook

Organization

This library follows the Atomic design pattern: Atoms, Molecules, and Organisms.

Atoms: These are the smallest building blocks of the UI, such as buttons, inputs, and labels.

Molecules: These are groups of atoms bonded together to form a functional unit, such as a form element with a label, input, and validation message.

Organisms: These are groups of molecules combined to form a more complex, standalone UI section, like a header, footer, or a complete form.

Structure

This is how are components are organized.

src/
  └─ components/
      ├─ atoms/
      ├─ molecules/
      └─ organisms/

This is an example of a component inside a building block.

src/
  └─ components/
      ├─ atoms/
      |   ├─ Button/
      |   |   ├─ Button.tsx
      |   |   ├─ Button.stories.tsx
      |   |   ├─ Button.stories.mdx
      |   |   └─ index.tsx
      |   └─ ...

Naming Conventions

Component names should be PascalCase and descriptive.

Keep names relatively short, but they must be still clear.

Component names should be consistent across atoms, molecules, and organisms.

Development - Creating New Components

A new component should exist in its folder following the above-mentioned conventions. That folder should have the following:

  • A file creating the component. ex: Button.tsx. This file will house your atom, molecule, or organism.
  • A template file or multiple template files. ex: Button.stories.tsx and/or Button.stories.mdx. mdx stands for markdown. Storybook lets you use a markdown file to explain components and their uses further.

After creating a component, you will have to export it out multiple levels until you reach src/index.ts. Please be explicit and export each type and component you make. Only use export default if there is only a single item you are exporting. Here's an example of being explicit:

  • Box.tsx
export type BoxProps = MuiBoxProps;

export const Box = (props: BoxProps): React.JSX.Element => (
  <MuiBox {...props} />
);
  • Box/index.ts
export { Box } from './Box';
export type { BoxProps } from './Box';