Author: buildbot
Date: Fri Jul 15 19:13:44 2016
New Revision: 992904
Log:
Staging update by buildbot for taverna
Modified:
websites/staging/taverna/trunk/cgi-bin/ (props changed)
websites/staging/taverna/trunk/content/ (props changed)
websites/staging/taverna/trunk/content/community/edit.html
Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 15 19:13:44 2016
@@ -1 +1 @@
-1752865
+1752867
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 15 19:13:44 2016
@@ -1 +1 @@
-1752865
+1752867
Modified: websites/staging/taverna/trunk/content/community/edit.html
==============================================================================
--- websites/staging/taverna/trunk/content/community/edit.html (original)
+++ websites/staging/taverna/trunk/content/community/edit.html Fri Jul 15
19:13:44 2016
@@ -243,8 +243,7 @@ by using the username <code>anonymous</c
prefer not to use GitHub, or if you want to suggest larger changes that
involve renames, etc.</p>
<p>Note that in this case your suggested edit will be sent as a patch to the
-<a href="/community/lists#devtaverna">dev@taverna</a> mailing list,
-which you should subscribe to in order to respond to any feedback.</p>
+<a href="/community/lists#devtaverna">dev@taverna</a> mailing list. Please
subscribe to the mailing list to receive and respond to any feedback.</p>
<p><a name=cms-for-committers></a></p>
<h2 id="cms-usage-for-committers">CMS usage for committers<a
class="headerlink" href="#cms-usage-for-committers" title="Permanent
link">¶</a></h2>
<p>Before editing an Apache Taverna web page, familiarize yourself with the <a
href="http://www.apache.org/dev/cmsref.html#flow";>CMS information flow</a>.</p>
@@ -255,12 +254,20 @@ which you should subscribe to in order t
<h3 id="opening-the-file">Opening the file<a class="headerlink"
href="#opening-the-file" title="Permanent link">¶</a></h3>
<p>Open the file in the editor using the <strong>Edit in CMS</strong>
bookmarklet:</p>
<ul>
-<li>Navigate to the page you want to edit</li>
-<li>Click the bookmarklet and log in</li>
-<li>Click <code>[Update]</code> to refresh the page</li>
-<li>Click <code>[Edit]</code> to enter the editor</li>
+<li>
+<p>Navigate to the page you want to edit</p>
+</li>
+<li>
+<p>Click the bookmarklet and log in</p>
+</li>
+<li>
+<p>Click <code>[Update]</code> to refresh the page</p>
+</li>
+<li>
+<p>Click <code>[Edit]</code> to enter the editor</p>
+</li>
</ul>
-<p><em>Or</em> use the <a href="https://cms.apache.org/taverna/";>Apache
CMS</a>:</p>
+<p><em>Or</em> use the <strong><a
href="https://cms.apache.org/taverna/";>Apache CMS</a></strong>:</p>
<ul>
<li>Click <code>Get taverna Working Copy</code></li>
<li>Click on <code>Parent Directory</code>, and then click <code>[Update this
directory]</code></li>
@@ -270,8 +277,8 @@ which you should subscribe to in order t
<h3 id="committing-and-publishing-your-changes">Committing and publishing your
changes<a class="headerlink" href="#committing-and-publishing-your-changes"
title="Permanent link">¶</a></h3>
<ul>
<li>
-<p>Tick <code>Quick Commit : [ ]</code> and click <code>Submit</code>
- ** You forgot the Quick Commit? No problem! Now, click <code>[Commit]</code>
followed by <code>Submit</code>.</p>
+<p>Tick <code>Quick Commit : [ ]</code>, enter a commit message, and click
<code>Submit</code>.
+ **You forgot the Quick Commit? No problem! Click <code>[Commit]</code> and
enter your message followed by <code>Submit</code>.</p>
</li>
<li>
<p>Click <code>[View Staging Build]</code> to see if the CMS has built your
changes. (Usually
@@ -327,7 +334,7 @@ Link text should be understandable and f
<p><strong>Everything is easier with a link.</strong></p>
<ul>
<li>
-<p>Don't just say "You can find more in the documentation" - link to the right
place in the documentation.</p>
+<p>Link to the right place in the documentation rather than saying, "You can
find more in the documentation."</p>
</li>
<li>
<p>Deep-links are good, unless the target pages become confusing.</p>
@@ -352,7 +359,7 @@ Link text should be understandable and f
<p><strong>Start internal links with <code>/</code></strong> unless they are
part of the same sub-folder.</p>
</li>
<li>
-<p><strong>Don't include extensions</strong> (<code>.html</code> or
<code>.cgi</code>) in the internal links. It doesn't just look nice, this gives
us flexibility to later use a folder <code>page/</code> instead of
<code>page.html</code>.</p>
+<p><strong>Don't include extensions</strong> (<code>.html</code> or
<code>.cgi</code>) in the internal links. It not only looks nice, but also
gives us flexibility to later use a folder <code>page/</code> instead of
<code>page.html</code>.</p>
<ul>
<li>
<p>YES: <code>/introduction/why-use-workflows</code></p>
