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

generator-doc-metrix-doc

v0.0.0

Published

A Yeoman generator for doc-metrix metric documentation.

Downloads

4

Readme

Yeoman Generator

NPM version Build Status Dependencies

This module is a Yeoman generator for doc-metrix metric documentation.

Getting Started

To use the generator, ensure that you have installed Yeoman:

$ npm install -g yo

For a general overview of Yeoman generators, see the Getting Started Guide.

Installation

$ npm install -g generator-doc-metrix-doc

Usage

Once installed, navigate to the directory in which you want to place generated files and run

$ yo doc-metrix-doc

The generator will provide a series of prompts and will use your answers to tailor the documentation files, providing a scaffold upon which you can immediately build.

Prompts

The prompts are as follows...

Name

Enter the documentation name. The default documentation name is the name of the current working directory. To accept the default, type enter.

Naming convention:

  • The documentation name should be descriptive of the documentation.

For example, documentation for cpu related metrics should be named cpu. Similarly, documentation for memory related metrics should be named memory or shortened to mem. Other examples might include network, sensors-power, sensors-temperature, sensors-{{ classification }}, etc.

Git

You have the option to initialize the documentation directory as a Git repository. The default option is Y. Typing enter or y+enter will confirm initialization and do the following:

$ git init
$ git remote add origin https://github.com/doc-metrix/<repo_name>.git
$ git add -A
$ git commit -m "[INIT]"

The initialization process stops short of pushing the commit to the remote repository.

Note: Git initialization assumes you have write access to the doc-metrix organization on Github. If you are not already a member and are interested in contributing, contact one of the owners.

Repository

Enter the repository name. The default is the documentation name. Hit enter to accept the default as the repository name.

Author

Enter the primary author's name; i.e., in all likelihood that will be your name.

Email

If you have chosen to initialize the directory as a Git repository, the default will be the email associated with your Github account. This email should be a correspondence address for those individuals wanting to contact you directly with their questions and comments.

If the Github email address is fine, just type enter.

Description

Enter the documentation description.

Scaffold

Once you have answered all prompts, you will have the following scaffold:

doc/
	- index.json
.gitignore
LICENSE
README.md
TODO.md
bower.json

Dotfiles

These are standard fare. If you notice that files are not tracking in Git , consult .gitignore.

License

The default license is the MIT license.

Bower.json

The generator creates a scaffold bower.json. You need to manually add keywords. Individuals who want to use the documentation in their libraries can use Bower to manage the documentation as a dependency.

$ bower install <documentation_name> --save

By default, the Bower package name is the documentation name prefixed by doc-metrix-. Hence,

doc-metrix-<documentation_name>

In order to register the documentation with Bower, you must first tag a release.

$ git tag -a <major.minor.patch> -m "[UPDATE] version."
$ git push origin <major.minor.patch>

Use semantic versioning (semvar) for communicating versions.

Once tagged,

$ bower register doc-metrix-<documentation_name> git://github.com/doc-metrix/<documentation_name>

Documentation

The generator includes a TODO.md file. Use this file for general TODOs which are not tied to any particular file line.

The README.md is a scaffold. You should set the documentation name and add to the documentation description.

Resource

Add the metric documentation to doc/index.json.

Notes

If you opted to initialize the module as a Git repository, you will need to manually push changes to Github.

$ git push origin master

License

MIT license.


Copyright

Copyright © 2014. Nodeprime.