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

gitbook-plugin-tech-radar

v0.2.0

Published

Generate a (Thoughtworks) tech radar from pages in a Gitbook. Forked from https://github.com/thoughtworks/build-your-own-radar

Downloads

2

Readme

A gitbook plugin that generates an interactive radar, inspired by thoughtworks.com/radar and forked from github.com/thoughtworks/build-your-own-radar

How To Use

Add the tech-radar plugin to your book.json. By default, your tech radar will be generated at radar.html in your book.

{
    "plugins": ["tech-radar"],
    "pluginsConfig": {
        "tech-radar": {
            "title": "Tech Radar",
            "publicPath": "/",
            "radarPath": "radar.html"
        }
    }
}

The interactive radar will include links to the Gitbook pages. It can be used as the book's homepage by specifying "radarPath": "index.html", replacing the README.md of the book.

Specify publicPath if the site will be deployed under a context path (for example, if the site is deployed to http://example.io/tech-radar, set "publicPath": "/tech-radar") so that the Webpack build can generate links correctly.

Setting up your data

This plugin will examine a page's front matter to determine if it should be added as an item on the interactive radar. This example front matter will add an item to the "trial" ring:

---
tech-radar:
  name: Vault
  quadrant: Tools
  ring: trial
---

# Vault Secret Storage

NOTE: There will be an error message on the generated radar if there are less than four quadrants represented in the pages' markdown files.

Change default rings

Specify an { "name": "index", ... } format map of rings like so:

{
    "plugins": ["tech-radar"],
    "pluginsConfig": {
        "tech-radar": {
            "rings": { "first": "0", "second": "1", "third": "2", "fourth": "3" }
        }
    }
}

The ring names in page front matter must match ring names in the plugin config.