Re: ogo website redesign

> > I don't have too much time right now, but a few thoughts (most I
> > mentioned in the past).
> > - there should be a mockup. do not invest too much work
> >    before you know it will be accepted.
> > - personally I thought about doing the OGo site like the
> >    SOPE/old-SOGo site (just use a styleshout template, use my
> >    StaticCMS publisher).
> > - I haven't seen a FOSS CMS yet which I like :-/ 

Yea, I feel the same way.   Actually I rather like Mojoportal
<http://www.mojoportal.com/home.aspx> but that is like swatting a fly
with a bulldozer for most use-cases.

> > I would like to avoid the PHP hell if possible.

As the admin of a very large and complex LAIP site (Linux, Apache,
Informix/DB2, PHP) I can second the vote that the long-term maintenance
of the PHP component of of the LAxP stack is pretty darn gruesome.  This
is why many (nearly all?) hosting providers still run antique versions
of PHP; their forward compatibility is pretty shaky.  And PEAR/PECL can
get to be almost 10% as bad as Perl's CPAN [What only 10%?  Everything
is relative: nothing is as bad as CPAN,  I'd choose
Windows-For-Workgroups DLL hell over CPAN!  In some language somewhere
CPAN must mean: Updating-Will-Break-Everything.]

Not that there aren't upsides to LAxP, but the easy-up-ness is paid for
later.

> > - I love tools which generate a static site. Maybe this
> >    one: http://site.ringce.com/products/hyde/hyde.html ?
> > Preferences mostly. I probably wouldn't refuse some Typo3 or Joomla
> > setup, but those are certainly '-' points.
> > Be prepared that the work might be rejected, we won't accept something
> > just because it was done by some volunteer! Hence: *mockup*!!
> > Also consider who is going to maintain the website when its in place!
> > (Frank certainly won't admin a Joomla site!) I would like to avoid the
> > Plone 'situation' ;-/
> > I know, its a bit discouraging :-> We definitely need to improve the
> > website and help would be very welcome. But lets not get 'bloated'.

I can't image this being a site with more than a dozen or so pages.
With a handful of people who have perform modifications.  If editing is
easy that is a plus since it makes it more likely to happen.

> I got that point, make it as nice as possible but keep future maintenance as 
> simple as possible too. E.g. a website update should be as simple as a svn ci 
> command. 
> before implementing anything, we will propose some designs, layed out in gimp 
> or sth. like that, and try to stick to some CSS stylesheets.

Excellent!

> Adam, when you have figured out, how to set permissions on plone so that a 
> group can edit a page, could you setup one, and post a link to it here, or 
> let me know, and I'll setup one.

Actually you can create a page if you want and then I can go in and edit
the permissions [I'm pretty sure].

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss