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

markade

v1.0.1

Published

Yaml + Markdown + Pug Static Site Generator

Downloads

8

Readme

A static site generator using Pug, Markdown and YAML

Installation

  npm install -g markade

Usage

  markade -h
    init [directory]                Initialize a markade directory
    compile [directory]             Compiles a markade directory
    watch [options] [directory]     Watches for changes and sets up a dev server

Init

  1. (Optional) Make a new directory.
  2. To initialize, run markade init <directory>. This will create a markade.json file and copy over the sample templates and data.
  3. You can edit the markade.json file as you wish, such as the paths for outut, template or data.

Compile

  1. (Optional) Move into your directory.
  2. To compile, run markade compile <directory>. This will look for markade.json you created earlier then look for data files in the data directory you specified and compare them against the templates in the following way:
  3. A YAML variable template: file.jade specified.
  4. Templates defined in your markade.json in a templates object. "templates": {"file.jade": "file.md"}
  5. If none found, it defaults to a file with the same name in the template directory.
  6. Then it will write the file in the same relative path as your data file in your output directory in the following way:
  7. A YAML variable output: file.xml specified.
  8. The same name and relative path as your data file: data/about/index.md -> public/about/index.html.

Watch and Server

  1. To watch for changes and run a server, run markade watch <directory>

License

MIT © Ilias Ismanalijev