qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jr...@apache.org
Subject svn commit: r1504439 - in /qpid/site: ./ docs/ docs/components/ docs/components/dispatch/ input/ input/components/ input/components/dispatch/
Date Thu, 18 Jul 2013 11:46:27 GMT
Author: jross
Date: Thu Jul 18 11:46:27 2013
New Revision: 1504439

URL: http://svn.apache.org/r1504439
Log:
QPID-5001: Update dispatch content for style conventions and small punctuation-level issues;
add an initial style guide

Modified:
    qpid/site/README
    qpid/site/docs/components/dispatch/addressing.html
    qpid/site/docs/components/dispatch/index.html
    qpid/site/docs/components/index.html
    qpid/site/docs/site.html
    qpid/site/input/components/dispatch/addressing.md
    qpid/site/input/components/dispatch/index.md
    qpid/site/input/components/index.md
    qpid/site/input/site.md

Modified: qpid/site/README
URL: http://svn.apache.org/viewvc/qpid/site/README?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/README (original)
+++ qpid/site/README Thu Jul 18 11:46:27 2013
@@ -83,6 +83,11 @@ is set to <http://qpid.apache.org>, for 
 
 You can see more definitions in `input/site.conf`.
 
+## Style guide
+
+See <http://qpid.apache.org/site.html#style-guide> for site guidelines
+for formatting and style.
+
 ## Generating release content
 
 Most of the site content is written by human beings.  Release content,

Modified: qpid/site/docs/components/dispatch/addressing.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/dispatch/addressing.html?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/docs/components/dispatch/addressing.html (original)
+++ qpid/site/docs/components/dispatch/addressing.html Thu Jul 18 11:46:27 2013
@@ -21,7 +21,7 @@
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   <head>
-    <title>Qpid Dispatch Router - Addressing - Apache Qpid&#153;</title>
+    <title>Qpid Dispatch Addressing - Apache Qpid&#153;</title>
     <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
     <link rel="stylesheet" href="http://qpid.apache.org/site.css" type="text/css"/>
     <link rel="stylesheet" href="http://qpid.apache.org/pygments.css" type="text/css"/>
@@ -46,16 +46,16 @@
         </ul>
       </div>
       <div id="middle">
-        <ul id="path-navigation"><li><a href="http://qpid.apache.org/components/index.html">Components</a></li><li><a
href="http://qpid.apache.org/components/dispatch/index.html">Qpid Dispatch Router</a></li><li>Qpid
Dispatch Router - Addressing</li></ul>
-        <h1 id="qpid-dispatch-router-addressing">Qpid Dispatch Router - Addressing</h1>
+        <ul id="path-navigation"><li><a href="http://qpid.apache.org/components/index.html">Components</a></li><li><a
href="http://qpid.apache.org/components/dispatch/index.html">Qpid Dispatch Router</a></li><li>Qpid
Dispatch Addressing</li></ul>
+        <h1 id="qpid-dispatch-addressing">Qpid Dispatch Addressing</h1>
 
 <p>AMQP addresses are used to control the flow of messages across a network of
 routers.  Addresses are used in a number of different places in the AMQP 1.0
-protocol.  They can be used in a specific message in the <em>to</em> and <em>reply-to</em>
+protocol.  They can be used in a specific message in the <code>to</code> and
<code>reply-to</code>
 fields of a message's properties.  They are also used during the creation of
-links in the <em>address</em> field of a <em>source</em> or a <em>target</em>.</p>
+links in the <code>address</code> field of a <code>source</code>
or a <code>target</code>.</p>
 
-<h2 id="routing-mechanisms">Routing Mechanisms</h2>
+<h2 id="routing-mechanisms">Routing mechanisms</h2>
 
 <p>The fact that addresses can be used in different ways suggests that message
 routing can be accomplished in different ways.  Before going into the specifics
@@ -63,43 +63,43 @@ of the different routing mechanisms, it 
 meant by the term <em>routing</em>:</p>
 
 <blockquote>
-  <p>In a network built of multiple routers connected by connections (i.e. nodes and
+  <p>In a network built of multiple routers connected by connections (i.e., nodes and
   edges in a graph), <em>routing</em> determines which connection to use to send
a message
   directly to its destination or one step closer to its destination.</p>
 </blockquote>
 
 <p>Each router serves as the terminus of a collection of incoming and outgoing links.
-Some of the links are designated for message-routing and others are designated for
-link-routing.  In both cases, the links either connect directly to endpoints that
-produce and consume messages or they connect to other routers in the network along
+Some of the links are designated for message routing, and others are designated for
+link routing.  In both cases, the links either connect directly to endpoints that
+produce and consume messages, or they connect to other routers in the network along
 previously established connections.</p>
 
-<h3 id="message-routing">Message Routing</h3>
+<h3 id="message-routing">Message routing</h3>
 
 <p>Message routing occurs upon delivery of a message and is done based on the address
-in the message's <em>to</em> field.</p>
+in the message's <code>to</code> field.</p>
 
 <p>When a delivery arrives on an incoming message-routing link, the router extracts
the
-address from the delivered message's <em>to</em> field and looks the address
up in its
+address from the delivered message's <code>to</code> field and looks the address
up in its
 routing table.  The lookup results in zero or more outgoing links onto which the message
-shall be re-sent.</p>
+shall be resent.</p>
 
 <table>
 <tbody>
 <tr><td><em>Delivery</em></td><td><em>Handling</em></td></tr>
-<tr><td><em>pre-settled</em></td><td>If the arriving
delivery is pre-settled (i.e. fire and forget), the incoming delivery shall be settled by
the router and the outgoing deliveries shall also be pre-settled. In other words, the pre-settled
nature of the message delivery is propagated across the network to the message's destination(s).</td></tr>
+<tr><td><em>pre-settled</em></td><td>If the arriving
delivery is pre-settled (i.e., fire and forget), the incoming delivery shall be settled by
the router, and the outgoing deliveries shall also be pre-settled. In other words, the pre-settled
nature of the message delivery is propagated across the network to the message's destination.</td></tr>
 <tr><td><em>unsettled</em></td><td>Unsettled delivery
is also propagated across the network.  Because unsettled delivery records cannot be discarded,
the router tracks the incoming deliveries and keeps the association of the incoming deliveries
to the resulting outgoing deliveries.  This kept association allows the router to continue
to propagate changes in delivery state (settlement and disposition) back and forth along the
path which the message traveled.</td></tr>
 </tbody>
 </table>
 
-<h3 id="link-routing">Link Routing</h3>
+<h3 id="link-routing">Link routing</h3>
 
 <p>Link routing occurs when a new link is attached to the router across one of its
AMQP connections.
-It is done based on the <em>target.address</em> field of an inbound link and
the <em>source.address</em> field
+It is done based on the <code>target.address</code> field of an inbound link
and the <code>source.address</code> field
 of an outbound link.</p>
 
-<p>Link routing uses the same routing table that message routing uses.  This difference
is that the
-routing occurs during the link-attach operation and link-attaches are propagated along the
appropriate
+<p>Link routing uses the same routing table that message routing uses.  The difference
is that the
+routing occurs during the link-attach operation, and link attaches are propagated along the
appropriate
 path to the destination.  What results is a chain of links, connected end-to-end, from source
to
 destination.  It is similar to a <em>virtual circuit</em> in a telecom system.</p>
 

Modified: qpid/site/docs/components/dispatch/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/dispatch/index.html?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/docs/components/dispatch/index.html (original)
+++ qpid/site/docs/components/dispatch/index.html Thu Jul 18 11:46:27 2013
@@ -49,15 +49,16 @@
         <ul id="path-navigation"><li><a href="http://qpid.apache.org/components/index.html">Components</a></li><li>Qpid
Dispatch Router</li></ul>
         <h1 id="qpid-dispatch-router">Qpid Dispatch Router</h1>
 
-<p>A lightweight message router, written in C, built on Qpid Proton, that provides
-flexible and scalable interconnect between AMQP endpoints or between endpoints
+<p>A lightweight message router, written in C and built on
+<a href="http://qpid.apache.org/proton/index.html">Qpid Proton</a>, that provides
flexible
+and scalable interconnect between AMQP endpoints or between endpoints
 and brokers.</p>
 
 <table>
 <tbody>
 <tr><td><em>Platforms</em></td><td>Linux</td></tr>
-<tr><td><em>Protocols</em></td><td>AMQP 1.0</td></tr>
-<tr><td><em>Download</em></td><td><i>Coming Soon</i></td></tr>
+<tr><td><em>AMQP versions</em></td><td>1.0</td></tr>
+<tr><td><em>Download</em></td><td><em>Coming soon</em></td></tr>
 <tr><td><em>Source location</em></td><td><a href="http://svn.apache.org/repos/asf/qpid/trunk/qpid/extras/dispatch/">http://svn.apache.org/repos/asf/qpid/trunk/qpid/extras/dispatch/</a></td></tr>
 <tr><td><em>Issues</em></td><td><a href="https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+%3D+%22Bug%22+and+status+in+%28%22Open%22%2C+%22Reopened%22%2C+%22In+Progress%22%2C+%22Ready+To+Review%22%29+and+component+%3D+%22Qpid+Dispatch%22">Open
bugs</a>, <a href="https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+in+%28%22New+Feature%22%2C+%22Improvement%22%29+and+status+in+%28%22Closed%22%2C+%22Resolved%22%29+and+resolution+%3D+%22Fixed%22+and+component+%3D+%22Qpid+Dispatch%22">Completed
enhancements</a>, <a href="https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+in+%28%22New+Feature%22%2C+%22Improvement%22%29+and+status+in+%28%22Open%22%2C+%22Reopened%22%2C+%22In+Progress%22%2C+%22Ready+To+Review%22%29+and+component+%3D+%22Qpid+Dispatch%22">Requested
enhancements</a></td></tr>
 </tbody>
@@ -66,15 +67,15 @@ and brokers.</p>
 <h2 id="benefits">Benefits</h2>
 
 <ul>
-<li>Simplifies Connectivity
+<li>Simplifies connectivity
 <ul>
 <li>An endpoint can do all of its messaging through a single transport connection</li>
-<li>Avoid opening holes in Firewalls for incoming connections</li>
+<li>Avoid opening holes in firewalls for incoming connections</li>
 </ul></li>
-<li>Simplifies Reliability
+<li>Simplifies reliability
 <ul>
-<li>Reliability and Availability are provided using redundant topology, not server
clustering</li>
-<li>Reliable messaging end-to-end without persistent stores</li>
+<li>Reliability and availability are provided using redundant topology, not server
clustering</li>
+<li>Reliable end-to-end messaging without persistent stores</li>
 <li>Use a message broker only when you need store-and-forward semantics</li>
 </ul></li>
 </ul>
@@ -82,16 +83,16 @@ and brokers.</p>
 <h2 id="features">Features</h2>
 
 <ul>
-<li>Supports Arbitrary Topology - No restrictions on redundancy</li>
-<li>Automatic Route Computation - Adjusts quickly to changes in topology</li>
-<li>Cost-Based Route Computation</li>
-<li><a href="addressing.html">Rich Addressing Semantics</a></li>
+<li>Supports arbitrary topology - no restrictions on redundancy</li>
+<li>Automatic route computation - adjusts quickly to changes in topology</li>
+<li>Cost-based route computation</li>
+<li><a href="addressing.html">Rich addressing semantics</a></li>
 <li>Security</li>
 </ul>
 
 <h2 id="documentation">Documentation</h2>
 
-<p><i>Coming Soon</i></p>
+<p><em>Coming soon</em></p>
 
       </div>
       <div id="bottom">

Modified: qpid/site/docs/components/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/index.html?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/docs/components/index.html (original)
+++ qpid/site/docs/components/index.html Thu Jul 18 11:46:27 2013
@@ -77,7 +77,7 @@ persistence, and manageability.</p>
 <li><a href="cpp-broker-tools/index.html">C++ broker command-line tools</a>
- Manage the C++ broker</li>
 <li><a href="java-broker/index.html">Java broker</a> - A pure-Java AMQP
message broker</li>
 <li><a href="qmf/index.html">QMF</a> - Management built on Qpid messaging</li>
-<li><a href="dispatch/index.html">Qpid Dispatch Router</a> - An AMQP Router
for scalable messaging interconnect</li>
+<li><a href="dispatch/index.html">Qpid Dispatch router</a> - An AMQP router
for scalable messaging interconnect</li>
 </ul>
 
 <h2 id="compatibility">Compatibility</h2>
@@ -90,12 +90,12 @@ persistence, and manageability.</p>
 <tr><td><a href="http://qpid.apache.org/components/cpp-broker/index.html">C++
broker</a></td><td>C++</td><td>Linux, Windows</td><td>1.0,
0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/cpp-broker-tools/index.html">C++
broker command-line tools</a></td><td>-</td><td>Linux</td><td>0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/java-broker/index.html">Java
broker</a></td><td>Java</td><td>JVM</td><td>1.0,
0-10, 0-91, 0-9, 0-8</td></tr>
+<tr><td><a href="dispatch/index.html">Qpid Dispatch router</a></td><td>C</td><td>Linux</td><td>1.0</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/qpid-jca/index.html">Qpid
JCA</a></td><td>Java</td><td>JVM</td><td>0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/qpid-jms/index.html">Qpid
JMS</a></td><td>Java</td><td>JVM</td><td>1.0, 0-10,
0-91, 0-9, 0-8</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/messaging-api/index.html">Qpid
Messaging API</a></td><td>C++, Perl, Python, Ruby, .NET</td><td>Linux,
Windows</td><td>1.0, 0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/qpid-wcf/index.html">Qpid
WCF</a></td><td>.NET</td><td>Windows</td><td>0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/qmf/index.html">QMF</a></td><td>C++,
Python</td><td>Linux</td><td>0-10</td></tr>
-<tr><td><a href="dispatch/index.html">Qpid Dispatch Router</a></td><td>C</td><td>Linux</td><td>1.0</td></tr>
 </tbody>
 </table>
 

Modified: qpid/site/docs/site.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/site.html?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/docs/site.html (original)
+++ qpid/site/docs/site.html Thu Jul 18 11:46:27 2013
@@ -49,6 +49,15 @@
         <ul id="path-navigation"><li>About This Site</li></ul>
         <h1 id="about-this-site">About This Site</h1>
 
+<h2 id="style-guide">Style guide</h2>
+
+<h3 id="capitalization">Capitalization</h3>
+
+<ul>
+<li>Use initial caps for section and table headings; don't capitalize every word</li>
+<li>Otherwise, capitalize page titles and proper names</li>
+</ul>
+
 <h2 id="colors">Colors</h2>
 
 <div class="spacious">

Modified: qpid/site/input/components/dispatch/addressing.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/dispatch/addressing.md?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/input/components/dispatch/addressing.md (original)
+++ qpid/site/input/components/dispatch/addressing.md Thu Jul 18 11:46:27 2013
@@ -17,54 +17,53 @@
 ;; under the License.
 ;;
 
-# Qpid Dispatch Router - Addressing
+# Qpid Dispatch Addressing
 
 AMQP addresses are used to control the flow of messages across a network of
 routers.  Addresses are used in a number of different places in the AMQP 1.0
-protocol.  They can be used in a specific message in the *to* and *reply-to*
+protocol.  They can be used in a specific message in the `to` and `reply-to`
 fields of a message's properties.  They are also used during the creation of
-links in the *address* field of a *source* or a *target*.
+links in the `address` field of a `source` or a `target`.
 
-## Routing Mechanisms
+## Routing mechanisms
 
 The fact that addresses can be used in different ways suggests that message
 routing can be accomplished in different ways.  Before going into the specifics
 of the different routing mechanisms, it would be good to first define what is
 meant by the term *routing*:
 
-> In a network built of multiple routers connected by connections (i.e. nodes and
+> In a network built of multiple routers connected by connections (i.e., nodes and
 > edges in a graph), *routing* determines which connection to use to send a message
 > directly to its destination or one step closer to its destination.
 
 Each router serves as the terminus of a collection of incoming and outgoing links.
-Some of the links are designated for message-routing and others are designated for
-link-routing.  In both cases, the links either connect directly to endpoints that
-produce and consume messages or they connect to other routers in the network along
+Some of the links are designated for message routing, and others are designated for
+link routing.  In both cases, the links either connect directly to endpoints that
+produce and consume messages, or they connect to other routers in the network along
 previously established connections.
 
-### Message Routing
+### Message routing
 
 Message routing occurs upon delivery of a message and is done based on the address
-in the message's *to* field.
+in the message's `to` field.
 
 When a delivery arrives on an incoming message-routing link, the router extracts the
-address from the delivered message's *to* field and looks the address up in its
+address from the delivered message's `to` field and looks the address up in its
 routing table.  The lookup results in zero or more outgoing links onto which the message
-shall be re-sent.
+shall be resent.
 
   || *Delivery* || *Handling* ||
-  || *pre-settled* || If the arriving delivery is pre-settled (i.e. fire and forget), the
incoming delivery shall be settled by the router and the outgoing deliveries shall also be
pre-settled. In other words, the pre-settled nature of the message delivery is propagated
across the network to the message's destination(s). ||
+  || *pre-settled* || If the arriving delivery is pre-settled (i.e., fire and forget), the
incoming delivery shall be settled by the router, and the outgoing deliveries shall also be
pre-settled. In other words, the pre-settled nature of the message delivery is propagated
across the network to the message's destination. ||
   || *unsettled* || Unsettled delivery is also propagated across the network.  Because unsettled
delivery records cannot be discarded, the router tracks the incoming deliveries and keeps
the association of the incoming deliveries to the resulting outgoing deliveries.  This kept
association allows the router to continue to propagate changes in delivery state (settlement
and disposition) back and forth along the path which the message traveled. ||
 
-
-### Link Routing
+### Link routing
 
 Link routing occurs when a new link is attached to the router across one of its AMQP connections.
-It is done based on the *target.address* field of an inbound link and the *source.address*
field
+It is done based on the `target.address` field of an inbound link and the `source.address`
field
 of an outbound link.
 
-Link routing uses the same routing table that message routing uses.  This difference is that
the
-routing occurs during the link-attach operation and link-attaches are propagated along the
appropriate
+Link routing uses the same routing table that message routing uses.  The difference is that
the
+routing occurs during the link-attach operation, and link attaches are propagated along the
appropriate
 path to the destination.  What results is a chain of links, connected end-to-end, from source
to
 destination.  It is similar to a *virtual circuit* in a telecom system.
 

Modified: qpid/site/input/components/dispatch/index.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/dispatch/index.md?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/input/components/dispatch/index.md (original)
+++ qpid/site/input/components/dispatch/index.md Thu Jul 18 11:46:27 2013
@@ -19,40 +19,41 @@
 
 # Qpid Dispatch Router
 
-A lightweight message router, written in C, built on Qpid Proton, that provides
-flexible and scalable interconnect between AMQP endpoints or between endpoints
+A lightweight message router, written in C and built on
+[Qpid Proton](@site-url@/proton/index.html), that provides flexible
+and scalable interconnect between AMQP endpoints or between endpoints
 and brokers.
 
   || *Platforms* || Linux ||
-  || *Protocols* || AMQP 1.0 ||
-  || *Download* || <i>Coming Soon</i> ||
+  || *AMQP versions* || 1.0 ||
+  || *Download* || *Coming soon* ||
   || *Source location* ||  <http://svn.apache.org/repos/asf/qpid/trunk/qpid/extras/dispatch/>
||
   || *Issues* || [Open bugs](https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+%3D+%22Bug%22+and+status+in+%28%22Open%22%2C+%22Reopened%22%2C+%22In+Progress%22%2C+%22Ready+To+Review%22%29+and+component+%3D+%22Qpid+Dispatch%22),
[Completed enhancements](https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+in+%28%22New+Feature%22%2C+%22Improvement%22%29+and+status+in+%28%22Closed%22%2C+%22Resolved%22%29+and+resolution+%3D+%22Fixed%22+and+component+%3D+%22Qpid+Dispatch%22),
[Requested enhancements](https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+in+%28%22New+Feature%22%2C+%22Improvement%22%29+and+status+in+%28%22Open%22%2C+%22Reopened%22%2C+%22In+Progress%22%2C+%22Ready+To+Review%22%29+and+component+%3D+%22Qpid+Dispatch%22)
||
 
 ## Benefits
 
- - Simplifies Connectivity
+ - Simplifies connectivity
    - An endpoint can do all of its messaging through a single transport connection
-   - Avoid opening holes in Firewalls for incoming connections
- - Simplifies Reliability
-   - Reliability and Availability are provided using redundant topology, not server clustering
-   - Reliable messaging end-to-end without persistent stores
+   - Avoid opening holes in firewalls for incoming connections
+ - Simplifies reliability
+   - Reliability and availability are provided using redundant topology, not server clustering
+   - Reliable end-to-end messaging without persistent stores
    - Use a message broker only when you need store-and-forward semantics
 
 ## Features
 
- - Supports Arbitrary Topology - No restrictions on redundancy
- - Automatic Route Computation - Adjusts quickly to changes in topology
- - Cost-Based Route Computation
- - [Rich Addressing Semantics](addressing.html)
+ - Supports arbitrary topology - no restrictions on redundancy
+ - Automatic route computation - adjusts quickly to changes in topology
+ - Cost-based route computation
+ - [Rich addressing semantics](addressing.html)
  - Security
 
 ## Documentation
 
-<i>Coming Soon</i>
+*Coming soon*
+
 ;;This is the documentation for the current released version.  You can
 ;;find previous versions with our
 ;;[past releases](@site-url@/releases/index.html#past-releases).
 
 ;; - [Deployment and Configuration Guide](@current-dispatch-release-url@/qpid-dispatch-deploy/book/index.html)
-

Modified: qpid/site/input/components/index.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/index.md?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/input/components/index.md (original)
+++ qpid/site/input/components/index.md Thu Jul 18 11:46:27 2013
@@ -44,7 +44,7 @@ persistence, and manageability.
  - [C++ broker command-line tools](cpp-broker-tools/index.html) - Manage the C++ broker
  - [Java broker](java-broker/index.html) - A pure-Java AMQP message broker
  - [QMF](qmf/index.html) - Management built on Qpid messaging
- - [Qpid Dispatch Router](dispatch/index.html) - An AMQP Router for scalable messaging interconnect
+ - [Qpid Dispatch router](dispatch/index.html) - An AMQP router for scalable messaging interconnect
  
 ## Compatibility
 
@@ -54,12 +54,12 @@ persistence, and manageability.
   || [C++ broker](@site-url@/components/cpp-broker/index.html) || C++ || Linux, Windows ||
1.0, 0-10 ||
   || [C++ broker command-line tools](@site-url@/components/cpp-broker-tools/index.html) ||
- || Linux || 0-10 ||
   || [Java broker](@site-url@/components/java-broker/index.html) || Java || JVM || 1.0, 0-10,
0-91, 0-9, 0-8 ||
+  || [Qpid Dispatch router](dispatch/index.html) || C || Linux || 1.0 ||
   || [Qpid JCA](@site-url@/components/qpid-jca/index.html) || Java || JVM || 0-10 ||
   || [Qpid JMS](@site-url@/components/qpid-jms/index.html) || Java || JVM || 1.0, 0-10, 0-91,
0-9, 0-8 ||
   || [Qpid Messaging API](@site-url@/components/messaging-api/index.html) || C++, Perl, Python,
Ruby, .NET || Linux, Windows || 1.0, 0-10 ||
   || [Qpid WCF](@site-url@/components/qpid-wcf/index.html) || .NET || Windows || 0-10 ||
   || [QMF](@site-url@/components/qmf/index.html) || C++, Python || Linux || 0-10 ||
-  || [Qpid Dispatch Router](dispatch/index.html) || C || Linux || 1.0 ||
 
 ;; ## Servers
 

Modified: qpid/site/input/site.md
URL: http://svn.apache.org/viewvc/qpid/site/input/site.md?rev=1504439&r1=1504438&r2=1504439&view=diff
==============================================================================
--- qpid/site/input/site.md (original)
+++ qpid/site/input/site.md Thu Jul 18 11:46:27 2013
@@ -22,6 +22,13 @@
 ;; who maintains it
 ;; code used to produce it
 
+## Style guide
+
+### Capitalization
+
+ - Use initial caps for section and table headings; don't capitalize every word
+ - Otherwise, capitalize page titles and proper names
+
 ## Colors
 
 <div class="spacious">



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org


Mime
View raw message