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

sassdoc-theme-pheek

v0.5.0

Published

Sasscoc theme with heavy weighting to codeformatting that matches the atom text editor

Downloads

45

Readme

alt text

Sassdoc Pheek Theme

A stylish but agnostic SASSDoc theme with heavy focus on rendering code examples.

  • Code examples styled to match atom.io One Dark Theme
  • SASS filenames for easy reference
  • Previews for colours both in the main body of the documentation and in the sidebar navigation

TODO Still a couple of things I want to tidy up before this hits 1 dot release

  • Fix the inconsistent left alignment of annotation details
  • Use FontAwesome icons for function, variable and mixin labels on the @see and @usedby annotation blocks

Let me know if you find any other display quirks and I'll patch 'em. If you end up using the theme - thanks - and ping me a link. I'm @petehotchkiss on Twitter

alt text

Up and running...

Assuming you even know what Sassdoc is, and already have the bad-boy installed. Install the theme via npm

npm i --save sassdoc-theme-pheek

Depending on which way your skinning your configuration cat, change the theme value to pheek

Using gulp

gulp.task('sassdoc', function () {
  var options = {
    dest: 'docs',
    verbose: true,
    theme: 'pheek',
    display: {
      alias: true
    }
  };

  return gulp.src('path/to/you/sass/files/**/*.scss')
    .pipe($.sassdoc(options));
});

Using sassdoc.config file

{
  "dest": "destination/path",
  "verbose": true,
  "theme": "pheek",
  "display": {
    "alias": "true"
  },
  "groups": {
    "groupname": "display name",
  }
}

Changing display items

Logo

The theme will look automatically for a file called your_logo.svg in the assets/images folder of where your docs are built to. To change this, edit the package.json file, amending the logo property to your prefered file name.

Other stuff you should read

Note: Current SassDoc instance appears to have bug 464 which means anything documented with a @group annotation isn't correctly referenced with an #anchor point. Subsequently, should the items be referenced with a @see annotation the incorrect link is injected into the page.There is a pending pull request PR which fixes this and exposes a see.group value to the see.html.swig template file. Once this PR is authorsied this theme will automatically pick up the feature and the linking will work correctly on your next documentation generation.