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

a_design

v3.0.0

Published

Styles for a UI design

Downloads

3

Readme

a_design

Build Status Greenkeeper badge

Styles for a UI design

Installation

npm i a_design

Usage

This UI library is splitted in two, on one side there are class, the easiest way to use them is to import them

// root_styles_in_your_project.styl

@require 'a_design/styles'

Once compiled, you will be able to use any class (e.g: <div class="_p10, _mb20">...</div>).

On the other side, if you don't want to use the class but directly some mixins (which will reduce the size of you final css)

// any_file.styl

@import 'a_design/styles/mixins/sizing'

.a-class {
  _p(10)
  _background('grey1')
}

It will check if the padding 10 is valid (the padding list is available in a_desgign/styles/design) and import add a padding: 10px rule to the class. This ensure you don't structure your UI with too much different spaces (around 4-5 enforce a coherent structure).

Principle

There are 2 main principles :

  • Avoid using too much padding, margin, font sizes... anything that influence the UI spaces. You force yourself as a designer or frontend to use only mixins available in the design for those properties.
  • Visually differenciate the project and a_design class (or mixins) because everything starts with _