web site planning

[Anil Gangolli <an...@busybuddha.org>]

A couple of notes:

Confluence autogeneration seems to be based on Velocity templates.  We can 
probably start by cloning one and doing some edits.

Several teams seem to have decided to use multiple Confluence spaces in 
their auto-generated site.   The Geronimo team has a pretty good writeup 
here ( 
http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html   
) on how they've organized their site.  The different spaces can have 
different access rights; so, for example, some portions we could have 
limited to committers/CLAs on file while allowing edits by the public in 
other areas.   This affects what we can ship in distributions.
However, looking at the Geronimo or Apache Directory sites,  I'm not sure if 
I understand all of the reasons for all of the separated spaces.  It seems 
like something we should decide on before we start dumping a lot into the 
single Roller space.

--a.







----- Original Message ----- 
From: "Dave" <sn...@gmail.com>
To: <ro...@incubator.apache.org>
Sent: Wednesday, March 28, 2007 10:00 AM
Subject: Re: tangled web we've woven?


> >Anil Gangolli wrote:
>> > Is it just me or is our web site situation a tangle between 
>> > rollerweblogger.org, cwiki stuff, and dev.java.net support stuff?  Also 
>> > roller.apache.org seems to be pointing to an unpopulated auto-indexed 
>> > directory.Anyway, I've found I have a hard time navigating it and also 
>> > knowing where things should be going.
>> > I'd like to help with the untangling but I think we need to agree on a 
>> > rough site plan.
>
> It's not just you. Others have complained.
>
>
> On 3/28/07, Allen Gilliland <al...@sun.com> wrote:
>> I agree, an organized attempt to resolve the situation would be the most
>> beneficial and there isn't any plan that I've heard of so I say go for 
>> it.
>>
>> If we can get a plan and agree on it then maybe we can divide up the
>> work load amongst us and just have everyone do their part to get the sit
>> polished.  If we do that then I would expect we could get everything
>> cleaned up pretty quickly and no one person would have to do all the 
>> work.
>
> Cool!
>
> Now that the infra team has put the site in place at roller.apache.org
> any committer should be able to complete the job and populate it with
> content. Currently we use Velocity/Anikia to generate the site, but we
> don't have to continue with that. My preference is Confluence static.
>
> There is other work to be done to untangle and clean up our web
> presence. I'm busy on ROME/Propono most of this week, but here's what
> I'd like to do with the Roller sites:
>
> *** roller.apache.org - Roller project home page
> - Put site in place ASAP!
> - Use existing Anikia site?
> - Use Confluence static publishing feature?
> - Just point to the wiki?
> - Other ideas?
>
> *** http://cwiki.apache.org/confluence/display/ROLLER/ - Roller wiki
> - I think the site's charter and organization is pretty clear
> - Ideas for improvement?
> - But it it for use of committers only?
>
> *** rollerweblogger.org/project - blog and planet
> - Can still serve as project blog and planet site, since we can't run
> Roller at Apache
> - All official announcements must be made via email, but we can echo them 
> here
> - Could be a better showcase of what we can do with Roller
>
> *** roller.dev.java.net - non Apache Roller add-ons, plugins and themes
> - I think the site's charter and organization is pretty clear
> - Ideas for improvement?
>
> *** rollerweblogger.org/wiki - retire this site
> - I'd like to use this as my personal wiki and remove Roller content
> - So I'd like to empty all old Roller pages and make them point to new 
> wiki
>
>
> - Dave
> 

Re: web site planning

[Dave <sn...@gmail.com>]

On 4/2/07, Anil Gangolli <an...@busybuddha.org> wrote:
> Confluence autogeneration seems to be based on Velocity templates.  We can
> probably start by cloning one and doing some edits.

I did a little poking around over the weekend too, but I started by
looking at Matt's post and the Wicket site.

   http://raibledesigns.com/rd/entry/slick_looking_confluence_sites

I don't want to delay our "we've graduated" announcements forever so I
went ahead and put the basic site in place at http://roller.apache.org
using our existing mechanism. See the readme in ./site for details.
I'd like to switch to Confluence auto-export just as soon as we can
figure it out.

>
> Several teams seem to have decided to use multiple Confluence spaces in
> their auto-generated site.   The Geronimo team has a pretty good writeup
> here (
> http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html
> ) on how they've organized their site.  The different spaces can have
> different access rights; so, for example, some portions we could have
> limited to committers/CLAs on file while allowing edits by the public in
> other areas.  This affects what we can ship in distributions.
> However, looking at the Geronimo or Apache Directory sites,  I'm not sure if
> I understand all of the reasons for all of the separated spaces.  It seems
> like something we should decide on before we start dumping a lot into the
> single Roller space.

I don't understand why they have so many spaces either. A lot of their
spaces seem to be for different versions of Geronimo docs. Since we're
using Open Document format for our "official" docs, I think we only
need two spaces. We need a committer access only area for the Roller
website and a less restrictive space for new feature proposals.

I haven't yet found a step-by-step guide to setting up auto-export and
the cron-jobs necessary to make it work. Anybody have any pointers?

- Dave