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

@blamebutton/docmaker

v0.2.1

Published

A markdown document rendering tool

Downloads

12

Readme

Docmaker

github workflow npm dependencies

Docmaker is a WIP markdown documentation rendering tool.


Usage

$ docmaker <dir>

Docmaker will try to find docmaker.yaml in the current directory or above and resolve all filepaths specified in the config relative to this project directory.

Config

Via a config file called docmaker.yaml you can specify pages to render, which data to load and which layout HTML file the document should use.

Example

layout: layout.html
data:
  - data.yaml
  - dynamic_data.js
pages:
  - "_titlepage.html"
  - "_toc.md"
  - "[0-9]+*.md"
assets:
  - styles.css.liquid

Layout

Every docmaker project can specify a layout file to use when rendering the document. All pages will be rendered, joined and added into the layout file to render the final document.

Pages

You can specify globs for files to load as pages. These globs are expanded, sorted and the resulting filepaths will be loaded as files, processed and joined together into a document.

Assets

Using assets, you may specify additional assets to copy into the build dist directory in case they are needed for the final render to PDF. For example you can specify your document CSS or images needed to render the PDF.

It is also possible to use data variables in assets by giving the asset file a .liquid extension.

Data

Because every file loaded by docmaker is pre-processed using the Liquid templating engine, you can specify static (using yaml) or dynamic (using javascript) data files to load before rendering the pages. All pages will get the output from these datafiles as liquid variables for use while rending their content.