[45/47] tinkerpop git commit: Updated committers docs about site publishing.

[sp...@apache.org]

Updated committers docs about site publishing.


Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/7bfc8686
Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/7bfc8686
Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/7bfc8686

Branch: refs/heads/TINKERPOP-1235
Commit: 7bfc8686aff4215f6069c34bf8e08d586dd8ad32
Parents: 1661729
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Thu Oct 27 07:58:11 2016 -0400
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Thu Oct 27 07:58:11 2016 -0400

----------------------------------------------------------------------
 docs/src/dev/developer/for-committers.asciidoc | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/7bfc8686/docs/src/dev/developer/for-committers.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/dev/developer/for-committers.asciidoc b/docs/src/dev/developer/for-committers.asciidoc
index ca9c2c2..f2ae9ff 100644
--- a/docs/src/dev/developer/for-committers.asciidoc
+++ b/docs/src/dev/developer/for-committers.asciidoc
@@ -440,6 +440,21 @@ uploaded to the server and should preserve the directory structure in git as ref
 Please see the <<building-testing,Building and Testing>> section for more information on how to generate the
 documentation.
 
+[[site]]
+Site
+----
+
+The content for the TinkerPop home page and related pages that make up the web site at link://tinkerpop.apache.org[tinkerpop.apache.org]
+is stored in the git repository under `/docs/site`. In this way, it becomes easier for the community to provide content
+presented there, because the content can be accepted via the standard workflow of a pull request. To generate the site
+for local viewing, run `bin/generate-home.sh`, which will build the site in `target/site/`. PMC members can officially
+publish the site with `bin/publish-home.sh <username>`.
+
+"Publishing" does not publish documentation (e.g. reference docs, javadocs, etc) and only publishes what is generated
+from the content in `/docs/site`. Publishing the site can be performed out of band with the release cycle and is no
+way tied to a version. The `master` branch should always be considered the "current" web site and publishing should
+only happen from that branch.
+
 [[logging]]
 Logging
 -------