+1 for switching.  Also I like the idea of replacing the front page
with a blog - I can think of a couple sites I could use that on.

Matt

On 4/5/06, David M Johnson <[EMAIL PROTECTED]> wrote:
>
> I've been thinking about how to better use the planet features in
> Roller and as part of that, I've put together a new layout for the
> Roller project site, which is itself a Roller blog.
>
> I think tighter Roller-Planet integration is the key to building
> better project/community sites, so I want to show some of the cool
> things you can do right now with Roller's integrated planet
> aggregator. Eventually, I would like to allow every blog to be able
> to define it's own set of aggregations and not limit planet
> configuration to global admins. I'd also like to do away with the
> main.do and planet.do Struts Actions / JSP page and replace the
> Roller front page with a blog, so it  can be configured at runtime
> via the Roller UI. More about that later.
>
> If you go to the Roller project blog, you still see the old layout:
>     http://rollerweblogger.org/page/project
>
> To view the new layout, visit one of these pages:
>
>     http://rollerweblogger.org/page/project/about
>     http://rollerweblogger.org/page/project/news
>     http://rollerweblogger.org/page/project/planet
>     http://rollerweblogger.org/page/project/dashboard
>
> The about page is a simple what is Roller page. The news page
> displays the entries of the project blog. That's just routine Roller
> blog stuff. The planet page is where things get interesting. It uses
> the planet aggregator to display the most recent post from the Roller
> project members (i.e. committers). The dashboard page uses the planet
> features to display the most recent Roller wiki changes and the most
> recent JIRA issues.
>
> This is all done using a stock Roller 2.2 build, but with this
> configuration setting:
> velocity.pagemodel.classname=org.roller.presentation.velocity.planet.Pla
> netPageModel
>
>
> Anybody opposed to switching over to this new layout?
>
> - Dave
>
>
>
>

Reply via email to