docs: individual package support

[callmehiphop]

Closes #1475
Relates to #1471
Depends on https://github.com/GoogleCloudPlatform/gcloud-common/pull/157

Demo

[callmehiphop]

@stephenplusplus I'm kinda puzzled on the deployment strategy for this.. seems like there's a lot of duplicated logic between

• scripts/release.sh
• scripts/build.sh
• scripts/publish.js

Should travis be where we update the individual modules JSON in ghpages? Or in the publish script? I'm a little lost about which scripts fire when now.

[coveralls]

Coverage remained the same at 100.0% when pulling 78fef07 on callmehiphop:modular-json-docs into 2613bcc on GoogleCloudPlatform:master.

[stephenplusplus]

I think anything touching gh-pages should be handled by Travis.

publish.js should just be a convenience wrapper around several commands that we would have to run manually, which will

• create a git tag
• run npm version
• run npm publish
• push to github

Because the publish script in my PR will create a custom git tag (e.g. bigquery-0.1.0), the release.sh script will run because it's a tagged commit. It will need to be modified to parse the git tag (tag.split('-')[0] = module name, tag.split('-')[1] = version number).

[stephenplusplus]

fixed typo above (npm publish not npm docs)

[stephenplusplus]

LGTM!

[coveralls]

Coverage remained the same at 100.0% when pulling bf408fa on callmehiphop:modular-json-docs into 2613bcc on GoogleCloudPlatform:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 1cb8447 on callmehiphop:modular-json-docs into 2613bcc on GoogleCloudPlatform:master.