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

plankton

v0.1.3

Published

A static blog generator for node.

Downloads

8

Readme

Plankton - a static blog generator for node

Plankton uses markdown files as source and EJS templates for layout.

Getting started

Install using NPM:

$ npm install -g plankton

Blog posts are markdown files which contain a YAML front-matter. For example:

---
title: Ipsum
author: Kishore Nallan
date: January 26, 2013
published: true
layout: post
---

This is *some* text. First para here.

Second para is _right_ here!

The YAML front-matter allows you to define the following post-level properties:

  • title - The title of the post. Note that this is NOT used to generate the URL slug. The URL slug is generated using the original name of the markdown file.
  • author - Author of the post.
  • date - The date the blog post was written.
  • published - Set this to false if you don't want to publish a post (e.g. if it's still in a draft form).

Place your markdown files in a _posts folder and your EJS template files in a _layouts folder. A EJS template itself can contain a YAML font-matter that specifies a parent template. For example:

---
layout: wrapper
---
<h1>Post page</h1>
<h2><%= post.title %></h2>
<%- post.body %>

The EJS template has access to the following template variables:

  • posts - An array of all posts parsed from the _posts directory.
  • post - The actual post. post.body contains the post text and post.title contains the title of the post. You can also access all other properties specified in the YAML front-matter as properties of the post object.
  • content - If a template file specifies another template as a layout, the referred layout file get the contents of the subview as the content variable.

Publishing the site

To publish the site, call plankton from the command-line:

$ plankton --src=./example --dest=./out

Check out the the /example folder to see a bare-bones example.

Todo

  • Pagination
  • Tags