forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From je...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs faq.xml site.xml
Date Wed, 09 Apr 2003 16:14:54 GMT
jefft       2003/04/09 09:14:53

  Modified:    src/documentation/content/xdocs faq.xml site.xml
  Log:
  - Remove obsolete FAQ entry
  - Update and clean up other entries
  
  Revision  Changes    Path
  1.30      +18 -21    xml-forrest/src/documentation/content/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/faq.xml,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- faq.xml	9 Apr 2003 15:15:20 -0000	1.29
  +++ faq.xml	9 Apr 2003 16:14:53 -0000	1.30
  @@ -13,11 +13,15 @@
         </question>
         <answer>
           <p>
  -          Run &quot;<code>./build.sh docs</code>&quot; to see the documentation
  -          for Forrest.
  +          Run &quot;<code>./build.sh</code>&quot; to generate the documentation
  +          for Forrest, built with Forrest.
             The documentation is generated in the <code>build/site/</code> directory.
             Logfiles are in the <code>build/tmp/context/WEB-INF/logs/</code>
directory.
           </p>
  +        <p>
  +          The <link href="site:your-project">Using Forrest</link> guide provides
  +          further step-by-step assistance in getting started with Forrest.
  +        </p>
         </answer>
       </faq>
   
  @@ -34,18 +38,6 @@
           </p>
         </answer>
       </faq>
  -
  -    <faq id="build_fails_subsequent_builds">
  -      <question>
  -        Why is build docs failing on subsequent builds?
  -      </question>
  -      <answer>
  -        <p>
  -          It is a bug. Workaround: <code>./build.sh clean docs</code> every
time.
  -          There is an entry on the <link href="site:todo">To Do List</link>.
  -        </p>
  -      </answer>
  -    </faq>
     </part>
   
   
  @@ -282,16 +274,21 @@
   
       <faq id="how_can_I_help">
         <question>
  -        How can i help?
  +        How can I help?
         </question>
         <answer>
           <p>
  -          Join the forrest-dev <link href="site:mail-lists">mailing list</link>
  -          and help to discuss it. Read the 
  -          <link href="site:primer">Forrest Primer</link> for an overview.
  -          See the 
  -          <link href="site:todo">To Do List </link> and choose something that
  -          interests you.
  +          Join the forrest-dev <link href="site:mail-lists">mailing list</link>,
  +          and tell us what you'd like to see improved.  We regard all feedback
  +          as valuable, particularly from newcomers&mdash;often, close proximity
  +          blinds software developers to faults that are obvious to everyone
  +          else. Don't be shy!
  +        </p>
  +        <p>
  +          More info on contributing can be found on the <link
  +            href="site:contrib">Contributing to Forrest</link> page.  Its always
  +          a good idea to check the Forrest <link href="site:todo">to do</link>
  +          list before diving in.
           </p>
         </answer>
       </faq>
  
  
  
  1.9       +1 -0      xml-forrest/src/documentation/content/xdocs/site.xml
  
  Index: site.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/site.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- site.xml	11 Feb 2003 16:54:56 -0000	1.8
  +++ site.xml	9 Apr 2003 16:14:53 -0000	1.9
  @@ -83,6 +83,7 @@
           <catalogs href="userdocs/concepts/catalog.html"/>
           <sitemap href="userdocs/concepts/sitemap.html"/>
           <input-modules href="userdocs/concepts/modules.html"/>
  +        <views href="userdocs/concepts/views.html"/>
         </cocoon>
         <forrest href="forrest/"/>
         <xindice href="xindice/"/>
  
  
  

Mime
View raw message