Projectz

Stop wasting time syncing and updating your project's README and Package Files!

Used by over 300 repositories and 200 projects thus far!

Watch the talk.

Here's some of the things it can do:

• Keep your projects data files synchronised appropriately, supports:
  • package.json
  • bower.json
  • component.json
  • jquery.json
• Create beautiful standardised readme files that stay in sync with your data files, supports:
  • README
  • CONTRIBUTING
  • LICENSE
  • BACKERS
  • HISTORY
• Automatic injection of the appropriate installation methods, supports:
  • NPM
  • Browserify
  • Ender
  • Component
  • Bower
  • Editions
  • DocPad Plugins
• Automatic injection of your desired badges
• Automatic injection of your SPDX license information
• Keep your data and readme files up to date with remote data, supports:
  • Pulling in your latest contributors from GitHub
  • Pulling in your latest sponsors from remote APIs (coming soon)

Install

NPM

• Install: npm install --global projectz
• Executable: projectz

Editions

This package is published with the following editions:

• projectz aliases projectz/index.js which uses Editions to automatically select the correct edition for the consumers environment
• projectz/source/index.js is Source + ESNext + Require + Flow Type Comments
• projectz/es2015/index.js is Babel Compiled + ES2015 + Require

Older environments may need Babel's Polyfill or something similar.

Running Projectz

Directly

Once installed locally, you can compile your project using projectz by running the following in your terminal:

node ./node_modules/.bin/projectz compile

Automatically

To make projectz more automatic, we recommended adding the direct command above to your build tool.

If you don't use a build tool, but do use npm, then you can add the following to your project's package.json file:

{
  "scripts": {
    "compile": "projectz compile",
    "posttest": "npm run compile"
  }
}

The compile script here is runnable via the command npm run-script compile and will compile your project with projectz.

The posttest script here automatically compiles your project with projectz after your tests have successfully completed, providing you use npm test to run your tests. This is a great place to put projectz as projectz only updates meta documents so won't affect your test, and will always run before a publish.

GitHub Rate Limiting

If you get a rate limit warning, you will need to add GITHUB_ACCESS_TOKEN (or a GITHUB_CLIENT_ID AND GITHUB_CLIENT_SECRET combination) to your environment. To do this:

1. Create a personal access token for your computer at: https://github.com/settings/tokens
2. Projectz needs the readonly/access permissions for repos and users
3. Generate the token and copy it
4. Inside your dotfile profile (.bashrc, .zshrc) add export GITHUB_ACCESS_TOKEN="the token value"
5. Open a new shell, or run export GITHUB_ACCESS_TOKEN="the token value" in your current shell
6. Run projectz again

Configuring Projectz

Data Files

Projectz helps you maintain the following data files:

• package.json
• bower.json
• component.json
• jquery.json

It does this by reading them, combining their data in memory, and then outputting the appropriate fields and over-rides for each file.

If you are making use of multiple meta data files, you may find defining a projectz meta file (projectz.json for JSON, or projectz.cson for CSON) to be useful. The projectz meta file can serve as a central location for the configuration of all the other files. However, if you only require one meta data file, then you can ignore this ability.

Projectz takes notes of these meta data fields:

{
	// Specify your project's human readable name
	"title": "Projectz",

	// Specify your project name
	"name": "projectz",

	// Specify your project's Website URL
	"homepage": "https://github.com/bevry/projectz",

	// Specify your project's demo URL
	// If this is missing, and `homepage` is set, we set it to the `homepage` value
	"demo": "https://github.com/bevry/projectz",

	// Specify your project description
	"description": "Stop wasting time syncing and updating your project's README and Package Files!",

	// Specify your project's SPDX License
	// Uses https://www.npmjs.com/packages/spdx for parsing
	"license": "MIT",

	// Specify your whether the project can run on the client-side in web browsers
	// If this is missing, and the component or bower package files exist, then this becomes `true`
	"browsers": true,

	// Specify your project's author details
	// Can be an array or CSV string
	"author": "2013+ Bevry Pty Ltd <us@bevry.me> (http://bevry.me)",

	// Specify your maintainers
	"maintainers": [
		"Benjamin Lupton (b@lupton.cc) (http://balupton.com)"
	],

	// Specify your sponsors
	"sponsors": [
		"Benjamin Lupton (b@lupton.cc) (http://balupton.com)"
	],

	// Specify your contributors
	// This is automatically combined with the contributors from the GitHub Repository API
	"contributors": [
		"Benjamin Lupton (b@lupton.cc) (http://balupton.com)"
	],

	// Specify your project's repository details
	// If this is missing, and `homepage` is a GitHub URL, this determined automatically
	"repository": {
		"type": "git",
		"url": "https://github.com/bevry/projectz.git"
	},

	// Specify your project's issue tracker
	// If this is missing, and `repository` is a GitHub repository, this determined automatically
	"bugs": {
		"url": "https://github.com/bevry/projectz/issues"
	},

	// Specify your project's badges for use in the readme files
	// Projectz renders badges by sending the `badges` field to the `badges` package.
	// Below is some sample projectz configuration for this field to render our most common badges.
	// Even more badge types and configurations are available than just those included below.
	// Complete details of what is available can be found over at the badges package:
	// https://github.com/bevry/badges
	"badges": {
		"list": [
			"travisci",
			"npmversion",
			"npmdownloads",
			"daviddm",
			"daviddmdev",
			"---",
			"slackin",
			"patreon",
			"gratipay",
			"flattr",
			"paypal",
			"bitcoin",
			"wishlist"
		],
		"config": {
			"patreonUsername": "bevry",
			"gratipayUsername": "bevry",
			"flattrUsername": "balupton",
			"paypalURL": "https://bevry.me/paypal",
			"bitcoinURL": "https://bevry.me/bitcoin",
			"wishlistURL": "https://bevry.me/wishlist",
			"slackinURL": "https://slack.bevry.me"
		}
	},

  // If you are using the projectz meta file, you can also define this field
  // it allows you to set the configuration for other package systems
  "packages": {
    "bower": {},
    "component": {},
    "jquery": {}
  }
}

Readme Files

Projectz helps you maintain the following readme files:

• README.md
• CONTRIBUTING.md
• LICENSE.md
• BACKERS.md
• HISTORY.md

It does this by reading them, and replacing comment tags with the appropriate data.

The following comment tags are supported:

• <!-- TITLE --> — outputs the package's title field
• <!-- BADGES --> — outputs the badges you have enabled from your package's badges field
• <!-- DESCRIPTION --> — outputs the package's description field
• <!-- INSTALL --> — outputs the package's installation instructions
• <!-- HISTORY --> — outputs a link to the HISTORY file if it exists, otherwise if it is a Github repository, outputs a link to the releases page
• <!-- CONTRIBUTE --> — outputs a link to the CONTRIBUTE file if it exists
• <!-- BACKERS --> — outputs who the backers are for the project, including maintainers, sponsors, funding badges, and contributors
• <!-- LICENSE --> — outputs a summary of the license information

As well as these comment tags for updating entire files:

• <!-- LICENSEFILE --> — outputs the complete license information
• <!-- BACKERSFILE --> — same as <!-- BACKERS --> but made for an individual file instead

As an example, here is a a basic README.md file:

<!-- TITLE -->
<!-- BADGES -->
<!-- DESCRIPTION -->
<!-- INSTALL -->

## Usage
Usage instructions go here

<!-- HISTORY -->
<!-- CONTRIBUTE -->
<!-- BACKERS -->
<!-- LICENSE -->

This README is also, expectedly, built with projectz. View its source.

History

Discover the release history by heading on over to the HISTORY.md file.

Contribute

Discover how you can contribute by heading on over to the CONTRIBUTING.md file.

Backers

Maintainers

These amazing people are maintaining this project:

• Benjamin Lupton — view contributions
• Rob Loach — view contributions

Sponsors

No sponsors yet! Will you be the first?

Contributors

These amazing people have contributed code to this project:

• Benjamin Lupton — view contributions
• Peter Flannery — view contributions
• Rob Loach — view contributions
• Zearin — view contributions
• vsopvsop — view contributions
• Shahar Or — view contributions
• Zlatan Vasović — view contributions

Discover how you can contribute by heading on over to the CONTRIBUTING.md file.

License

Unless stated otherwise all works are:

• Copyright © 2013+ Bevry Pty Ltd

and licensed under:

• MIT License