[Grok-dev] the grok website: Plone?

[Matt Bowen]

Hi all,

Before we head out and install Plone, we should probably do a little needs
assessment. How much do we want the new site to be like the current one? Do
we want a new look and feel, or to mirror what we've got? What features is
the current site lacking that the new site needs? Of these features, which
should be reserved for Grok apps? Do we want to modify the IA of the Grok
site to accommodate content and feature growth?

Also, maybe just because I'm new, I don't have a great feel for what kinds
of ability and commitment people are able to offer. Maybe those interested
in working on the site could give an idea of their areas of expertise and
how much time they have to chip in? I'll start :) I help run a
moderately-large nonprofit's website (www.ncpc.org), and we use Plone. I'm
comfortable with installation and configuration, product design (via
ArchGenXML), and some skinning. I'm not a designer, but if handed a design,
I can turn it into ZPT and CSS. I do have some time over the next month that
I could dedicate to this, and will be happy to volunteer for tasks as we
determine them.

Best,
Matt

On 9/18/07, Martijn Faassen <faassen at startifact.com> wrote:
>
> Hi there,
>
> It's clear from the earlier website thread that Plone seems to have some
> volunteers from within our own community. This, and the fact that Plone
> is a mature system, weighs strongly in favor of Plone in my mind.
>
> [I do by the way hope to hear from Darryl. He's been rather quiet the
> last few weeks and didn't weigh in on the thread: I hope he's okay and
> just on vacation or something]
>
> Plone volunteers, please organize yourself and distribute tasks among
> yourselves. Let us know the plan. Let's use Sebastian's layout for the
> website! With some luck we could be up and running with a Plone based
> solution by Grok's anniversary next month. :)
>
> That said, I'd like to keep the following options open explicitly:
>
> * Eventually we should switch to a Grok-based solution as we should
> indeed showcase our own dogfood. :) I believe Zope 3, and Grok, are
> great systems to build CMSes in. I therefore have every hope that we'll
> see one or more excellent, mature Grok-based CMSes in the future.
> Sebastian's and Darryl's efforts are great starts already. Let's wait
> and see.
>
> * We should also explicitly allow areas of our website to be made with
> other tools that are indeed in Grok already. A reference site with
> inline commenting features for instance might be a great Grok application.
>
> Regards,
>
> Martijn
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
>



-- 
blog: http://m.odul.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/grok-dev/attachments/20070918/523f795e/attachment.htm