cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gou...@osmosis.gr
Subject RE: Moving docs from Wiki
Date Wed, 26 Nov 2003 07:58:10 GMT
On Wed, 26 Nov 2003, Reinhard Poetz wrote:

> 
> From: David Crossley
>  
> > Vadim Gritsenko wrote:
> > > Reinhard Poetz wrote:
> > > 
> > > >No problem, that was not the difficult part - I had more problems 
> > > >with the publishing process itself:
> > 
> > I presume that you know about 
> > http://wiki.cocoondev.org/Wiki.jsp?page=CocoonWebsiteUpdate
> > 
> > Agreed, the process could be easier. Thank your lucky stars 
> > that you were not struggling with Cocoon docs a couple of years ago.
> > 
> > > >  1) complete build of Cocoon including documentation
> > > >  2) use forrest to generate 'real' documentation
> > > 
> > > "build docs" does these two items.
> > > 
> > > >  3) then I used 'forrest run' and and XML editor to edit/create
> > > >     my docs (it took me very long until I found out *where* I
> > > >     can edit my docs)
> > 
> > Sorry. The cvs head version of Forrest is leaving source and 
> > skins in-place and not copying them around. (But Cocoon is 
> > using 0.5 ATM.)
> > 
> > > >     BTW: an XML editor is the *worst* thing to edit 
> > content at all 
> > > > ...
> > 
> > Why do you say that? We should fix it then.
> 
> The only fix which will help me is a WYSIWIG-editor - otherwise it is
> always painful to edit content.

altova's  authentic can provide a WYSIWIG but every time i had to try to 
setup an XML/XSL/SPS (SPS is a autheintic  xml file that "drive" the 
WYSISWG) i have no reluts.

maybe a authentic view of xdocs can help

-- stavros
 


> 
> > 
> > > >  4) then I had to copy the changed docs *manually* back into
> > > >     the Cocoon docs to check them in
> > 
> > Yes, see answer to 3). In Forrest-0.5 there is the 'forrest 
> > backcopy' target for that.
> > 
> > > >  5) then I had to generate the 'site' and copy them *manually*
> > > >     into cocoon-site
> > > 
> > > "build docs" does (5) too.
> > >
> > > >  6) then I checked in cocoon-2.1
> > > >  7) then I checked in cocoon-site
> > 
> > Cannot be avoided.
> > 
> > > >  8) then I updated our website using the CVS client on 
> > > > cvs.apache.org
> > > 
> > > Yes, these are manual steps.
> > 
> > Some projects have a cron job to do that automatically,
> > say every 12 hours.
> 
> 
> thanks for your explanations - I'll look them up when I add/change some
> docs in the future!
> 
> --
> Reinhard
> 
> 


Mime
View raw message