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

simple-site

v0.1.27

Published

A simple tool to generate web sites.

Downloads

27

Readme

simple-site

Build Status codecov License

A simple website generator.

Usage

Install with npm install -g simple-site.

Run with simple-site build.

Function

Simple-site recursively processes all files in the current directory and outputs them into an output directory. Depending on the file extension, different actions take place.

  • *.md apply the contents to the given template (see below).
  • *.html apply possibly existing handlebar {{...}} tags.
  • all other files copied into the output directory without any processing.

Templating

A simple .md file looks like this:

title: Hello site!
author: Joe Doe
date: 2017-03-17
template: _templates/simple.html
---
Here some *markdown* content.

the corresponding template simple.html would be:

<body>
    <h1>{{title}}</h1>
    {{date}}, {{author}}
    <br>
    {{{content}} 
</body>

{{...}} are handlebars expressions which reference the data from the .md file.

Configuration

Configuration parameters can be defined on the command line simple-site build --outputDir=dist or in a file named _config.yaml. All parameters are available in handlebar tags. The following parameters exist:

outputDir The output directory. Default: output

exclude File patterns that should excluded from processing (by default all files starting with _ or . are already excluded).

watch When present, all files are watched and processed on change, the output directory is served on port 8111.

Plugins

All .js files in _plugins are read and processed at the begin of the process.