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

matchacss

v0.0.8

Published

Matcha is a minimal CSS design system and framework to try and influence the use of the Cascade in CSS and promote the use of semantic HTML.

Downloads

9

Readme

MatchaCSS

A Minimal CSS Framework

Matcha is a minimal CSS design system and framework to try and influence the use of the Cascade in CSS and promote the use of semantic HTML.

It provides a hard override of base CSS element styling (using normalize.css as a starting point), while also providing the user the ability to override any styles themselves using normal css (by only styling base elements any classes added to elements will default to highest specificity).

Matcha takes a style-first stance in a framework, while it does provide some basic utilities for layout (grid/flexbox) it mostly leaves top level layout to the user

Matcha is designed for quick prototyping and extendibility, either write your own classes to override styles or modify/add your own the design token to create your own themes. Dark modes are as simple as changing a class on the body!

Install guide

  1. via NPM / Yarn
    npm install matchacss
    yarn add matchacss

and then either link to the stylesheet in your html

<link rel="stylesheet" href="node_modules/matchacss/matcha.css" />
<link rel="stylesheet" href="node_modules/matchacss/themes/dark.css" />

or in your JS file and let your bundler do the work

// import main bundle
import 'matchacss';

// import a theme
import 'matchacss/themes/dark.css';
  1. via cdn
// base package
<link rel="stylesheet" href="https://unpkg.com/matchacss" />

// to include a specific theme include this below the base package link
<link
  rel="stylesheet"
  href="https://unpkg.com/matchacss/themes/<THEME_NAME>.css"
/>

Base useage

MatchaCSS is easy to use as all you need to do is include the package to your project (as shown above), and write semantic hmtl, MatchaCSS overrides base elements stylings with an opinionated style and normalises defaults across browsers.

if you dont like a particular styling of an element, just add a class to that element and restyle, as all our styles are done purely on base element selectors any classes added to the elements will default to heighest specificity.

CSS Custom Property Usage

Matcha makes heavy use of CSS custom properties under the hood, so themeing is really easy, create a class and override the internal custom properties in your class, add your class to the body element to add your theme the page.

here is an example of the default dark theme class.

.dark {
  --background: var(--darkerBlue);
  --textColor: var(--white);
  --headerBackground: var(--black);
  --cardBackground: var(--darkBlue);
  --btnTextColor: var(--black);
  --inputHighlight: 0 0 1px 4px var(--red), 0 0 10px 1px var(--red);
}

Redefining base values

you can also overide the default values of the custom properties with your own values inside the :root pseudo-element ,

// default values for colors
:root {
  /* Shades */
  --pureBlack: #000;
  --black: #333;
  --darkerGray: #383838;
  --darkGray: #777777;
  --gray: #bfbfbf;
  --default: #d4d4d4;
  --lightGray: #eeeeee;
  --white: #f6f6f6;
  --pureWhite: #ffffff;

  /* Colors */
  --darkGreen: #335533;
  --green: #32a65a;
  --lightGreen: #5acca6;
  --teal: #60bbbf;
  --orange: #dab820;
  --yellow: #ecec75;
  --lightYellow: #f6f6b8;
  --lightRed: #df5e36;
  --red: #e84201;
  --darkRed: #992b2b;
  --lightBlue: #87ceeb;
  --blue: #909fcc;
  --darkBlue: #323b55;
  --darkerBlue: #23293a;
}

// in your stylesheet..

:root {
  --blue: red;
}

Or your can overide the color intension

:root {
  --primary: var(--teal);
  --danger: var(--red);
  --cancel: var(--lightRed);
  --attention: var(--orange);
  --success: var(--green);
  --info: var(--blue);
}

Alternative styles with data-* attributes

elements that make use of color intensions (e.g buttons) will be able to define which color intention is used by giving the element a data-<COLOR_INTENTION> attribute, otherwise will revert to its default color.

<button data-primary>Primary</button>
<button data-Danger>Danger</button>
<button data-cancel>Cancel</button>
<button data-attention>Attention</button>
<button data-success>Success</button>
<button data-info>Info</button>

Forms are super easy!

form elements styles have been normalized, input["submit"] are styled the same as normal buttons and text inputs and textareas share similar styling by default. labels are now display block to conform with best practice of having labels above the input theyre a label for, and placeholders are given better padding and colouring. Wrap grouped elements in fieldsets for best results.

ok well...its 95% Classless...

While MatchaCSS is mostly classless, it does provide some utility classes to create some components which aren't naturally comparable to basic HTML elements (e.g cards) or to provide some basic positioning using flexbox and grid, these are usually used with div's as they have no naturally styling of their own.

NB: basic grids are not resposive as of v0.0.7 (feel free to make a pull request!)

// card components create an element with some padding child elements and a box
shadow, images will default to 100% width of the card and object-fit
<div class="card">Card Component</div>

// grid element (defaults to two column grid)
<div class="grid">Grid Component</div>

// use col-[NUMBER] to specify number of columns (max: 12)
<div class="grid col-4">
  <div>Four Column Grid Element</div>
  <div>Four Column Grid Element</div>
  <div>Four Column Grid Element</div>
  <div>Four Column Grid Element</div>
</div>

// or use auto grid to create a grid element that will naturally fill the
container with as many columns it can and will be responsive out of the box with
no media queries
<div class="auto-grid">Card Component</div>

// flex component (defaults to using space between and row as direction)
<div class="flex">Default Flex Component</div>
<div class="flex flex-around">Justify-Content: space-around</div>
<div class="flex flex-center">Justify-Content: center</div>
<div class="flex flex-even">Justify-Content: space-evently</div>
<div class="flex flex-start">Justify-Content: flex-start</div>
<div class="flex flex-end">Justify-Content: flex-end</div>
<div class="flex flex-column">flex-direction: column</div>

Check out our examples page to see some of our base stylings.

Contributing

We are open to contributors at any level, the framework is built using SASS so a basic understanding of sass is prefererable (but not neccessary!). its a bit wild west at the moment but if you have any ideas or queriers about design choices message me on twitter @phl3bas or make a issue and we can move forward from there.

cheers

Sepp Wikramaratna-Clarke (twitter: @Ph3lbas)

MatchaCSS Creator