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

ftshp-michelangelo

v0.1.2

Published

This is a custom template for the kss-node living style guide forker from Michelangelo template.

Downloads

22

Readme

Ftshp Michelangelo Styleguide

npm version

Table of contents

About

This is a custom template for the KSS-node living style guide created on top of the Michelangelo template Adjusted as a template for Footshop styleguide

Get started

Go to your project directory. If you haven't installed KSS-node yet, install it locally* npm install kss --save-dev.

*Don't install KSS-node globally, it will cause problems in the long run when you have multiple projects using KSS-node.

Now, install the Michelangelo package locally.

npm install ftshp-michelangelo --save-dev

Create a kss-config file touch kss-config.json and specify the required config:

  • title
  • builder: refer to the Michelangelo template
  • source
  • destination
  • homepage
  • css
  • js

Read the KSS-node docs for more information about the config, or use the example below. Note: the source config should refer to your styles directory.

{
  "title"        : "Ftshp Michelangelo Styleguide",
  "mask"         : "*.scss",
  "placeholder"  : "[modifier]",

"//": "relative to this file.",
  "builder"      : "node_modules/ftshp-michelangelo/kss_styleguide/custom-template/",
  "source"       : "src/",
  "destination"  : "kss_styleguide/styleguide/",

"//": "relative to source.",
  "homepage"     : "../kss_styleguide/kss-homepage.md",

"//": "relative to the generated style guide.",
  "css": [],
  "js" : []
}

After setting up the config file, run kss --config kss-config.json to generate your living styleguide*. Locate your styleguide at the specified path in your config file and open it in the browser. Cowabunga!

*If you get the error command not found: kss. Fix this by adding ./node_modules/.bin to your PATH.

Usage

KSS-node and documentation syntax

KSS-node is an implementation of Knyle Style Sheets. This is a documentation syntax for css that can be used to create a living style guide. KSS-node has a few additional features such as adding a copy of the markup inline or external.

To get familiar with the documentation syntax it is highly advised to read through the annotated copy of the official KSS spec on the KSS-node repository.

Pro tip

When you're dealing with a high amount of example markup and you don't want to cause any code-bloat, seperate your example markup from your css modules. Create a directory in your kss_styleguide directory (name it anyway you want), and place the markup files in there. In your css module, link to the file for your example markup. (e.g., Markup: ../kss_styleguide/markup/components.form.html)

Michelangelo specifications

Color grid

This is a grid overview of all your project colors. Every color item consists of 4 parts (the color variable and hexadecimal are required).

  • color example
  • color name
  • color variable
  • color hexadecimal

In the example below you can see we have a heading, a description, and we list our colors. To make the colors work you must first define your hexadecimal after the dash, then optionally add a color name.

// Primary Colors
//
// The primary colors for branding.
//
// $leonardo      -  #2980b9; Leader blue
// $donatello     -  #8e44ad; Purple tech
// $raphael       -  #c0392b; Sai
// $michelangelo  -  rgb(232, 126, 4); Cowabunga
// $splinter      -  #FDE3A7
//
// Styleguide Settings.Colors

Responsive

The specific styling for the styleguide is written mobile first. Which makes it possible to test your project's styling directly on any device size.

Smooth scrolling

When clicking on a sub navigation item, the page animate scrolls to that specific item, so smooooth.

Prefixed styles

All styles written for the styleguide are prefixed with .kss-. They do not interfere with your project styles.

ITCSS architecture

The example src directory is a boilerplate for ITCSS methodology. A methodology created by Harry Roberts.

Customize

Inside the node package directory, go to kss_styleguide/custom-template/kss-assets/css/ to change the styling of this theme. Run sass --watch --sourcemap=none kss.scss:kss.css to watch for changes and compile the scss files.

You can quickly change the primary color by changing the value of the variable $cowabunga in kss-settings.scss.