Author: buildbot
Date: Fri Jul 15 19:02:21 2016
New Revision: 992901
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:02:21 2016
@@ -1 +1 @@
-1752864
+1752865
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 15 19:02:21 2016
@@ -1 +1 @@
-1752864
+1752865
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:02:21 2016
@@ -206,8 +206,7 @@ where you can navigate to the source for
<p><em>Anyone with a GitHub account</em>
can suggest an edit to an Apache Taverna page directly in the browser.</p>
</blockquote>
-<p>Note that <strong>GitHub's rendering of the Markdown is not 100%
equivalent</strong> to the resulting HTML
-within the Apache CMS. In particular, the <code>Title:</code> and
<code>License:</code> headers at the top
+<p>Note that <strong>GitHub's rendering of the Markdown is not 100%
equivalent</strong> to the resulting Apache CMS HTML. In particular, the
<code>Title:</code> and <code>License:</code> headers at the top
of every <code>.md</code> file will not be rendered as shown on GitHub.</p>
<p>To submit your suggested change, raise a
<a href="https://github.com/apache/incubator-taverna-site/pulls";>GitHub pull
request</a>.
@@ -222,16 +221,16 @@ to watch for to any follow-up comments a
<p>If you are an <strong>Apache Taverna committer</strong>, use the
<a href="http://www.apache.org/dev/cmsref.html";>Apache CMS</a> directly from
<a href="https://cms.apache.org/taverna/";>https://cms.apache.org/taverna/</a>
using your <code>@apache.org</code> account as login.</p>
+<blockquote>
<p>Committers can also drag the
<a
href="javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))">Edit
in CMS</a>
bookmarklet to your browser toolbar or bookmark collection.</p>
-<p>See <a href="#cms-for-committers">CMS usage for committers</a> for how to
use the Apache CMS.</p>
+</blockquote>
+<p><a href="#cms-for-committers">CMS usage for committers</a> describes how to
use the Apache CMS.</p>
<h3 id="non-taverna-apache-committers">Non-Taverna Apache committers<a
class="headerlink" href="#non-taverna-apache-committers" title="Permanent
link">¶</a></h3>
<p>If you are an existing
<a href="https://people.apache.org/phonebook.html?unix=committers";>Apache
committer</a>,
-but don't have write access to the pages
-(e.g. you are not in the <code>incubator</code> group), your edit will be
sent as a
- suggested patch to the
+but are not in the <code>incubator</code> group, your suggested edit will be
sent as a patch to the
<a href="/community/lists#devtaverna">dev@taverna</a> mailing list.
Subscribe to the mailing list to respond to any feedback.</p>
<h3 id="anonymous-use-of-cms">Anonymous use of CMS<a class="headerlink"
href="#anonymous-use-of-cms" title="Permanent link">¶</a></h3>
@@ -243,7 +242,7 @@ by using the username <code>anonymous</c
<p>This can be beneficial if you
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 edit will be sent as a suggested patch to the
+<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>
<p><a name=cms-for-committers></a></p>
@@ -261,7 +260,7 @@ which you should subscribe to in order t
<li>Click <code>[Update]</code> to refresh the page</li>
<li>Click <code>[Edit]</code> to enter the editor</li>
</ul>
-<p><em>Or</em> use the [Apache CMS]((https://cms.apache.org/taverna/):</p>
+<p><em>Or</em> use the <a href="https://cms.apache.org/taverna/";>Apache
CMS</a>:</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>
@@ -272,11 +271,11 @@ which you should subscribe to in order t
<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>
+ ** You forgot the Quick Commit? No problem! Now, click <code>[Commit]</code>
followed by <code>Submit</code>.</p>
</li>
<li>
-<p>Click <code>[View Staging Build]</code> to see if CMS has built your
changes. Usually
- this is quite quick. Refresh the page, as necessary, to make sure there are
no "Current" or "Pending" jobs before you continue.</p>
+<p>Click <code>[View Staging Build]</code> to see if the CMS has built your
changes. (Usually
+ this is quite quick.) Refresh the page, as necessary, to make sure there
are no "Current" or "Pending" jobs before you continue.</p>
</li>
<li>
<p>Click <code>[Staging]</code> to see the result of your change (and anyone
else's at the same time)
@@ -302,7 +301,8 @@ which you should subscribe to in order t
<h3 id="linking-tips">Linking tips:<a class="headerlink" href="#linking-tips"
title="Permanent link">¶</a></h3>
<ul>
<li>
-<p><strong>Avoid <a href="http://www.cs.tut.fi/~jkorpela/www/click.html";>click
here</a> links.</strong> Link text should be understandable and flow with the
text. Rewrite the sentence, if needed.</p>
+<p><strong>Avoid <a href="http://www.cs.tut.fi/~jkorpela/www/click.html";>click
here</a> links.</strong>
+Link text should be understandable and flow with the text. Rewrite the
sentence, if needed.</p>
<ul>
<li>
<p>YES: <em>"Code is generated automatically by the <a
href="#">CodeGenerator</a> class."</em></p>
@@ -330,7 +330,7 @@ which you should subscribe to in order t
<p>Don't just say "You can find more in the documentation" - link to the right
place in the documentation.</p>
</li>
<li>
-<p>Deep-links are good, unless the target pages become confusing out of
context.</p>
+<p>Deep-links are good, unless the target pages become confusing.</p>
</li>
</ul>
</li>
@@ -363,11 +363,8 @@ which you should subscribe to in order t
</ul>
</li>
<li>
-<p><strong>Link to source code.</strong> More people may appreciate it than
you think. Who knows, maybe a patch is around the corner?</p>
-<ul>
-<li>Deep-link to source folder/file under the <code>incubator-taverna-*</code>
project at
- <a href="http://github.com/apache/";>GitHub</a></li>
-</ul>
+<p><strong>Link to source code.</strong> More people may appreciate it than
you think. Who knows, maybe a patch is around the corner? <strong>Deep-link to
source folder/file</strong> under the <code>incubator-taverna-*</code> project
at
+ <a href="http://github.com/apache/";>GitHub</a></p>
</li>
</ul>
<h3 id="if-you-are-adding-a-new-page">If you are adding a new page:<a
class="headerlink" href="#if-you-are-adding-a-new-page" title="Permanent
link">¶</a></h3>
@@ -384,12 +381,12 @@ which you should subscribe to in order t
</ul>
</li>
<li>
-<p><strong>Link from/to relevant existing Apache Taverna pages</strong> (not
just the hierarchical parent).</p>
+<p><strong>Link from/to relevant existing Apache Taverna pages</strong> (not
just the hierarchical parent).
+ For example, if <code>/code</code> describes the source code, and
<code>/community</code> different ways to contribute, <code>/code</code> should
link to the <code>/community</code> page and vice versa.</p>
+</li>
+<li>
+<p><strong>Include the page in the <a
href="https://github.com/apache/incubator-taverna-site/blob/trunk/templates/navbar.html";>navigation
menu bar</a></strong> and in the listing of a higher-level page.</p>
</li>
-</ul>
-<p>For example, if <code>/code</code> is describing the source code, and
<code>/community</code> different ways to contribute, <code>/code</code> should
link to the <code>/community</code> page and vice versa.</p>
-<ul>
-<li><strong>Include the page in the <a
href="https://github.com/apache/incubator-taverna-site/blob/trunk/templates/navbar.html";>navigation
menu bar</a></strong> and in the listing of a higher-level page.</li>
</ul></div>
</div>
