svn commit: r1053534 - /forrest/trunk/site-author/content/xdocs/index.xml

[email protected]
Newsgroups gmane.text.xml.forrest.cvs
Message-ID <[email protected]>
Author: crossley
Date: Wed Dec 29 05:43:38 2010
New Revision: 1053534

URL: http://svn.apache.org/viewvc?rev=1053534&view=rev
Log:
Use the "Documentation V2.0 DTD" for home page.

Modified:
    forrest/trunk/site-author/content/xdocs/index.xml

Modified: forrest/trunk/site-author/content/xdocs/index.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?rev=1053534&r1=1053533&r2=1053534&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/index.xml (original)
+++ forrest/trunk/site-author/content/xdocs/index.xml Wed Dec 29 05:43:38 2010
@@ -15,7 +15,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://forrest.apache.org/dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
 <document>
   <header>
     <title>Welcome to Apache Forrest</title>
@@ -32,14 +32,14 @@
   <body>
     <p>
       The Apache Forrest project uses the opensource
-      <link href="site:license">Apache License 2.0</link> and adheres to
-      <link href="site:way">open development</link> ideals.
-      We are part of the Apache Software Foundation (<link href="ext:asf">ASF</link>).
+      <a href="site:license">Apache License 2.0</a> and adheres to
+      <a href="site:way">open development</a> ideals.
+      We are part of the Apache Software Foundation (<a href="ext:asf">ASF</a>).
     </p>
     <note>
       Please realise that Forrest is still pre-1.0 release version. It is
       certainly usable for those who are prepared to move with it. See more
-      notes about <link href="#status">status</link> below.
+      notes about <a href="#status">status</a> below.
     </note>
     <section>
       <title>Explanation and features</title>
@@ -62,7 +62,7 @@
           can be developed.</li>
         <li><strong>Step 5</strong>: For more information about installation
           and use, see the
-          <link href="site:your-project">Using Forrest</link> guide.
+          <a href="site:your-project">Using Forrest</a> guide.
         </li>
       </ul>
 <!-- FIXME: Needs review for 0.9  -->
@@ -75,7 +75,7 @@
         will be retrieved from your local installation. In all cases once a
         plugin has been installed locally there is no need for Forrest to access
         the Internet. For more information see the
-        <link href="site:pluginVersions/overview">plugins documentation</link>.
+        <a href="site:pluginVersions/overview">plugins documentation</a>.
       </note>
       <p>
         Forrest's focus on low "startup cost" makes it ideal for rapid
@@ -97,36 +97,36 @@
       <p>
         Forrest is far from a quick and dirty solution however. Forrest is built
         on the world's leading XML application framework,
-        <link href="ext:cocoon">Apache Cocoon</link>, which provides advanced
+        <a href="ext:cocoon">Apache Cocoon</a>, which provides advanced
         users with extremely powerful publishing capabilities.
       </p>
       <ul>
         <li>Multiple task-specific source XML formats can be used
-            (<link href="site:write-howto">How-To</link>,
-          <link href="site:faq">
+            (<a href="site:write-howto">How-To</a>,
+          <a href="site:faq">
           <acronym title="Frequently Asked
-              Questions">FAQ</acronym></link>,
-          <link href="site:changes">changelogs</link> and
-          <link href="site:todo">todo lists</link> supported natively).
+              Questions">FAQ</acronym></a>,
+          <a href="site:changes">changelogs</a> and
+          <a href="site:todo">todo lists</a> supported natively).
           Source formats include: Apache xdocs xml format, plain html
           documents, some Wiki formats, a subset of DocBook, ...
         </li>
         <li>Multiple output formats supported, for example HTML and PDF (using
-          <link href="ext:fop">Apache FOP</link>).
+          <a href="ext:fop">Apache FOP</a>).
         </li>
-        <li>SVG to PNG rendering (using <link href="ext:batik">Apache
-            Batik</link>). Simply drop the SVG in the appropriate directory
+        <li>SVG to PNG rendering (using <a href="ext:batik">Apache
+            Batik</a>). Simply drop the SVG in the appropriate directory
             and it will be rendered as PNG.</li>
         <li>
           Transparent inclusion and aggregation of external content, like
-          <link href="site:changes-rss">RSS feeds</link>.
+          <a href="site:changes-rss">RSS feeds</a>.
         </li>
         <li>
           Anything else possible with the
-          <link href="ext:cocoon/sitemap">Cocoon sitemap</link>.  Using database
-          queries, <link href="ext:apache-stats">charting</link>, web services
+          <a href="ext:cocoon/sitemap">Cocoon sitemap</a>.  Using database
+          queries, <a href="ext:apache-stats">charting</a>, web services
           integration; the possibilities are constantly growing as Cocoon grows.
-          See the <link href="ext:cocoon/features">Cocoon Features</link> list
+          See the <a href="ext:cocoon/features">Cocoon Features</a> list
           for the full suite of capabilities.
         </li>
         <li>
@@ -149,8 +149,8 @@
       <p>
         Running as a webapp has a major advantage during development: content
         can be written, and then the rendered output viewed almost instantly in
-        a web browser. This <link href="site:your-project/webapp">webapp
-        technique</link> enables Forrest's edit/review cycle to be faster than
+        a web browser. This <a href="site:your-project/webapp">webapp
+        technique</a> enables Forrest's edit/review cycle to be faster than
         command-line transformation tools.
       </p>
     </section>
@@ -159,17 +159,17 @@
       <p>
         Apache Forrest was started in January 2002, with the major use-case
         being to create a consistent and efficient
-        <link href="http://xml.apache.org/">xml.apache.org</link> group of
+        <a href="http://xml.apache.org/">xml.apache.org</a> group of
         project websites with a uniform, lightweight, easy-to-navigate layout
         and structure. In addition, Forrest was to be a Sourceforge-like project
-        management tool, complementing <link href="ext:gump">Apache Gump</link>
+        management tool, complementing <a href="ext:gump">Apache Gump</a>
         (hence the name 'Forrest').
         See the Apache XML and Apache Cocoon mail lists around end 2001 (e.g.
-        <link href="http://mail-archives.apache.org/mod_mbox/xml-general/200112.mbox/%[email protected]%3E">here</link>
+        <a href="http://mail-archives.apache.org/mod_mbox/xml-general/200112.mbox/%[email protected]%3E">here</a>
         and
-        <link href="http://mail-archives.apache.org/mod_mbox/xml-general/200112.mbox/%[email protected]%3E">here</link> /
-        <link href="http://mail-archives.apache.org/mod_mbox/cocoon-dev/200112.mbox/%[email protected]%3E">here</link>).
-        Forrest <link href="site:guidelines/pmc">became</link> a top-level project
+        <a href="http://mail-archives.apache.org/mod_mbox/xml-general/200112.mbox/%[email protected]%3E">here</a> /
+        <a href="http://mail-archives.apache.org/mod_mbox/cocoon-dev/200112.mbox/%[email protected]%3E">here</a>).
+        Forrest <a href="site:guidelines/pmc">became</a> a top-level project
         in May 2004.
       </p>
       <p>
@@ -180,8 +180,8 @@
       <p>
         Apache Forrest is currently progressing rapidly through a series of 0.x
         releases. It is certainly usable now (despite not yet being version
-        1.x). See the growing list of <link href="site:live-sites">example
-        sites</link> including many Apache sites.
+        1.x). See the growing list of <a href="site:live-sites">example
+        sites</a> including many Apache sites.
       </p>
       <p>
         In general, prior to 1.0, ensuring quality of design will be considered
@@ -198,27 +198,27 @@
         releases. All versions of Forrest include their own copy of the
         documentation. There is also documentation for each plugin and the
         forrest seed site contains further examples and documentation (see
-        <link href="site:faq/docs">FAQ</link>).
+        <a href="site:faq/docs">FAQ</a>).
       </p>
     </section>
     <section id="news">
       <title>News and events</title>
       <p>
-        See the <link href="site:events">events</link> list for more detail.
+        See the <a href="site:events">events</a> list for more detail.
       </p>
       <ul>
 <!--
         <li>
-         <link href="http://apachecon.com/">
+         <a href="http://apachecon.com/">
            <img src="http://apache.org/images/ac2005eu_135x50.gif"
              alt="ApacheCon Europe 2005" width="135" height="50"/>
-         </link>
+         </a>
          
-         <link href="http://apachecon.com/2006/EU/">ApacheCon EU 2006</link>
+         <a href="http://apachecon.com/2006/EU/">ApacheCon EU 2006</a>
          - Please make plans to join us for the conference in
          Dublin, Ireland on 26-30 June 2006.
 
-         See our <link href="site:events">events</link> list for the schedule
+         See our <a href="site:events">events</a> list for the schedule
          of Forrest meetings at ApacheCon.
         </li>
 -->
@@ -239,7 +239,7 @@
       <p>
         As with all Apache projects, Forrest is a meritocracy; the more you put
         in, the more you get to define the project's future. See the
-        <link href="site:contrib">"contributing"</link> page for more
+        <a href="site:contrib">"contributing"</a> page for more
         information.
 
       </p>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.