+ Forrest is still quite young, so there are known issues. + Standards compliance is a definite major goal. Please send patches + for the Forrest skin stylesheets to ensure such compliance. +

+ + + +

HTML

+ Tested using the W3C HTML Validation Service + (validator.w3.org). The + index.html page of Forrest sites will have a link to this validator, + unless the user has turned this off. +

+ The "pelt" skin + validates as HTML 4.0.1 +

+ The "tigris" skin + validates as HTML 4.0.1 +

+ + + +

WAI

See +Web Accessibility Initiative (WAI) + +

+ There are actually many accessibility issues with the heavy use of + tables and images. These skins are gradually being improved. +

+Bobby with WAI: +bobby.watchfire.com + +

Issues ...

+ Priority 1: alt text for images. +
Priority 2: + Explicitly + associate form controls and their labels with the LABEL element. + Perhaps we could have a label hidden with CSS?
FIXME: need to list other issues here, or attend to them.

Note

The forrest-site skin does not have any missing alts. Perhaps Bobby + does not like the trick with empty alt attributes. However, it only + complains about the two in the footer, and not about the other 40.

+Bobby with U.S. Section 508 Guidelines: +bobby.watchfire.com + +

Issues ...

The same issues as above

+ + + +

CSS

+Jigsaw: +jigsaw.w3.org + +

Issues ...

CSS 2: No errors. Some warnings.
CSS 1: Errors: hover class, @media-print. Some warnings.
FIXME: need to list other issues here, or attend to them.

+ +

+ + +

0.70

+Overview +

+FAQs +

+Changes +

+Todo +

+Using Forrest +

+XML Validation +

+Menus and Linking +

+Searching +

+Default Skins +

+Skin Packages +

+Views-dev +

+Our Contract +

+Standards Compliance +

How-To

+Overview +

+Write a How-to +

+Download mirror +

+Create tab PDF +

+Edit CSS (WYSIWYG) +

+CSS corner SVG +

+Maven Integration +

+Build a Plugin +

+Custom html source +

Multipage HowTo

+Introduction +

+Step 1 +

+Step 2 +

+Step 3 +

Views

+Install views +

+forrest:view DSL +

+contract implementations +

Advanced Topics

+Building Forrest +

+Using DTD Catalogs +

+Sitemap Reference +

+Project sitemap +

+Sourcetype Action +

+Upgrading to 0.7 +

Reference docs

DTD documentation

+Overview +

+document-v20 +

+howto-v20 +

+faq-v20 +

+document-v13 +

+howto-v13 +

+faq-v13 +

Doc samples

+document-v13 +

+document-v20 +

Older Docs

+Forrest Primer +

+Libre +

Dream list

+CVS over SSH +

+ This is documentation for current version v0.7 + (More)

+ PDF +

+Font size: + + + +

Forrest dream list

Overview

+ This is documentation for current version v0.7 + (More)

+Introduction +
+Draft dream list +

+ + +

Introduction

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 + provides an overview. +

These are the email threads and documents that are currently being + summarised. Please see those documents for further detail. +

+ [RT] my Forrest dream-list + Date: Wed, 20 Feb 2002 + http://marc.theaimsgroup.com/?l=forrest-dev&m=101431895118349 + [done] +
+ README + [FIXME: not yet started summarising] +
+ [phases] Forrest + Date: Fri, 22 Feb 2002 + http://marc.theaimsgroup.com/?l=forrest-dev&m=101445744931104 + [FIXME: not yet started summarising] +
+ adding to the dream list + Date: Fri, 15 Mar 2002 + http://marc.theaimsgroup.com/?l=forrest-dev&m=101620970016263 + [FIXME: not yet started summarising] +
+ analysis paralysis :-) + Date: Mon, 25 Feb 2002 + http://marc.theaimsgroup.com/?l=forrest-dev&m=101465344708301 + [FIXME: not yet started summarising] +
+ documentation architecture? + Date: Thu, 25 Apr 2002 + http://marc.theaimsgroup.com/?l=forrest-dev&m=101973705501466 + [FIXME: not yet started summarising] +
+ Topic Maps for Forrest ? + Date: Mon, 18 Mar 2002 + http://marc.theaimsgroup.com/?l=forrest-dev&m=101647290524645 + [FIXME: not yet started summarising] +

+ + + +

Draft dream list

+ Forrest provides a robust technological infrastructure for open software development for the Apache Software Foundation based on ASF software, ASF practices and experience, and modern software design principles. +
+ a publishing system for documentation +
+ analysis of logs and publishing of results +
+Ok, first of all: "it hurts my spirit" (I should TM this) to see the +apache web sites with such a *poor* information infrastructure. Just +look at sourceforge: it's not the best site of the world, but gives you +lots of tools and information that we currently don't have (or have +hidden someplace). +
+I want Forrest to be the development infrastructure of your dreams, +something that you'll be proud of showing your boss and say "if only we +had this in place, we would save big bucks" so... +
+ Dream #1: Forrest should make Sourceforge look obsolete. +
+So, in order for this to happen, it must be dynamic. +Assumption #1: Forrest is a dynamic site. +The staticity of apache web sites was mostly due to the quest for heavy +mirroring, Forrest should allow mirroring, so +
+ Dream #2: Forrest should reduce xml.apache.org bandwidth use dramatically +
+ Dream #3: Forrest should automate mirroring in a simple and easy way. + +My idea is to use the 'command line' features of Cocoon to generate +static snapshots of sites and produce mirrors directly using a sort of +rsync or other mean. Anyway, the goal is to make sure mirroring is as +easy as possible. No, easier than that. +
+ coherence: all the site should look coherent, same graphics, same +look-and-feel, same information in the same locations, coherent and nice URI +space (build to last! so that broken links are reduced!) +
+ structure: the site should look professional, the structure should be +flexible enough to fit every need but solid enough to guide users +browsing and developers adding resources +
+ scalability +
+ functionality: everything you ever wanted to have in your project web site +
+ logs and community rating: I want to have numbers to judge the value +of a community/effort +
+Downloads, number of committers, numbers of people subscribed on the users/dev +list, numbers of mail messages / week on these lists, CVS activity... +These are the kind of parameters I use to "judge" an Apache project that I +have not been looking into before. +
+ Graphs of various statistics. +
+Having good site metrics will be a valuable aid to those involved in +maintenance and future re-design phases. +See some discussion in +http://marc.theaimsgroup.com/?l=forrest-dev&m=102238816218885 + +
+ Built-in search engine: users much have a simple way to find things. + Lucene. +
+ User-writable pages: people should have a way to add things to the pages. + See the thread for more detail on this. +FIXME: get MARC ref +
+ short bios for the project committers, with pictures: gives a better +sense of community. Having a weblog there would be great. +
+ news, announcements, events and project calendaring: the news and +the announcements will generate a RSS feed, events will be aggregated +into a project-wide calendar, or an effort-specific calendar, the events +will also be overwritten on the logs, to indicate how logs were +influenced by the events (say, a release or a new committer added) +
+ book-like PDF versions of documentation: easy to print out docs. +
+ integration with GUMP: dependencies, runs, committer that broke the run +
+ javadocs seemlessly integrated with the documentation and with the +search engine. + http://marc.theaimsgroup.com/?l=forrest-dev&m=101620970016263 + +
+ mail archive seemlessly integrated with the search engine (one should +look for something and get results from either docs, javadocs or emails +messages) +
+ coherent-looking CVS view +
+ document translation using Google translation services +
+ Integrated project management, task management, bug tracking, feature requests, process management. +The idea is to integrate Scarab for bug tracking/patches and +managing/feature requests. +(As far as team management, this is a serious political issue and I do not +want to tackle that one yet, not even on the dreamlist.) +
+ overview doco for all projects ... CVS Usage precis, overview of opensource + and links to relevant doco +

+ + +