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

styleguide-gen

v1.0.0

Published

This Tool reads commented .scss-Files from a specified Folder and extract the comments to html.

Downloads

3

Readme

Team Enterprise Styleguide

This Tool reads commented .scss-Files from a specified Folder and extract the comments to html.

GETTING STARTED

  1. Navigate with your Terminal into the scssComments2HTML Folder.

  2. To start copy all scss.-Files you want to use in your Styleguide in the /content-Folder

  3. type "npm run build" in your terminal.

  4. Out of all the content the Tool creates a styleguide.min.css and a webpage.min.css, placed in the /docs-Folder. A index.html is also created inside the /docs-Folder. This file contains the Living Styelguide which you can explore in your Browser.

HOW TO USE THE STYLEGUIDE

You can import the styleguide.min.css file with the link-Tag or you copy it directly into your Project and use it like a regulary .css-File.

HOW IT WORKS

  1. The Tool looks for all .scss-Files in the Folder.

  2. An Container is created for each .scss-File. Be sure that you follow the correct Format-Style to gather all informations from the file.

  3. Every article should have a "title", an "overview" and as many "sections" you want

  4. a section contains an "example" of the rendered object, an "snippet" which shows how the Code looks like. And also an optional description.

  5. To read the correct information from the Files, your Comments should look like this:

  1. Out of all the content the Tool creates a styleguide.min.css and a webpage.min.css, placed in the /docs-Folder. A index.html is also created inside the /docs-Folder. This file contains the Living Styelguide which you can explore in your Browser.

NEED CHANGES IN THE INDEX.HTML?

If you need to change something like the design of the highlight.js or something else, you need to change the template.html! Also all paths need to be relative to the index.html in /docs! Otherwise it will not work.

After you have changed something run the build command to add all changes to the index.html in /docs