I think that using a CMS would be an excellent idea for the reasons
previously stated. I'm not dogmatic about using any particular CMS; however,
I have used Joomla (PHP) and know how it works. I originally chose it for
its ease of use; I think it would serve our needs quite well.

Please let me know if you guys think Joomla is a good idea, or if there is
another CMS that would work better for us. Then, we could get started
setting up the CMS (on whose server?).

Rex

> On Sun, Mar 23, 2008 at 1:09 PM,  <[EMAIL PROTECTED]> wrote:
> >  Today it's a lot of php-scripts, and I don't even know who (besides Lars)
> >  that is familiar with it's structure. Do we want to stick with PHP and
> >  just make changes to the appearance, or is it ok for Rex to also change to
> >  a different framework/backend?  If so, what kind of constraints do we
> >  have?  Should it be based on Python perhaps?
> >
> >  One that I can think of is that it should be relatively easy for several
> >  people to understand how it works, and to make changes. Perhaps another
> >  constraint is that it should be easy to check out the source code of the
> >  web pages in a different location, or on a different server, to make it
> >  easy to test changes outside of the production site. (Actually, when I
> >  think about this, it seems like one of the more important requirements).
>
> Honestly I think the website shouldn't be completely self made from
> scratch. I would use a content management system, be it Python-, PHP-
> or RoR-based. I personally have worked quite some times with Typo3
> (PHP) and think that this is a great system that offers a lot of
> functionality.
>
> A CMS offers the big advantage that most of the people will be able to
> edit contents without having to learn a certain programming language.
> Further I think a lot of CMS have some sandbox built in where certain
> features and/or contents can be tested outside the production
> environment.
>
> Having a look at www.lyx.com, I don't see very much dynamic content.
> Everything looks pretty static -- the only thing that gets updated
> frequently are the new and download section (and the (external) wiki
> of course). So, lyx.org looks to me like a typical candidate for a
> standard CMS.
>
> I recommend that the people that will put the new website online
> should state their favorite CMS, that they have worked with already
> and then you can decide which is the approach that minimizes the
> initial effort and maximizes the latter ease of use.
>
> Dominik
>
>

Reply via email to