Author: buildbot
Date: Wed Mar 26 02:46:02 2014
New Revision: 903672
Log:
Staging update by buildbot for thrift
Modified:
websites/staging/thrift/trunk/content/ (props changed)
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
Propchange: websites/staging/thrift/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 26 02:46:02 2014
@@ -1 +1 @@
-1581628
+1581645
Modified:
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
==============================================================================
---
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
(original)
+++
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
Wed Mar 26 02:46:02 2014
@@ -71,8 +71,15 @@
<div class="container">
<h2 id="apache-thrift-website">Apache Thrift Website</h2>
-<p>The thrift website is made up of markdown files and templates and uses the
<a href="http://nanoc.ws";>nanoc</a> static website generator. </p>
+<p>The thrift website is made up of markdown files and templates and uses the
(Apache CMS)[http://www.apache.org/dev/cms]. </p>
<h3 id="website-development">Website Development</h3>
+<h4
id="obsolete-there-are-no-prerequisites-for-working-productively-with-the-cms-publishing-the-site-is-doable-through-the-cms-webgui-or-via-shell-command">OBSOLETE:
there are NO prerequisites for working productively with the CMS. Publishing
the site is doable through the <a
href="https://cms.apache.org/thrift/publish";>CMS webgui</a> or via shell
command:</h4>
+<div class="codehilite"><pre><span class="c">% ssh -t people.apache.org
publish.pl thrift</span>
+</pre></div>
+
+
+<p>Casual changes to the site are best handled through the <a
href="https://cms.apache.org/#bookmarklet";>javascript bookmarklet</a>. The
workflow is to browse the live site looking for pages in need of repair, then
by clicking on the bookmarklet you will be redirected to an editor for the page
in question that can ultimately commit your changes back to the site and walk
you through the publication process through the webgui.</p>
+<p>Obsolete content follows...</p>
<p>In order to get started developing and testing the Thrift website ruby must
be installed along with the bundler gem.</p>
<ul>
<li>Install Bundler: <ul>
@@ -92,14 +99,15 @@
</li>
</ul>
<h3 id="updating-release-versions">Updating Release Versions</h3>
-<p>The current release versioning is kept in the global configuration file
config.yaml. Update the following values and then following <b>Updating the
Website</b> section below </p>
+<p>The current release versioning is kept in the YAML <strong>DATA</strong>
section of the global "configuration file" <a
href="https://svn.apache.org/repos/asf/thrift/cms-site/trunk/lib/path.pm";>lib/path.pm</a>.
Update the following values and then following <b>Updating the Website</b>
section below </p>
<div class="codehilite"><pre><span class="n">current_release</span><span
class="p">:</span> "0<span class="p">.</span>9<span
class="p">.</span>1"
<span class="n">current_release_date</span><span class="p">:</span>
"2013<span class="o">-</span>08<span class="o">-</span>21"
</pre></div>
<h3 id="updating-the-website">Updating the website</h3>
-<p>After you have updated any content or added new markdown files you will
need to regenerate the static website and publish these changes. </p>
+<p>After you have updated any content or added new markdown files you will
need to commit them to svn to trigger a <a
href="http://ci.apache.org/builders/thrift-site-staging";>CMS build</a> of your
changes. After a few seconds have passed your build will be ready for viewing
on the <a href="http://thrift.staging.apache.org/";>staging site</a>. See the
previous discussion for the various approaches to publishing your changes to
the live site after you have verified they are rendering correctly on the
staging site.</p>
+<p>Obsolete content follows...</p>
<ul>
<li>rake gen (static website is left in the 'output' folder)</li>
<li>Check in all the changes</li>
