Author: buildbot
Date: Wed Mar 26 15:01:11 2014
New Revision: 903767
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 15:01:11 2014
@@ -1 +1 @@
-1581870
+1581878
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 15:01:11 2014
@@ -71,24 +71,46 @@
<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://www.apache.org/dev/cms";>Apache CMS</a>. </p>
+<p>The thrift website is made up of markdown files with YAML headers, and
templates, and uses the <a href="http://www.apache.org/dev/cms";>Apache
CMS</a>.</p>
<h3 id="website-development">Website Development</h3>
<p>Publishing the staging site is doable through the <a
href="https://cms.apache.org/thrift/";>CMS webgui</a> or via shell command:</p>
<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/thrift/#bookmark";>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>More complex changes can be accomplished by checking out the <a
href="https://svn.apache.org/repos/asf/thrift/cms-site";>svn tree</a> directly.
Commits to that tree will trigger builds of the staging site just as if you had
committed them by using the CMS webgui. If you are still pining for a
nanoc-like feature to preview your changes before committing them by having a
daemon 'watch' your filesystem for edits, you really need to wrap your brain
around the CMS's <strong> commit early and commit often </strong> mantra. In
fact source control systems are far more effective at communicating changesets
than operating systems are (most of the time), and the CMS's build system is
changeset-aware based on the data it receives from svn. So think of committing
to the CMS's svn tree for thrift as just a formal way of notifying the CMS of
your changes so it can automatically (and efficiently) build them to the
staging site, just as if you were working locally with a daemon that watches yo
ur filesystem for modifications and builds them.</p>
+<p>Casual changes to the site are best handled through the <a
href="https://cms.apache.org/thrift/#bookmark";>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>More complex changes can be accomplished by checking out the <a
href="https://svn.apache.org/repos/asf/thrift/cms-site";>svn
+tree</a> directly. Commits to that tree will
+trigger builds of the staging site just as if you had committed them by using
the CMS webgui.
+If you are still pining for a nanoc-like feature to preview your changes
before committing them
+by having a daemon 'watch' your filesystem for edits, you really need to wrap
your brain around
+the CMS's <strong> commit early and commit often </strong> mantra. In fact
source control systems are far
+more effective at communicating changesets than operating systems are (most of
the time), and
+the CMS's build system is changeset-aware based on the data it receives from
svn. So think of
+committing to the CMS's svn tree for thrift as just a formal way of notifying
the CMS of your
+changes so it can automatically (and efficiently) build them to the staging
site, just as if
+you were working locally with a daemon that watches your filesystem for
modifications and
+builds them.</p>
<h3 id="updating-release-versions">Updating Release Versions</h3>
-<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>
+<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 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>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>
</div>
<div class="container">
<hr>
