Return-Path: Delivered-To: apmail-forrest-svn-archive@www.apache.org Received: (qmail 64624 invoked from network); 5 Mar 2007 06:32:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Mar 2007 06:32:42 -0000 Received: (qmail 64536 invoked by uid 500); 5 Mar 2007 06:32:51 -0000 Delivered-To: apmail-forrest-svn-archive@forrest.apache.org Received: (qmail 64492 invoked by uid 500); 5 Mar 2007 06:32:51 -0000 Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Forrest Developers List" List-Id: Delivered-To: mailing list svn@forrest.apache.org Received: (qmail 64480 invoked by uid 99); 5 Mar 2007 06:32:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 22:32:50 -0800 X-ASF-Spam-Status: No, hits=-99.5 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 22:32:40 -0800 Received: by eris.apache.org (Postfix, from userid 65534) id F29411A981A; Sun, 4 Mar 2007 22:32:19 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r514566 - in /forrest/trunk/site-author/content/xdocs: ./ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ pluginDocs/ pluginDocs/plugins_0_80/ procedures/release/ versions/ Date: Mon, 05 Mar 2007 06:32:19 -0000 To: svn@forrest.apache.org From: crossley@apache.org X-Mailer: svnmailer-1.1.0 Message-Id: <20070305063219.F29411A981A@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: crossley Date: Sun Mar 4 22:32:17 2007 New Revision: 514566 URL: http://svn.apache.org/viewvc?view=rev&rev=514566 Log: Remove "v0.80" from "site:" references. In the absence of a version qualifier, it will use the first match that it finds in site.xml (i.e. the current version, which is exactly what we want). When we move to the next version of Forrest, these references will now work automatically. This solves a fixme note in the "How_to_release" doc. Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml forrest/trunk/site-author/content/xdocs/howto-dev.xml forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml forrest/trunk/site-author/content/xdocs/site.xml forrest/trunk/site-author/content/xdocs/versions/index.xml forrest/trunk/site-author/content/xdocs/who.xml Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml Sun Mar 4 22:32:17 2007 @@ -103,7 +103,7 @@ content/xdocs/*.xml see the immediate effect.

- The document Using Forrest is + The document Using Forrest is your next step.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml Sun Mar 4 22:32:17 2007 @@ -236,7 +236,7 @@

Other Forrest documentation has some notes about configuring the entity resolver for your own DTDs. See - XML Validation. + XML Validation.

Cocoon has extensive documentation about the entity resolver. See Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml Sun Mar 4 22:32:17 2007 @@ -30,7 +30,7 @@

This is the initial attempt to give focus to the Forrest project. This summary is a loose collection of items from the forrest-dev mailing list. Please add and re-arrange so that it can evolve into a - focus document. The Forrest Primer + focus document. The Forrest Primer provides an overview.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml Sun Mar 4 22:32:17 2007 @@ -33,7 +33,7 @@ Where can I read an overview about how to work with Forrest? -

See the Using Forrest guide.

+

See the Using Forrest guide.

@@ -60,8 +60,8 @@ How can I use SVN to keep up to date with the latest codebase? -

Follow these Building Forrest notes.

-

The Using Forrest guide provides further +

Follow these Building Forrest notes.

+

The Using Forrest guide provides further step-by-step assistance in getting started with Forrest for your project.

@@ -72,7 +72,7 @@ Sometimes one does not want to use the most recent functionality of a plugin and instead need to use an older version. Information about changes to each plugin can be found in its - documentation. + documentation.

In the forrest.properties file, specify the version of the plugin @@ -185,9 +185,9 @@ What tools can be used to edit the content? -

If you are using the Apache Forrest XML document format +

If you are using the Apache Forrest XML document format or DocBook or other XML document types, then you can use any text editor or even a - dedicated XML editor. You must ensure valid XML. See our configuration notes for various editors.

There are content management systems like Apache Lenya.

Remember that Forrest can also use other source formats, such as OpenOffice.org docs or @@ -207,7 +207,7 @@ defining the navigation menus, and as a method for defining references to be used when linking between documents. This file is fully explained in - Menus and Linking. Here is a precis: + Menus and Linking. Here is a precis:

The labels can be whatever text you want. @@ -286,9 +286,9 @@ ... ]]>

In this case the menu labeled "About" will have 2 new items: "Full PDF" and "Full HTML". - (See also How to create a PDF document for each + (See also How to create a PDF document for each tab.)

-

This assumes that you use the site.xml method for your +

This assumes that you use the site.xml method for your site structure and navigation, rather than the old book.xml method.

@@ -379,7 +379,7 @@ I need help with the interaction between tabs.xml and site.xml

- See the tips. + See the tips.

@@ -394,7 +394,7 @@
  • Edit that file to replace 'index.html' in index.html]]> with 'overview.html'.
    • -
  • Edit your project's sitemap.xmap file.
    • +
  • Edit your project's sitemap.xmap file.
  • Add the following code just before the end of the pipelines-element: @@ -415,7 +415,7 @@ start-up-page for a CD-based documentation project to be named 'start.html'.

    To change the start page of a site:

      -
    1. Edit your project's sitemap.xmap file.
      2. +
    2. Edit your project's sitemap.xmap file.
    3. Add the following code just before the end of the pipelines-element: @@ -645,7 +645,7 @@

      If you have:<version>$Revision: 1.30 $</version>The '1.30' will be extracted and displayed at the bottom of the page as "version 1.30". See for example the - bottom of the Using Forrest document.

      + bottom of the Using Forrest document.

      This technique could also be used for a modification date with $Date: 2004/01/15 08:52:47 $

      @@ -678,7 +678,7 @@ ]]>

      This is just an example, and you should modify it appropriately for your site.

      Wildcards may be used. These are a powerful feature of Cocoon's sitemap. For example, foo/* would match + href="site:sitemap-ref">sitemap. For example, foo/* would match foo/bar, but not foo/bar/baz — use foo/** to match that. @@ -762,19 +762,19 @@ How do i configure my favourite XML editor or parser to find the local Forrest DTDs? -

      Notes are provided for various tools at Using Catalog Entity +

      Notes are provided for various tools at Using Catalog Entity Resolver for local DTDs.

      How to make the site look better and change its skin? -

      There are default skins provided, which are configurable +

      There are default skins provided, which are configurable and so should meet the needs of most projects. The aim is to provide many capabilities so that extra skins are not needed.

      -

      See notes about configuration of the skins. +

      See notes about configuration of the skins. Some projects may have special needs and can define their own skin.

      + href="site:your-project/new-skin">own skin.

      @@ -791,7 +791,7 @@ directory (or lib/core/ directory in the source distribution).

    4. Add the following generator definition in the map:generators section of your project sitemap + href="site:project-sitemap">project sitemap

      Menus and + &s;-generated menus aren't appropriate. See Menus and Linking.

      @@ -926,8 +926,8 @@

      The other way is to use the full DocBook stylesheets directly. The DocBook DTDs are shipped with Forrest and automatically handled. However, you will need to have the DocBook stylesheets on your system (they are too massive to ship with Forrest) and configure - Forrest accordingly. You will need to create a project - sitemap as explained in Using Forrest and + Forrest accordingly. You will need to create a project + sitemap as explained in Using Forrest and add matches to handle your DocBook documents. Here is an example. Note that you need to change it to suit your situation. The match must be very specific so that only the DocBook documents are matched. The rest of the documents will be handled by Forrest core. Powerful @@ -960,7 +960,7 @@ html, then uses a Forrest core stylesheet to transform and serialize to the internal xml format, then the normal machinery takes over and does the output transformation. This use the Content Aware Pipelines - (SourceTypeAction) + (SourceTypeAction) to peek at the source xml. If it is DocBook-4.2 then this sitemap match is triggered, if not then it falls through to the core of Forrest.

      @@ -1005,7 +1005,7 @@ "document-v*" DTD and DocBook.

      Ensure that the document type declaration in your XML instance is well specified. Use a public identifier. The DTD will then be properly resolved by Forrest. If you need to use - different DTDs, then see Using Forrest for + different DTDs, then see Using Forrest for configuration guidance.

      Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml Sun Mar 4 22:32:17 2007 @@ -23,7 +23,7 @@ xmlns:xlink="http://www.w3.org/1999/xlink"> - + Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml Sun Mar 4 22:32:17 2007 @@ -218,7 +218,7 @@

      It is beyond the scope of this How-To to give details about how to build your plugins XMap. See the - Sitemap Reference for general + Sitemap Reference for general information. See also Plugin Infrastructure for some hints and tips on creating plugin sitemaps. In addition, as with Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml Sun Mar 4 22:32:17 2007 @@ -52,8 +52,8 @@

    5. Understand how to use the skinconf.xml file to change the appearance of the output documents.
    6. Understand how to create or modify skins by following the - Using Forrest document - (topic "Forrest skins").
      7. + Using Forrest document + (topic "Forrest skins").
      7. Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml Sun Mar 4 22:32:17 2007 @@ -47,7 +47,7 @@
      1. Know how to use a - project sitemap. + project sitemap.
      2. A basic understanding of coocons pipelines and their Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml Sun Mar 4 22:32:17 2007 @@ -46,7 +46,7 @@
        • Understand how to create project-specific sitemaps by following the - Using Forrest document.
          • + Using Forrest document.
        Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml Sun Mar 4 22:32:17 2007 @@ -31,7 +31,7 @@ - Provides instructions about writing documents. Please copy this file to serve as a template for your own document.
        3. -
      3. Generate an ASF mirrors page using interactive web form +
      4. Generate an ASF mirrors page using interactive web form - include html form elements into a forrest-generated html page. For example, this enables building automated download mirror pages for ASF project websites. @@ -48,24 +48,24 @@ users and developers.

          -
        • How to create a PDF document for each tab +
        • How to create a PDF document for each tab - Describes the generation of a PDF document for each group of documents that is defined by a tab.
          • -
        • How to edit Forrest's CSS in a WYSIWYG fashion +
        • How to edit Forrest's CSS in a WYSIWYG fashion - Describes the use of Mozilla Firebird and the free EditCSS-Plugin to customize your Forrest design in a WYSIWYG-way.
          • -
        • How to modify the color of generated corner images +
        • How to modify the color of generated corner images - Describes the use of CSS values from the skinconf.xml configuration file to change the color of the corner images to be suitable for your own skin colors. Advanced use explains editing the *.css too.
          • -
        • How to run Forrest from within Maven +
        • How to run Forrest from within Maven - For Maven users who want to generate their project's documentation and/or website using Forrest in lieu of Maven's site plugin.
          • -
        • How to customize processing of html source +
        • How to customize processing of html source - When integrating legacy html documents into a Forrest-built site, additional processing of the html sources might be required.
          • @@ -75,7 +75,7 @@
          Extending Forrest
            -
          • How to create a Plugin for Forrest +
          • How to create a Plugin for Forrest - Describes how to write a plugin to add new input or output document formats, or to modify the default behaviour of Forrest
          Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml Sun Mar 4 22:32:17 2007 @@ -69,7 +69,7 @@
          &s; is used to generate the menus for the HTML website.
          Indirect linking
          &s; provides a basic aliasing mechanism for linking, e.g. one - can write <link href="site:v0.80//changes"> from anywhere in the site, and + can write <link href="site:changes"> from anywhere in the site, and link to the "changes" information node (translated to changes.html). More on this below.
          @@ -150,7 +150,7 @@ "http://xml.apache.org/commons/resolver/"

        - See another explained example. + See another explained example.

        @@ -357,7 +357,7 @@ is present in the linked-to directory. How do I fix this? A: In &t; use @href instead of @dir attribute and omit the trailing '/'. Which file to serve is then a concern of the sitemap. - See more at the FAQ. + See more at the FAQ.
        5. @@ -425,7 +425,7 @@ Indirect linking

        Forrest's solution is simple: instead of <a href="todo.html">, - write <a href="site:v0.80//todo"> where: + write <a href="site:todo"> where:

        site
        @@ -448,7 +448,7 @@ Resolving site: URIs

        - So how does "site:v0.80//todo" get resolved? A full answer + So how does "site:todo" get resolved? A full answer is provided in the implementation section. Essentially, the "todo" part has "/site//" prepended, and "/@href" appended, to @@ -468,7 +468,7 @@

        Notice that the "//" allows us any degree of specificity when linking. - In the sample &s; above, both "site:v0.80//new_content_type" and + In the sample &s; above, both "site:new_content_type" and "site:about/your-project/new_content_type" identify the same node. It is up to you to decide how specific to make links. One nice benefit of link "ambiguity" is that &s; can be reorganized @@ -519,7 +519,7 @@

        Theory: source URIs

        - The "site:" URIs like "site:v0.80//todo" are examples of + The "site:" URIs like "site:todo" are examples of "source" URIs, in contrast to the more usual foo.html style URIs, which we here call "destination" URIs. This introduces an important concept: that @@ -606,9 +606,9 @@

        Implementation

        Full details on the implementation of - link rewriting and - menu generation are available in - the Sitemap Reference

        + link rewriting and + menu generation are available in + the Sitemap Reference

        Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml Sun Mar 4 22:32:17 2007 @@ -432,7 +432,7 @@ them to start contributing to Forrest. We have a decent generation system for static project documentation, a nice set of skins and some simple but effective DTDs. Our goals however are much more ambitious: we have compiled a - dream list that lists most of them.

        + dream list that lists most of them.

        • Our first ambition is to support the project site generation and maintenance of other Apache projects in an automated manner, starting with our Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml Sun Mar 4 22:32:17 2007 @@ -36,7 +36,7 @@ and related component documentation. The Forrest sitemap is broken into multiple files. The main one is sitemap.xmap which delegates to others. See the - Sitemap Reference for a tour of the + Sitemap Reference for a tour of the default sitemap.
        @@ -71,9 +71,9 @@ Adding a new content type

        See the section "Advanced customizations: sitemap.xmap" in - the Using Forrest document + the Using Forrest document and then follow the - Example: + Example: Adding a new content type.

        Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml Sun Mar 4 22:32:17 2007 @@ -60,7 +60,7 @@ is not handled, passes through to be handled by the default Forrest sitemaps - obviously extremely powerful. The capability is described in - "Using project sitemaps". + "Using project sitemaps".

        @@ -102,7 +102,7 @@ linkmap.xmap Defines a mapping from abstract ("site:index") to physical ("index.html") links for the current page. See - Menus and Linking for a conceptual + Menus and Linking for a conceptual overview, and the Link rewriting section for technical details. @@ -126,7 +126,7 @@ status.xmap - Generates changes and + Generates changes and todo pages from a single status.xml in the project root. @@ -151,7 +151,7 @@ Clark's DTD Parser. Useful for documenting DTD-based XML schemas, such - as Forrest's own DTDs. + as Forrest's own DTDs. @@ -218,7 +218,7 @@ Most of the usual Source pipelines are defined in forrest.xmap which is the default (fallback) handler for **.xml pages. The forrest.xmap uses the - SourceTypeAction to determine the type of XML + SourceTypeAction to determine the type of XML it is processing, and converts it to document-v13 if necessary.

        For instance, say we are rendering a @@ -500,7 +500,7 @@ ]]>

        Meaning that it is defined in the menu.xmap file. In there we find the real definition, which is quite complicated, because there are three - supported menu systems (see menus and + supported menu systems (see menus and linking). We will not go through the sitemap itself (menu.xmap), but will instead describe the logical steps involved:

          @@ -508,7 +508,7 @@ root-relative.

        1. Depending on the forrest.menu-scheme property, we now apply one of the two algorithms for choosing a set of menu links - (described in menu + (described in menu generation):

          • @@ -574,7 +574,7 @@ "linkrewriter" transformer in action. For example:

            ]]>

            This statement is Cocoon's linking system in action. A full - description is provided in Menus and + description is provided in Menus and Linking. Here we describe the implementation of linking.

            Cocoon foundations: Input Modules Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml Sun Mar 4 22:32:17 2007 @@ -30,7 +30,7 @@

            Note that the new Dispatcher capability will be a better solution. - See Status of Themes: Skins and Dispatcher. + See Status of Themes: Skins and Dispatcher.

            Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml Sun Mar 4 22:32:17 2007 @@ -26,7 +26,7 @@ This is the development version of Apache Forrest which can be obtained from the Subversion repository or from a code snapshot. -See the notes for obtaining and Building Forrest. +See the notes for obtaining and Building Forrest.

            This page describes some changes to Apache Forrest that affect people who are @@ -57,7 +57,7 @@

            Many new initial plugins are in the "whiteboard". See the entries in the change log and see each plugin's documentation and changes log. This includes the new Dispatcher. - See Status of Themes: Skins and Dispatcher. + See Status of Themes: Skins and Dispatcher.

            Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml Sun Mar 4 22:32:17 2007 @@ -98,7 +98,7 @@ forrest/main/webapp/resources/schema/catalog.xcat as a means of associating public identifiers (e.g. -//APACHE//DTD Documentation V1.1//EN above) with DTDs. - If you add a new content type, you + If you add a new content type, you should add the DTD to ${project.schema-dir}/dtd/ and add an entry to the ${project.schema-dir}/catalog.xcat file. This section describes the details of this process. @@ -110,7 +110,7 @@ The main Forrest DTDs are designed to be modular and extensible, so it is fairly easy to create a new document type that is a superset of one from Forrest. This is what we'll demonstrate here, using our - earlier download format + earlier download format as an example. Our download format adds a group of new elements to the standard 'documentv13' format. Our new elements are described by the following DTD: @@ -342,7 +342,7 @@ it know where the Forrest catalog file is, and you will be able to validate any Forrest XML file, regardless of location, as you edit your files. See the - configuration notes your favourite + configuration notes your favourite editor.

            Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml (original) +++ forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml Sun Mar 4 22:32:17 2007 @@ -38,7 +38,7 @@ Download the latest release of Forrest and follow the index.html in the top-level, or if you want to try the development version, then - build Forrest from source. + build Forrest from source.

            @@ -599,7 +599,7 @@ site.xml file. This site.xml is like a site index, and is rendered as the vertical column of links in the default skin. Look at Forrest's own xdocs for an example. More detailed info about site.xml is provided in - the document Menus and Linking. + the document Menus and Linking.

            @@ -608,7 +608,7 @@ The tabs.xml file is used to produce the 'tabs'. which enable users to quickly jump to sections of your site. See the - menu generation documentation + menu generation documentation for more details, and again, consult Forrest's own docs for a usage example.

            @@ -692,7 +692,7 @@ is not handled, passes through to be handled by the default Forrest sitemaps - obviously extremely powerful. The capability is described in - "Using project sitemaps" + "Using project sitemaps" and some worked examples are shown in the following sections here.

            @@ -702,7 +702,7 @@ and related component documentation. The Forrest sitemap is broken into multiple files. The main one is sitemap.xmap which delegates to others. See the - Sitemap Reference for a tour of the + Sitemap Reference for a tour of the default sitemap.
            @@ -819,7 +819,7 @@ structure into the Forrest intermediate xdocs structure.

            - The Sitemap + The Sitemap Reference provides details about how the sitemap works.

            @@ -856,7 +856,7 @@ By default, Forrest requires that all XML files be valid, i.e. they must have a DOCTYPE declaration and associated DTD, and validate against it. Our new 'downloads' document type is no - exception. The XML + exception. The XML Validation document continues this example, showing how to register a new document type. Briefly, this involves:

            @@ -870,7 +870,7 @@
          • Tell the system about your catalog.
          - Please see XML Validation + Please see XML Validation for the complete description for those steps. @@ -886,7 +886,7 @@

          We need to digress and explain the powerful - SourceTypeAction (content aware pipelines). + SourceTypeAction (content aware pipelines). It is a Cocoon sitemap component that peeks at the top-part of a document to look for hints about the type of the document. It has four methods: document-declaration, document-element and @@ -947,7 +947,7 @@ This is the type of processing that happens in the main main/webapp/forrest.xmap sitemap. We have added similar handling to our project sitemap. Basically, this - uses the SourceTypeAction (content aware pipelines) + uses the SourceTypeAction (content aware pipelines) to detect the doctype. The new document-v11.dtd needs to be also added to your project Catalog as described above. @@ -1008,7 +1008,7 @@

          Forrest supplies a collection of - default skins which are configurable + default skins which are configurable and so should meet the needs of most projects. The aim is to provide many capabilities so that extra skins are not needed. @@ -1094,7 +1094,7 @@ In comparison to simpler tools (like Anakia) the Cocoon command-line mode (and hence Forrest command-line mode) is slow. - As the dream list notes, Forrest was + As the dream list notes, Forrest was originally intended to be used for dynamic sites, and the Cocoon crawler used only to create static snapshots for mirroring. This section describes how, by using Modified: forrest/trunk/site-author/content/xdocs/howto-dev.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/howto-dev.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/howto-dev.xml (original) +++ forrest/trunk/site-author/content/xdocs/howto-dev.xml Sun Mar 4 22:32:17 2007 @@ -69,12 +69,12 @@ You have achieved the basic level of using Forrest. You have Forrest installed and can create a new site with 'forrest seed'. You have followed at least the first parts of the - Using Forrest + Using Forrest document.
        2. You will enventually see that understanding of the Cocoon - sitemap + sitemap is important. For the initial examples below, you can do without that. However please explore the sitemap soon.
          3. @@ -147,7 +147,7 @@

          To get started, see the - instructions + instructions for obtaining the Apache Forrest sources via SVN.

          @@ -284,7 +284,7 @@ Editing content

          See the - FAQ. + FAQ. Basically any editor can be used, because Forrest treats the editing of content as a separate concern. Be sure to configure the editor to find local copies of DTDs. @@ -377,11 +377,11 @@ The Cocoon sitemap is essential for Forrest developers. See some introductions ....

            -
          • Forrest sitemap reference.
            • +
          • Forrest sitemap reference.
          • Introduction to Pipelines in this - How-to.
            • + How-to.
          • About - Forrest project sitemaps.
            • + Forrest project sitemaps.
          • Cocoon concepts.
          • Cocoon sitemap.
          • Cocoon protocols, i.e. cocoon:/ and @@ -403,7 +403,7 @@ the "logkit.xconf" in webapp/WEB-INF and raise the level of some loggers to WARN.

            - This FAQ + This FAQ describes the location of the Cocoon logfiles and their configuration.

            @@ -547,7 +547,7 @@

            Do 'forrest site' to produce the whole documentation set. Cocoon will report its progress and reveal any problems. - This FAQ + This FAQ explains the messages that Cocoon sends to standard output. Broken links are also reported to a special file, which also shows the source file containing the break. The location Modified: forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml (original) +++ forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml Sun Mar 4 22:32:17 2007 @@ -26,7 +26,7 @@

            • 0.7 - the current release
              • -
            • 0.8-dev - the current development version
              • +
            • 0.8-dev - the current development version
            Modified: forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml (original) +++ forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml Sun Mar 4 22:32:17 2007 @@ -295,7 +295,7 @@
            Further Reading

            If you want to build a plugin you might like to start with our - HowTo on Building Plugins.

            + HowTo on Building Plugins.

            Modified: forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml (original) +++ forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml Sun Mar 4 22:32:17 2007 @@ -217,7 +217,7 @@ Further Reading Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml (original) +++ forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml Sun Mar 4 22:32:17 2007 @@ -261,7 +261,7 @@ - + @@ -272,7 +272,7 @@ - + @@ -285,19 +285,6 @@

            Remove the past versions (0.6) docs directory by doing 'svn rm site-author/content/xdocs/docs_0_60

            Do we also remove the generated docs from forrest/site/docs_0_60 SVN? This also removes it from the website. -
            • -
          • -

            Adjust version-numbers in site.xml

            - This used to be the comment: 'Do global replace throughout docs_0_80 to replace the string - ="site:v0.70 with ="site:v0.80' but this needs checking. - Perhaps you are talking about something else. - I meant that when we copy the docs to become the next -dev (i.e. - this time docs_0_90) then we need to replace all "site:" references - (i.e. ="site:v0.80 with ="site:v0.90'). If you can see a better way, then great. - Maybe dropping the v0.x prefix will cause it to use the most recent doc, - e.g. use site:buildPlugin rather than site:v0.90/howto/buildplugin. - -
          • Modified: forrest/trunk/site-author/content/xdocs/site.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/site.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/site.xml (original) +++ forrest/trunk/site-author/content/xdocs/site.xml Sun Mar 4 22:32:17 2007 @@ -221,14 +221,14 @@ - + - + Modified: forrest/trunk/site-author/content/xdocs/versions/index.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/versions/index.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/versions/index.xml (original) +++ forrest/trunk/site-author/content/xdocs/versions/index.xml Sun Mar 4 22:32:17 2007 @@ -27,7 +27,7 @@
            • 0.6 - the past release
            • 0.7 - the current release
              • -
            • 0.8-dev - the current development version
              • +
            • 0.8-dev - the current development version
            Modified: forrest/trunk/site-author/content/xdocs/who.xml URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/who.xml?view=diff&rev=514566&r1=514565&r2=514566 ============================================================================== --- forrest/trunk/site-author/content/xdocs/who.xml (original) +++ forrest/trunk/site-author/content/xdocs/who.xml Sun Mar 4 22:32:17 2007 @@ -31,7 +31,7 @@ Of course the committers are not the only people involved in the community. Thanks to the many people for their contributions of patches, assistance, ideas, and email discussion. - Some are mentioned at the changes page. + Some are mentioned at the changes page. See how we acknowledge contributions.