Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Message-ID: <40D76637.3020206@apache.org>
Date: Tue, 22 Jun 2004 00:50:31 +0200
From: Stephen McConnell <mcconnell@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.6b) Gecko/20031208
MIME-Version: 1.0
To: Avalon Developers List <dev@avalon.apache.org>
Subject: Re: Documentation
References: <cb7bj0$vam$1@sea.gmane.org>
In-Reply-To: <cb7bj0$vam$1@sea.gmane.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Andreas:

I'm rather comfortable with the process of svn based document sources 
and I'm also sure that we could generate pdf from this when the need 
arises - but this raises an priority point ..... our content is the 
information is svn and avalon stuff is generated though evolution of 
that content.  For example - the world view of Merlin Studio is based on 
the content registered in svn today.  That world view needs to be 
available to committers here at avalon in order to accelerate its 
development.  That also means that the content needs to parseable into 
the avalon site as a primary step.

Where we go from there is a lot to do with with the investments we make 
into magic and in particular - transformations of the xdoc variant we 
are using.  Personally I'm keen on seeing a PDF output - the navigation 
structure we have in place lends itself nicely to subsection 
decomposition - and I think we would have one tremendous output pdf once 
the transformation is sorted.

Cheers, Steve.


Andreas Oberhack wrote:

> Hi All,
> 
> 
> I had a closer look at our documentation / website editing / updateding
> requirements.
> 
> 
> For me there some weaknesses in the current documentation development
> 
> process:
> 
> 
> 1) the xdoc -> checkout -> read / change - > check-in -> inform others etc.
> process is to slow and error prone
> 
> 2) concurrency is not handled properly or at least difficult
> 
> 
> Beside that we - or maybe only I - have multiple requirements on the xdoc
> 
> -> output generation:
> 
> 
> 1) HTML based output for: our website, eclipse help etc.
> 
> 2) Word / PDF output with various layouts: for us / my customers etc.
> 
> 
> My proposals:
> 
> 
> Maybe we could use MoinMoin as the editor for our documentation content. We
> get notification, change history, concurrency etc. for free. We could
> automatically download the content by RPC and generate the various output
> formats by velocity or what ever.
> 
> There are limited formatting options in MoinMoin - but we can easily enhance
> those if we like.
> 
> 
> What do you all think??
> 
> 
> Andreas
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
> 
> 


-- 

|---------------------------------------|
| Magic by Merlin                       |
| Production by Avalon                  |
|                                       |
| http://avalon.apache.org              |
|---------------------------------------|

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org