readme
add deployment instructions to README
default repo to <org>/<project.name>
allow customization of description and keywords
ignore autogenerated files

They will create unnecessary merge conflicts every time people
pull stuff from here.

https://github.com/repo-utils/badgeboard/issues/1#issuecomment-52462600
make more helpful makefile

 - npm install if no modules present
 - make db if no src/db.json present
 - allow to override node/npm executables
 - etc.
trying to make a single well-commented config file

This isn't actually used anywhere yet, but editing three
files (maintainers.json, projects.json and build.js)
without any documentation is less than ideal.

We have yaml parser for travis anyway, so no extra dependency for this.
make everything use config file
don't fetch stuff that's not necessary

People can write custom layouts that don't use maintainer name
or node versions.

This allows to turn off those in config.
make columns wider to fit th on one line
split src/ to templates/ and scripts/

https://github.com/repo-utils/badgeboard/commit/d94465d4f43fd3a71395f43fb568b99a4e488fd6#commitcomment-7451995
make columns smaller

"lead maintainer" -> "maintainer", "project name" -> "project"

https://github.com/repo-utils/badgeboard/commit/0f00e9ac59f33945a33c949ab58c1c81831e7bcd#commitcomment-7452003
removed comment, but forgot to remove actual css

see https://github.com/repo-utils/badgeboard/commit/4ed9392e55df9d142e6e0ceb620cafccf7a67231
fix readme
really fix readme

@rlidwka: learn to use preview
Merge https://github.com/repo-utils/badgeboard
fix readme, rebuild, etc.