Nicola,
> Take a look at this too.
> http://xml.apache.org/forrest/
After spending some time studying the information on the Forrest site it does
not take one long to see that the site does an exceptional job of marketing
Forrest's virtues.
In my opinion, wrapping the Embedlet project's documentation inside an XML file
format was always a must but I had not given too much thought on how to make
this information available to the public aside from placing periodic snapshots
of it on a website or having them pull it from the CVS.
If the periodic CVS snapshot technique is considered to be a country lane that
can be used to publish CVS contents to the web, then in comparison Forrest
appears to provide a 6 lane highway that can pump the contents in a CVS to the
web in a wide variety of flexible formats on an on-demand basis.
I also like Forrest's Documentation DTDs better than OpenOffice's DTDs because
they appear to be optimized for use with software project documentation while
OpenOffice's DTDs are much more generic.
Finally, I had been wondering how we were going to put together the Embedlets
main website and how much of a pain it was going to be to maintain it. If we
decide to go with something like Forrest then a lot of hard work has already
been done for us and we would have a much higher quality website on day one
then we could ever achieve with a home grown website.
What do other people think of the possibility of using Forrest for our
documentation needs?
Ted
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
|
