Keiron Liddle wrote:
> The original idea of the development was for user documentation
> for the current
> development. So it can be updated as the API and other such
> details are changed.
If "user documentation" means "developer documentation", and "current
development" means "maintenance branch development", then I think I
understand. That would make the "redesign" tab be for the new development.
If that is what we want, then I'll go to work on making that more clear.
> For example with the faq, it had some different information on
> things such as text
> in SVG. Maybe it would be better to only have the new information there.
With regard to the faq, I just last night sliced out nearly all of the
contents of the dev/faq.xml file. As far as I could tell, it was a duplicate
of an old version of the faq.xml. Those changes are not reflected on the
site yet (I have emailed Jeff to try to find out why not).
I don't care a lot about whether we have 1 or 2 developer tabs -- I just
want to clarify what they are, not only so that I know what to put where,
but also so that the web site users understand what they are seeing. It is
confusing enough to have two branches of development, but to have our
documentation mixed up or unclear is a serious problem. A case could be made
that we don't want a developer tab for the maintenance branch, because we
don't really want anyone developing for it. I kind of thought that was what
was going on when I saw the index for it with the title "FOP 1.0
development".
I propose the following for a 3-tab structure (I am not ignoring the Alt
Design tab, it just isn't affected by this):
Home
Release Development
1.0 Development
If you prefer to combine the developer doc, then:
Home
Development
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
