Return-Path: X-Original-To: apmail-cocoon-cvs-archive@www.apache.org Delivered-To: apmail-cocoon-cvs-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8189399FC for ; Tue, 10 Apr 2012 10:25:18 +0000 (UTC) Received: (qmail 3014 invoked by uid 500); 10 Apr 2012 10:25:18 -0000 Delivered-To: apmail-cocoon-cvs-archive@cocoon.apache.org Received: (qmail 2934 invoked by uid 500); 10 Apr 2012 10:25:18 -0000 Mailing-List: contact cvs-help@cocoon.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@cocoon.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list cvs@cocoon.apache.org Received: (qmail 2927 invoked by uid 99); 10 Apr 2012 10:25:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2012 10:25:18 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2012 10:25:13 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 13E442388A3F for ; Tue, 10 Apr 2012 10:24:53 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r1311666 [3/12] - in /cocoon/site/site: ./ css/ images/ js/ Date: Tue, 10 Apr 2012 10:24:49 -0000 To: cvs@cocoon.apache.org From: ilgrosso@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120410102453.13E442388A3F@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: cocoon/site/site/1273_1_1.html URL: http://svn.apache.org/viewvc/cocoon/site/site/1273_1_1.html?rev=1311666&r1=1311665&r2=1311666&view=diff ============================================================================== --- cocoon/site/site/1273_1_1.html (original) +++ cocoon/site/site/1273_1_1.html Tue Apr 10 10:24:47 2012 @@ -29,17 +29,13 @@ Cocoon Main Site - How to contribute? - + - - - + + + - +

Apache » Cocoon »

@@ -74,7 +70,7 @@
  • Core 2.2
  • Blocks 2.2
  • Maven Plugins 2.2
    • -
  • Cocoon 3.0 [alpha]
    • +
  • Cocoon 3.0
  • Subprojects
    • @@ -89,7 +85,7 @@
  • - Getting started + Getting Started
    • @@ -159,7 +153,7 @@
  • - Getting better + Getting Better
    • @@ -247,10 +231,6 @@ - - - -
  • Project Information @@ -259,7 +239,7 @@
  • Versions
    -

    How to contribute?

    Code

    TBD

    General documentation

    These instructions only work if you have an active account in our Daisy CMS + +

    How to contribute?

    Code

    TBD

    General documentation

    These instructions only work if you have an active account in our Daisy CMS and got the doc editor role assigned. If you haven't, create your account at -http://cocoon.zones.apache.org/daisy/registration -and ask at dev[_at_]cocoon.apache.org for editing rights.

    Note: Doc editors are not allowed to publish a document. This can only -be done by Apache Cocoon committers.

    Editing a document

    Simply follow the "Edit" link at the bottom of a page, login in and select -Page Actions - Edit from the menu.

    Adding a document

    Go to http://cocoon.zones.apache.org/daisy/, login and select the -documentation site where you want to add your new document. Select New -Document from the menu. The recommended document type is Cocoon -document.

    +http://cocoon.zones.apache.org/daisy/registration +and ask at dev[_at_]cocoon.apache.org for editing rights.

    Note: Doc editors are not allowed to publish a document. This can only +be done by Apache Cocoon committers.

    Editing a document

    Simply follow the "Edit" link at the bottom of a page, login in and select +Page Actions - Edit from the menu.

    Adding a document

    Go to http://cocoon.zones.apache.org/daisy/, login and select the +documentation site where you want to add your new document. Select New +Document from the menu. The recommended document type is Cocoon +document.
    If you want to make your new document appear in a navigation menu, click on -Go to navigation document below the navigation menu and select -Page Actions - Edit.

    What happens once I've added or edited a document?

    The moment you submit a new or changed document an email is sent to docs at -cocoon dot apache dot org.  An entry is also added to the list on the Daisy -Cocoon Site Overview page.  A Cocoon committer should -then see the change, review it and make it live.

    Sitemap component documentation

    For documenting sitemap components, we use a system whereby certain parts of +Go to navigation document below the navigation menu and select +Page Actions - Edit.

    What happens once I've added or edited a document?

    The moment you submit a new or changed document an email is sent to docs at +cocoon dot apache dot org.  An entry is also added to the list on the Daisy +Cocoon Site Overview page.  A Cocoon committer should +then see the change, review it and make it live.

    Sitemap component documentation

    For documenting sitemap components, we use a system whereby certain parts of the documentation are extracted automatically from the Java sources using a tool called sitemaptags2daisy.

    If you are not a committer, make sure that you have checked out the latest version of the Java source file from SVN, make your changes and create a patch -file. Create a new patch issue in JIRA and add your diff file.

    Editing the documentation of a sitemap component

    Only edit the content of the the Long Description part in Daisy. The short +file. Create a new patch issue in JIRA and add your diff file.

    Editing the documentation of a sitemap component

    Only edit the content of the the Long Description part in Daisy. The short description and the value of the fields are automatically assigned from the Java sources, so if you change them in Daisy, these changes will get overwritten the -next time the sitemaptags2daisy tool is run.

    Adding documentation for a new sitemap component

    If running the sitemaptags2daisy tool is not an option (no time, no +next time the sitemaptags2daisy tool is run.

    Adding documentation for a new sitemap component

    If running the sitemaptags2daisy tool is not an option (no time, no privileges, ...) then create manually a document of type "Sitemap Component". In the JavaClass field, enter the fully qualified name of the implementation class. Leave the other fields and the Short Description part empty, they will be assigned the next time the sitemaptags2daisy tool runs. Enter the documentation -in the Long Description part.

    Adding javadoc tags

    The following special javadoc tags are supported (none of these are strictly +in the Long Description part.

    Adding javadoc tags

    The following special javadoc tags are supported (none of these are strictly required by the sitemaptags2daisy tool):

      -
    • @cocoon.sitemap.component.name

      +
    • @cocoon.sitemap.component.name
      default name with which this component is declared in the sitemap
      • -
    • @cocoon.sitemap.component.documentation.disabled

      +
    • @cocoon.sitemap.component.documentation.disabled
      excludes the component from the documentation
      • -
    • @cocoon.sitemap.component.documentation

      +
    • @cocoon.sitemap.component.documentation
      A short (one-paragraph) description of the component. Can contain HTML markup (preferably only inline tags).
      • -
    • @cocoon.sitemap.component.documentation.caching

      +
    • @cocoon.sitemap.component.documentation.caching
      A comment about the caching of this component. The cacheability of the component is figured out automatially by its implemented interfaces, but this tag allows to provide a short comment on the chaching conditions. This is mapped to a field in Daisy, thus should not contain HTML markup.
    Next to these, the @deprecated tag is also synced with the Daisy document. -

    Running the sitemaptags2daisy tool

    TODO, see the README.txt in the sources for now.
    Errors and Improvements? If you see any errors or potential improvements in this document please help - us: View, Edit or comment on the latest development version (registration required). -
    +

    Running the sitemaptags2daisy tool

    TODO, see the README.txt in the sources for now.
    +
    - + \ No newline at end of file Modified: cocoon/site/site/1275_1_1.html URL: http://svn.apache.org/viewvc/cocoon/site/site/1275_1_1.html?rev=1311666&r1=1311665&r2=1311666&view=diff ============================================================================== --- cocoon/site/site/1275_1_1.html (original) +++ cocoon/site/site/1275_1_1.html Tue Apr 10 10:24:47 2012 @@ -29,17 +29,13 @@ Cocoon Main Site - Communication tools that we use - + - - - + + + - +

    Apache » Cocoon »

    @@ -74,7 +70,7 @@
  • Core 2.2
  • Blocks 2.2
  • Maven Plugins 2.2
    • -
  • Cocoon 3.0 [alpha]
    • +
  • Cocoon 3.0
  • Subprojects
    • @@ -89,7 +85,7 @@
  • - Getting started + Getting Started
    • @@ -159,7 +153,7 @@
  • - Getting better + Getting Better
    • @@ -247,10 +231,6 @@ - - - -
  • Project Information @@ -259,7 +239,7 @@
  • Versions
    -

    Communication tools that we use

    Mailing lists

    See below for descriptions of the Cocon mailing lists. A list of all + +

    Communication tools that we use

    Mailing lists

    See below for descriptions of the Cocon mailing lists. A list of all available lists as well as links is available a the -overview page.

    When posting, please observe common-sense netiquette when posting.  In +overview page.

    When posting, please observe common-sense netiquette when posting.  In particular:

    • When replying, please -edit the +edit the original message and include only enough to establish context, not the entire message.
      • -
    • Don't crosspost to the user and developer lists.  The developers also read +
    • Don't crosspost to the user and developer lists.  The developers also read the users list.
    • Only reply to a message if you are really posting a reply on that thread; don't use your mailer's "Reply" function as a shortcut to get the list address -into the "To:" field.  Instead, use your mailer's "new message" function to -start a fresh thread.  When people abuse "Reply" and just change the "Subject:" +into the "To:" field.  Instead, use your mailer's "new message" function to +start a fresh thread.  When people abuse "Reply" and just change the "Subject:" line to a new topic, it makes it harder for threaded mailreaders to display the -subjects accurately.  This can make it less likely that your message will be +subjects accurately.  This can make it less likely that your message will be seen and replied to.
    Regarding content:
      -
    • Please ask your questions on the list.  If someone helps you out, don't -email them off-list to ask your next question.  You will get the best answers if +
    • Please ask your questions on the list.  If someone helps you out, don't +email them off-list to ask your next question.  You will get the best answers if you stay on-list, and that way the question and answers can also benefit the current and future community.
    • When asking for help, don't forget to include:
      • @@ -303,100 +299,104 @@ are working with
    • Don't just say that something "doesn't work"; explain (a) exactly what you did; (b) what you expected to happen; and (c) what happened instead of what you -expected.  That type of explanation gives people a lot more information to work +expected.  That type of explanation gives people a lot more information to work with.
    • If you can show that you at least made some effort to figure something out, -you will in turn get a more helpful response.  In particular, if you have in +you will in turn get a more helpful response.  In particular, if you have in mind some idea that might help and it is an easy thing to try, don't post to the -list to ask "Can I....".  Just try it for yourself and see! :-)
      • +list to ask "Can I....".  Just try it for yourself and see! :-)
    • A very common response to user questions is "What are you trying to -accomplish"?  Try to supply that information when you first ask the question, -and you will get a definitive answer that much sooner.  Cocoon is a rich +accomplish"?  Try to supply that information when you first ask the question, +and you will get a definitive answer that much sooner.  Cocoon is a rich framework that gives you a lot of tools, so that it's not always obvious to new -users which tool set is the best to use for a particular problem.  New users +users which tool set is the best to use for a particular problem.  New users sometimes get wrapped around the axle on some detail of the solution they are trying to make for a given scenario, and then end up posting to the list to ask -how to do some exotic or bizarre thing.  If you can take a step back and +how to do some exotic or bizarre thing.  If you can take a step back and describe the scenario itself, the more experienced users may be able to suggest one or more simpler solutions.
    • If you ask for help with something, and then you later figure it out for yourself, please follow up on the list and describe what you did to fix the -problem.  We like to prepend "SOLVED: " to the Subject: line when doing this. +problem.  We like to prepend "SOLVED: " to the Subject: line when doing this.
    • If you feel you must say "Please reply to me off-list, since I'm not subscribed", you can certainly do that; you just may or may not get a helpful -reply!  You'll almost certainly get better results if you let people repond -on-list.  See the Gmane links below to learn how easy it is to read the Cocoon +reply!  You'll almost certainly get better results if you let people repond +on-list.  See the Gmane links below to learn how easy it is to read the Cocoon lists without subscribing your own email address.
      • -

    User list

    This is the general community help list and for Cocoon.  Use it to learn -Cocoon stuff, and share your own knowledge with somebody else!  Don't forget to -check the FAQ first.  Also, this list is not really the place to ask questions -about XSLT, HTML, CSS, Java programming, etc.  Please consult the +

    User list

    This is the general community help list and for Cocoon.  Use it to learn +Cocoon stuff, and share your own knowledge with somebody else!  Don't forget to +check the FAQ first.  Also, this list is not really the place to ask questions +about XSLT, HTML, CSS, Java programming, etc.  Please consult the Related Resources page to find the right forum for -asking those kinds of questions.Of course, new Cocoon releases are announced on this list.

    Gmane

    The Cocoon lists are mirrored on the Gmane -mail-to-news/web gateway.  -This page +asking those kinds of questions.Of course, new Cocoon releases are announced on this list.

    Gmane

    The Cocoon lists are mirrored on the Gmane +mail-to-news/web gateway.  +This page contains links you can use to subscribe your Usenet newsreader to the user list as a newsgroup, browse the list using Gmane's web interface, or subscribe your -feedreader to a number of RSS feeds driven by the list.The lists are also mirrored -at Nabble; you can browse or post.  (Note the "child forums" links).

    Archive

    Archive sites can be found on the overview +feedreader to a number of RSS feeds driven by the list.The lists are also mirrored +at Nabble; you can browse or post.  (Note the "child forums" links).

    Archive

    Archive sites can be found on the overview page. Note that the mail-archive site changed in July 2003.

    Developer list

    This list is for anyone interested in working on Cocoon -itself (application developers making applications with Cocoon are -Cocoon users).  Anyone can read or post to this list; you don't have to -be a Cocoon committer.  Read this list if you want to learn more about the inner +

    Developer list

    This list is for anyone interested in working on Cocoon +itself (application developers making applications with Cocoon are +Cocoon users).  Anyone can read or post to this list; you don't have to +be a Cocoon committer.  Read this list if you want to learn more about the inner workings of Cocoon, or for detailed discussions about bugs or future enhancement -requests.  Please don't post routine user questions to the dev list, though.  -The topic of this list is Cocoon development.If you post a question in the user list, and the discussion gets so geeky +requests.  Please don't post routine user questions to the dev list, though.  +The topic of this list is Cocoon development.If you post a question in the user list, and the discussion gets so geeky that it has to move to the dev list... don't forget to come back to the user list with a "SOLVED:" post, once you've gotten everything ironed out! :-)The dev list gets automatic update notifications from the -JIRA issue tracking +JIRA issue tracking system and from the -Continuum -build system.

    Gmane

    The developer list is also -available on -Gmane.

    Archive

    Archive sites can be found on the overview +Continuum +build system.

    Gmane

    The developer list is also +available on +Gmane.

    Archive

    Archive sites can be found on the overview page. Note that the mail-archive site changed in July 2003.

    Documentation list

    This read-only list is of interest to people who are -working on the Cocoon documentation.  It consists +

    Documentation list

    This read-only list is of interest to people who are +working on the Cocoon documentation.  It consists solely of update notifications from the Daisy docs CMS and -the Wiki.

    Gmane

    On Gmane, -right -here.

    SVN repository update list

    This list is probably only of interest to hard-core Cocoon developers.  It is -a read-only list that consists solely of automated update -notifications from the Subversion source code management system.  The name -"cocoon-cvs" is a holdover from when the Cocoon project used CVS.

    Gmane

    This one is on Gmane -too.

    Wiki

    There's a Cocoon Wiki.  YMMV -

    IRC

    The Cocoon community chat room is the #cocoon channel at -freenode.net.  Get over there and shake things -up!

    JIRA

    Bug/issue tracking on the Cocoon project -uses Atlassian -JIRA.  This is a communication medium in its own right.  Updates to JIRA +the Wiki.

    Gmane

    On Gmane, +right +here.

    SVN repository update list

    This list is probably only of interest to hard-core Cocoon developers.  It is +a read-only list that consists solely of automated update +notifications from the Subversion source code management system.  The name +"cocoon-cvs" is a holdover from when the Cocoon project used CVS.

    Gmane

    This one is on Gmane +too.

    Wiki

    There's a Cocoon Wiki.  YMMV +

    IRC

    The Cocoon community chat room is the #cocoon channel at +freenode.net.  Get over there and shake things +up!

    JIRA

    Bug/issue tracking on the Cocoon project +uses Atlassian +JIRA.  This is a communication medium in its own right.  Updates to JIRA issues trigger notifications to the dev mailing list, so you can monitor each -issue's mini-discussion from the dev mailing list.
    Errors and Improvements? If you see any errors or potential improvements in this document please help - us: View, Edit or comment on the latest development version (registration required). -
    +issue's mini-discussion from the dev mailing list.
    +
    - + \ No newline at end of file Modified: cocoon/site/site/1276_1_1.html URL: http://svn.apache.org/viewvc/cocoon/site/site/1276_1_1.html?rev=1311666&r1=1311665&r2=1311666&view=diff ============================================================================== --- cocoon/site/site/1276_1_1.html (original) +++ cocoon/site/site/1276_1_1.html Tue Apr 10 10:24:47 2012 @@ -29,17 +29,13 @@ Cocoon Main Site - Other tools that we use - + - - - + + + - +

    Apache » Cocoon »

    @@ -74,7 +70,7 @@
  • Core 2.2
  • Blocks 2.2
  • Maven Plugins 2.2
    • -
  • Cocoon 3.0 [alpha]
    • +
  • Cocoon 3.0
  • Subprojects
    • @@ -89,7 +85,7 @@
  • - Getting started + Getting Started
    • @@ -159,7 +153,7 @@
  • - Getting better + Getting Better
    • @@ -247,10 +231,6 @@ - - - -
  • Project Information @@ -259,7 +239,7 @@
  • Versions
    -

    Other tools that we use

    Fixme: TODO: add missing link targets

    Subversion

    subversion_logo

    The Cocoon project uses Subversion -for source code version management... details here.

    Maven

    maven-feather

    The Cocoon project uses Apache Maven + +

    Other tools that we use

    Fixme: TODO: add missing link targets

    Subversion

    subversion_logo

    The Cocoon project uses Subversion +for source code version management... details here.

    Maven

    maven-feather

    The Cocoon project uses Apache Maven in several roles:

      -
    • For Cocoon users: as the downloader for getting the +
    • For Cocoon users: as the downloader for getting the artifacts that constitute the Cocoon binary distributions. These artifacts include:
        @@ -281,47 +277,51 @@ include:
      This method is superior to other alternatives, e.g. downloading tarballs, manually downloading transitively dependent artifacts, etc.
      • -
    • Also for Cocoon users: optionally, as the deployer/launcher +
    • Also for Cocoon users: optionally, as the deployer/launcher for Cocoon, e.g. to run in an instance of the Jetty servlet container (details).
      • -
    • For Cocoon application developers building web +
    • For Cocoon application developers building web apps using Cocoon + custom Java code: it's recommended that you set up your -projects to use Maven as your build tool.  This frees you from having to deal +projects to use Maven as your build tool.  This frees you from having to deal with all the usual low-level build infrastructure issues of classpaths, jar dependencies and versions, etc. and lets you get on with the coding!
      • -
    • For Cocoon developers: as the build tool for +
    • For Cocoon developers: as the build tool for building Cocoon (all, or parts of) from the source -code.  You are a Cocoon developer if you are working on a patch or other source -code submission.  Note: Cocoon users / application -developers should never need to build Cocoon from the source code.  It should be +code.  You are a Cocoon developer if you are working on a patch or other source +code submission.  Note: Cocoon users / application +developers should never need to build Cocoon from the source code.  It should be sufficient to specify Cocoon artifacts in your project's Maven -POM, which +POM, which you can set up initially using a Maven archetype.
      • -
    Note: Maven 2.0.6 or greater is required for all of these tasks.

    Eclipse

    A lot of Cocoon developers like to use the -Eclipse IDE, so the Cocoon build sets up -Cocoon as an Eclipse project.  However, you don't have -to use Eclipse to develop with or on Cocoon.  You can get by with nothing but a -text editor and Maven.

    Jira

    jira_logo_smallThe Cocoon project uses Atlassian JIRA for bug/issue tracking.  Anyone can -browse the issues.  +
    Note: Maven 2.0.6 or greater is required for all of these tasks.

    Eclipse

    A lot of Cocoon developers like to use the +Eclipse IDE, so the Cocoon build sets up +Cocoon as an Eclipse project.  However, you don't have +to use Eclipse to develop with or on Cocoon.  You can get by with nothing but a +text editor and Maven.

    Jira

    jira_logo_smallThe Cocoon project uses Atlassian JIRA for bug/issue tracking.  Anyone can +browse the issues.  Anyone can create or comment on an issue too, you just have to -create a -login on Apache's JIRA first.

    Continuum

    continuumThe Cocoon project uses Maven -Continuum to run its -continuous +create a +login on Apache's JIRA first.

    Continuum

    continuumThe Cocoon project uses Maven +Continuum to run its +continuous integration build cycle. This probably isn't all that interesting except to the Cocoon committers. For the rest of us, we can just feel happy about the fact -that Cocoon is being integrated... continuously... :-)
    Errors and Improvements? If you see any errors or potential improvements in this document please help - us: View, Edit or comment on the latest development version (registration required). -
    +that Cocoon is being integrated... continuously... :-)
    +
    - + \ No newline at end of file Modified: cocoon/site/site/1277_1_1.html URL: http://svn.apache.org/viewvc/cocoon/site/site/1277_1_1.html?rev=1311666&r1=1311665&r2=1311666&view=diff ============================================================================== --- cocoon/site/site/1277_1_1.html (original) +++ cocoon/site/site/1277_1_1.html Tue Apr 10 10:24:47 2012 @@ -29,17 +29,13 @@ Cocoon Main Site - Cocoon GT 2006 in Amsterdam - + - - - + + + - +

    Apache » Cocoon »

    @@ -74,7 +70,7 @@
  • Core 2.2
  • Blocks 2.2
  • Maven Plugins 2.2
    • -
  • Cocoon 3.0 [alpha]
    • +
  • Cocoon 3.0
  • Subprojects
    • @@ -89,7 +85,7 @@
  • - Getting started + Getting Started
    • @@ -159,7 +153,7 @@
  • - Getting better + Getting Better
    • @@ -247,10 +231,6 @@ - - - -
  • Project Information @@ -259,7 +239,7 @@
  • Versions
    -

    Cocoon GT 2006 in Amsterdam

    The Apache Cocoon community is proud to announce the fifth -(!) annual edition  of the -Cocoon GetTogether, the main annual gathering of current and + +

    Cocoon GT 2006 in Amsterdam

    The Apache Cocoon community is proud to announce the fifth +(!) annual edition  of the +Cocoon GetTogether, the main annual gathering of current and future Cocoon users and developers. During this event, you'll have a unique chance to meet and intermingle with fellow Cocoon enthusiasts, to hear what's hot and what's not, and to get your hands dirty with some real on-site Cocoon -coding.

    Errors and Improvements? If you see any errors or potential improvements in this document please help - us: View, Edit or comment on the latest development version (registration required). -
    +coding.

    +
    - + \ No newline at end of file Modified: cocoon/site/site/1278_1_1.html URL: http://svn.apache.org/viewvc/cocoon/site/site/1278_1_1.html?rev=1311666&r1=1311665&r2=1311666&view=diff ============================================================================== --- cocoon/site/site/1278_1_1.html (original) +++ cocoon/site/site/1278_1_1.html Tue Apr 10 10:24:47 2012 @@ -29,17 +29,13 @@ Cocoon Main Site - Cocoon GT presentations available! - + - - - + + + - +

    Apache » Cocoon »

    @@ -74,7 +70,7 @@
  • Core 2.2
  • Blocks 2.2
  • Maven Plugins 2.2
    • -
  • Cocoon 3.0 [alpha]
    • +
  • Cocoon 3.0
  • Subprojects
    • @@ -89,7 +85,7 @@
  • - Getting started + Getting Started
    • @@ -159,7 +153,7 @@
  • - Getting better + Getting Better
    • @@ -247,10 +231,6 @@ - - - -
  • Project Information @@ -259,7 +239,7 @@
  • Versions
    +

    Cocoon GT presentations available!

    Slides and material from the Cocoon GetTogether 2006 are now available.

    See -http://wiki.apache.org/cocoon/GT2006Notes -

    Errors and Improvements? If you see any errors or potential improvements in this document please help - us: View, Edit or comment on the latest development version (registration required). -
    +http://wiki.apache.org/cocoon/GT2006Notes +

    + - + \ No newline at end of file Modified: cocoon/site/site/1279_1_1.html URL: http://svn.apache.org/viewvc/cocoon/site/site/1279_1_1.html?rev=1311666&r1=1311665&r2=1311666&view=diff ============================================================================== --- cocoon/site/site/1279_1_1.html (original) +++ cocoon/site/site/1279_1_1.html Tue Apr 10 10:24:47 2012 @@ -29,17 +29,13 @@ Cocoon Main Site - News archive - + - - - + + + - +

    Apache » Cocoon »

    @@ -74,7 +70,7 @@
  • Core 2.2
  • Blocks 2.2
  • Maven Plugins 2.2
    • -
  • Cocoon 3.0 [alpha]
    • +
  • Cocoon 3.0
  • Subprojects
    • @@ -89,7 +85,7 @@
  • - Getting started + Getting Started
    • @@ -159,7 +153,7 @@
  • - Getting better + Getting Better
    • @@ -247,10 +231,6 @@ - - - -
  • Project Information @@ -259,7 +239,7 @@
  • Versions
    -

    News archive

    Warning: There is no styling for this query available.
    Errors and Improvements? If you see any errors or potential improvements in this document please help - us: View, Edit or comment on the latest development version (registration required). -
    + +

    News archive

    Warning: There is no styling for this query available.
    +
    - + \ No newline at end of file Modified: cocoon/site/site/1281_1_1.html URL: http://svn.apache.org/viewvc/cocoon/site/site/1281_1_1.html?rev=1311666&r1=1311665&r2=1311666&view=diff ============================================================================== --- cocoon/site/site/1281_1_1.html (original) +++ cocoon/site/site/1281_1_1.html Tue Apr 10 10:24:47 2012 @@ -29,17 +29,13 @@ Cocoon Main Site - Cocoon in HigherEdWebDev conference - + - - - + + + - +

    Apache » Cocoon »

    @@ -74,7 +70,7 @@
  • Core 2.2
  • Blocks 2.2
  • Maven Plugins 2.2
    • -
  • Cocoon 3.0 [alpha]
    • +
  • Cocoon 3.0
  • Subprojects
    • @@ -89,7 +85,7 @@
  • - Getting started + Getting Started
    • @@ -159,7 +153,7 @@
  • - Getting better + Getting Better
    • @@ -247,10 +231,6 @@ - - - -
  • Project Information @@ -259,7 +239,7 @@
  • Versions
    +

    Cocoon in HigherEdWebDev conference

    -http://www.highedweb.org/2006/presentations/aus/AUS11.ppt -

    +http://www.highedweb.org/2006/presentations/aus/AUS11.ppt +
    Presentation at HigherEdWebDev 2006 featuring Cocoon as a framework for managing proposal-initiated workflows. The presentation was held during the conference -Oct 22-25 in Rochester, USA.

    Errors and Improvements? If you see any errors or potential improvements in this document please help - us: View, Edit or comment on the latest development version (registration required). -
    +Oct 22-25 in Rochester, USA.

    + - + \ No newline at end of file