svn commit: r1026146 [2/2] - in /websites/staging/gora/trunk/content: ./ current/ current/api/ resources/css/

[buildbot]

Modified: websites/staging/gora/trunk/content/version_control.html
==============================================================================
--- websites/staging/gora/trunk/content/version_control.html (original)
+++ websites/staging/gora/trunk/content/version_control.html Thu Mar  1 
16:09:29 2018
@@ -93,7 +93,7 @@ under the License.
           <span class="icon-bar"></span>
           <span class="icon-bar"></span>
         </a>
-        <a class="brand" href="./index.html"><img 
src="./resources/img/gora-logo.png" alt="Apache Gora" title="Apache Gora" 
style="width: 50%; height: 50%;"/></a>
+        <a class="brand" href="./index.html"><img 
src="./resources/img/gora-logo.png" alt="Apache Gora" title="Apache Gora"/></a>
         <div class="nav-collapse collapse">
           <ul class="nav">
             <li><a href="./downloads.html">Downloads</a></li>
@@ -153,15 +153,24 @@ under the License.
     </div> <!-- /navbar-inner -->
   </div> <!-- /navbar -->
 
-  <hr>
-  
-  <div class="container" id="Gora_Gora Version Control System">
+  <div class="container top-buffer" id="Gora_Gora Version Control System">
 
-<h2 id="overview">Overview</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, 
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, 
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="overview">Overview<a class="headerlink" href="#overview" 
title="Permanent link">&para;</a></h2>
 <p>For code development on Gora trunk, we use the official Apache Git 
repository of 
 the Apache Software Foundation.</p>
-<h2 id="git-repository">Git Repository</h2>
-<h3 id="anonymous-access-read-only">Anonymous Access (read-only)</h3>
+<h2 id="git-repository">Git Repository<a class="headerlink" 
href="#git-repository" title="Permanent link">&para;</a></h2>
+<h3 id="anonymous-access-read-only">Anonymous Access (read-only)<a 
class="headerlink" href="#anonymous-access-read-only" title="Permanent 
link">&para;</a></h3>
 <p>The Apache git repository can be used for accessing development trunk code.
 The URL for anonymous read-only access is <a 
href="http://git.apache.org/gora.git/";>http://git.apache.org/gora.git/</a>. 
 Alternatively the Github mirror at <a 
href="http://github.com/apache/gora";>http://github.com/apache/gora</a> can also 
be used. 
@@ -171,7 +180,7 @@ The repository can be cloned by:</p>
 
 
 <p>More instructions for setting up git access can be found <a 
href="http://www.apache.org/dev/git.html";>here</a>.</p>
-<h3 id="committer-access-read-write">Committer Access (read-write)</h3>
+<h3 id="committer-access-read-write">Committer Access (read-write)<a 
class="headerlink" href="#committer-access-read-write" title="Permanent 
link">&para;</a></h3>
 <p>Committers should always clone the read-write codebase as this is the 
latest codebase
 that the development team is working on. It will also give you access to 
development 
 branches at any given time. </p>