> >
> > Most things will be static and pregenerated, like you plan it for the
> > mod_perl site. There maybe a small dynamic part, where people are able
to
> > add links, examples, news etc.
>
>
> that would be a very good thing to have! The problem is providing the
required setup on apache.org.
>
>>Say, do you plan on static output from Embperl or only dynamic for
>>embperl docs? It doesn't make much sense to serve static content
>>dynamically, resource wise of course.
>>
>>
>
> Most things will be static and pregenerated, like you plan it for the
> mod_perl site. There maybe a small dyn
>
> Well, the code is quite crude yet, and it's hard to modularize before
> you know what to plan for, but yes the rendering engine is a separate
> thing. So after generalizing it and making it pluggable it should be
> possible to use other rendering modules.
>
I will take a look at it when you r
Gerald Richter wrote:
>> - the package handles links so we have no problem linking to e.g.
>>perl.apache.org/dist/
>>
>
> ok, so we have the possibility to use content that is not part of the docset
yup.
>> - embperl site, I suppose it can be folded into the docset, if Gerald
>>doesn't mi
>
> With my proposal we will have to do:
>on our machines:
>1. cvs up
>2. apply changes
>3. cvs ci
>on apache.org:
>4. cvs up
>5. bin/build
>
> so there is one extra step to do. Is this OK?
>
For the modperl site that would be ok for me. (Since everything is done for
m
