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

zapata

v1.1.5

Published

Extremely minimal static site generator: handlebars + markdown + frontmatter

Downloads

14

Readme

zapata

Extremely minimal static site generator: handlebars + markdown + frontmatter

Installation

npm install -g zapata

Getting started

To create yourself a simple starting point:

zapata create mysite

You write posts (articles, pages) as markdown .md files in the posts directory. A single template.html file (in Handlebars format) is used to convert each post into an HTML page.

To generate the site as plain HTML, run this from anywhere inside mysite

zapata generate

Optionally you can pass the path to your site's source directory.

This creates (or replaces) a sub-directory called generated. Everything is copied into generated (apart from the raw template.html and posts), so you can include images and .css resources and other pages required by your template.

Posts are converted to .html files at the root level.

The generated index.html file is just a redirector that switches to the latest post.

So in summary:

  • Customise the template.html file to get the look you want.
  • Write posts in the posts directory.
  • Run zapata generate to produce the generated sub-directory that is ready to be deployed.

Structure of a post

A post must start with a frontmatter section, which is a YAML object inside --- lines:

---
title: The introductory page of this site
posted: 2019-12-14
author: Octavia Optimism
---

The title and posted properties are mandatory. Posts are sorted by the posted data (most recent first).

Any other properties you define are exposed to the template as an object called data. The example demonstrates every feature of the template data model.

License

MIT