Skip to content

䷇ Generate and share dictionaries on your repositories to facilitate communication and avoid confusion with canonical terms: share a common vocabulary.

License

Notifications You must be signed in to change notification settings

commonality/common-vocabulary

Repository files navigation

commonality/common-vocabulary logo

common-vocabulary

Facilitate communication and avoid confusion with canonical terms: share a common vocabulary.

License NPM version FOSSA Status NSP Status
Dependency drift Dev dependency drift
macOS Build Status AppVeyor Windows build status Coverage percentage Codacy Badge PRs Welcome

Table of contents

Installation

Prerequisite software

common-vocabulary is written for Node.js, which must be installed prior to use. Unspecified requires npm, which is used for installing dependencies.

# Install with Unspecified
$ npm i common-vocabulary -g

Usage

You can add, edit, and remove entries directly from a Terminal.

common-vocabulary
# => Creates docs/common-vocabulary.md

API

const CommonVocabulary = require('common-vocabulary')

const cv = new CommonVocabulary()
cv.toHtml()

Semantic version and CHANGELOG

The latest version of common-vocabulary is 1.1.0. View the CHANGELOG for details.

Contributing

Learn how to make a Pull Request with free training We welcome contributions with Pull Requests (PRs)!


Request a feature Report a defect

Read the CONTRIBUTING guidelines


Contributions in the form of GitHub pull requests are welcome. Before embarking on a significant change, please adhere to the following guidelines:

  1. Create an issue—e.g., a defect ("bug") report or a feature request—to propose changes.

    Exceptions:

    If you're working on documentation and fixing something simple like a typo or an easy bug, go ahead and make a pull request.

  2. Follow the CONTRIBUTING guidelines.

    Why:

    Standards and guidelines make communication easier. If you're willing and able to program—or want to learn how— following the guidelines will increase the likelihood of adding your changes to the software product.

  3. Read the Code of Conduct.

    Why:

    It's more fun when everybody's friendly and respectful.

  4. Make a pull request when you're ready for other to review your changes (or you get stuck somewhere).

    PR novices:

    🙋 Never created a pull request? No problem. 🆓 Take this free online training. (It even covers most of the conventions in the CONTRIBUTING guidelines!)

License

MIT © commonality.

FOSSA Status


Greenkeeper badge README doc score

Graphic art by icons8.

About

䷇ Generate and share dictionaries on your repositories to facilitate communication and avoid confusion with canonical terms: share a common vocabulary.

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published