Addi wrote:
Hm, well I don't know what resources the Apache projects are dealing
with but I have not implemented Forrest at my work (other than for me to
play with) because I am the only person who understands anything about
XML. The biggest hurdles I see at my office are site.xml and the actual
documents with deployment also being a secondary issue. They are
hurdles because I can't be the only person who knows how to use it. It
isn't efficient if I'm the only one who can add docs and do anything at
all with it. Now that I have spent time with Forrest I know there are
some tools to help me with those issues. So *for my use case situation*
things that would make Forrest more viable:
- A simple, intuitive way for non-XMLers to add things to site.xml
Have you any suggestions about what this may look like?
Have you taken a look at the Eclipse plugin? This is a (very early
development) of a GUI application for editing of things like site.xml.
It works, but is a long way from perfect.
The biggest hurdle to its use is that it requires an Eclipse
installation, although it is possible to build a standalone application
for it.
- Emphasis and stupid clear instructions on document plugins (DocBook,
OpenOffice)
- Emphasis and stupid clear instructions on Forrestbot
>
By stupid clear, I mean so that someone with little XML and Forrest
experience can understand at least half of what you are saying and not
be intimidated to at least try.
Yes, docs are important and are the hardest things to create. The
problem is that to write them you need to have the inclination to make
them "stupid clear", unfortunately most of the devs don't have such a drive.
All help is welcome, and newcomers to Forrest are in the best position
to write these stupid clear docs - with help and guidance from the devs
of course.
Ross
