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

miam-ds

v1.2.5

Published

Sass and Css styles for Miam Design System

Downloads

866

Readme

Miam Design System

Getting started

Install dependencies

npm install

Build css

npm run build

Try locally

npm run serve

Open http://localhost:8080 in your browser

Contributing

Design system reference files

  • Web UI kit : https://www.figma.com/file/TvdkWJGeGaMQ9a3r3kmejY
  • Brand Foundation : https://www.figma.com/file/SQk0Q72cmgFI467RhsacPy

Conventions

  1. Everything directly coming from the brand foundation document (such as colors, spacings, and general conventions) should be put in variables.scss
  2. Every css code snippet that can be duplicated from one CSS class to another should be put in mixins.scss
  3. Every style that should be generic and is not a component should be defined in styles.scss (eg: keyframes for animations)
  4. Follow hierarchy and naming as defined in the Web UI kit document: components are organized in Figma files :
    • 1 figma file = 1 scss stylesheet in /components
    • 1 component = 1 class
    • CSS class name should be prefixed with .miam-ds- and reuse the component naming as per the Web UI kit document (eg: .miam-ds-button)
  5. Be cautious with your imports : while designing a component, you can import variables and mixins files as much as you like (they won't be compiled in the minified css stylesheet), but everytime you import another component, its code will be duplicated in the minified CSS => to be avoided. If you feel like you need to import another component style, you probably need a mixin...

Using within a separate project

Install package

npm install miam-ds

Import package in your project

In styles.scss, link the minified stylesheet:

@import "~miam-ds/miam-ds.min.css";

Then, start using miam-ds colors and css classes:

<div style="background-color: var(--miam-ds-color-page-background)">
  All my pages will now have this background
</div>
  
<button class="miam-ds-button success">
  New style for all my buttons!
</button>

Override classes using variables, mixins and styles

TODO