Now that I've gotten started on new docs I'm realizing that it makes things way more complicated to have a separate docs repo. An API change would require two commits into two different repos—no more checking a PR and examining app code, tests, and docs all in one diff. Instead of the current structure, the docs folder would contain the actual markup that gets assembled into the documentation. The groc docs would not be checked in to master.
Travis can handle all the deploy steps, including generating docs and publishing to the gh_pages branch after a successful build. Travis can also deploy to npm on tagged releases.
@tgriesser @johanneslumpe
Now that I've gotten started on new docs I'm realizing that it makes things way more complicated to have a separate docs repo. An API change would require two commits into two different repos—no more checking a PR and examining app code, tests, and docs all in one diff. Instead of the current structure, the docs folder would contain the actual markup that gets assembled into the documentation. The groc docs would not be checked in to master.
Travis can handle all the deploy steps, including generating docs and publishing to the gh_pages branch after a successful build. Travis can also deploy to npm on tagged releases.