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

gatsby-theme-nodeschool

v2.0.41

Published

Gatsby Theme for NodeSchool

Downloads

196

Readme

Node School Vancouver

This is our static site generator, powered by gatsby

Attendees

Want a simple pull request? Add yourself to the data/attendees/ directory. Create a new yaml file with your name, with the following content:

---
name: Name
github: <github id>
twitter: <optional twitter id>

When in doubt, look at other people in that directory

Mentors

If you want to help teach or contribute in anyway, Add yourself to the data/mentors/ directory. Create a new yaml file with your name, with the following content:

---
name: Name
github: <github id>
twitter: <optional twitter id>

We usually like mentors to have come to a session before, and read up on the https://github.com/nodeschool/organizers/wiki/Event-Mentor-Best-Practices#on-being-a-mentor section on the nodeschool wiki.

Sponsors

Any sponsors can be added to the data/sponsors/ directory. Create a new yaml file with the name of the sponsor name, with the following content:

---
name: $Name
logo: $relativePathToLogo.png
link: $URL

Template

This is heavily based off the nodeschool toronto template. It used jekyll which when I tried it wouldn't compile properly, and as a node group, figured all node was better.

Install all dependencies

npm install

Local Development

npm run dev

This should start gatsby on port 3000

Configuration

Everything for your nodeschool event should be managed in the data/ directory

data
├── mentors
├── attendees
├── photos
├── sponsors
├── config.js
  1. /data/mentors: This contains a list of your mentors. One yaml file per mentor. Icons are taken from github

  2. /data/attendees: This contains a list of any attendees that want to show themselves as part of the community.

  3. /data/photos: Your events photos.

  4. /data/sponsors: Your events sponsors.

  5. config.js: Your main configuration file, all your chapter's specific information should go here

💫 Deploy

npm run deploy:github

This will deploy your site to your gh-pages branch of the current repository