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

ym-styleguide

v0.1.6

Published

A quick and dirty styleguide generator based on YAML and Markdown

Downloads

4

Readme

YM Styleguide

This script will pull out anything that looks like this:

---
title: {title of styling block}
description: |    # Note the pipe character here.
    {brief description of styling block. parsed in markdown.}
elements:
    - {list of}
    - {elements used}
modifiers:
    - {list of}
    - {available modifiers}
parameters:
    - {list of}
    - {input parameters}
    - {for mixins}
returns:
    - {list of}
    - {output parameters}
    - {for mixins}
example: |     # Note the pipe character here as well.
    <div>
        {An HTML example}
    </div>
---

...and produce a single HTML styleguide document. Only the title field is required.

Elements, modifiers, parameters, and returns can all accept multilevel lists. In the generated style guide, the title of these fields will have a class of sg-field.

Examples will both render directly as well as provide a summary and details toggle to view the code source within the generated styleguide. They are wrapped in a div with a class of sg-example.

It doesn't care if you are using CSS, Sass, SCSS, Less, Stylus... it has no knowledge of such things.

You also need an outline.json in your stylesheets directory to tell it how to organize the blocks into the styleguide document. It looks like this:

{ "outline": [
    "Metrics",
    "Global Utilities", [
        "Clearfix",
        "Display Type Helpers",
        "Pull and Push Helpers",
    ],
    "Typography", [
        "Font Sizes",
        "Width Limiting",
        "Headings, Subheadings, and Header Groups",
        "Paragraphs", [
            "Leading Paragraphs"
        ]
    ]
] }

The title must be identical to the outline to match up. If you use a title in the outline that doesn't exist as a component, it will just display the title. It will warn you however if not all blocks have been used by the outline.

Then with the NPM:

var yms = require('ym-styleguide');
yms.build('/stylesheets', function(html) {
    // do something with `html`
});