[thelist] Intranet cms recommendations

Mark MacInnes mark.macinnes at gmail.com
Tue Aug 19 03:19:39 CDT 2008

I've only had proper experience using Joomla, and this was several months
ago so things may have changed now. My experiences were that Joomla is a
very comprehensive system and the core functionality is done very well.
Templating the core functionality is relatively straightforward. The
difficulties arise when you start using community generated
plugins/components to extend Joomla. In most off the plugins/components that
I used, the HTML was entwined with the PHP code. This made is extremely
difficult and time consuming to style and design the site the way we wanted.
It also made it difficult to customise. Joomla also has a significant
learning curve to get to a proficient level. But then I think that is the
same with just about every decent quality CMS anyway.

I think Joomla pretty much matches your requirements, although instead of
vendor/company support it is community support. Plus, there are lots and
lots of tutorials and books about Joomla. It all depends if you intend to
use plugins/components to extend it, as I think that is where it could all
fall down.


2008/8/19 Martin Burns <martin at easyweb.co.uk>

> On 19 Aug 2008, at 00:47, Paul Bennett wrote:
> > * clean front end code
> > * clear separation of content & presentation in templating
> > * basic workflow (edit, authorise, publish)
> > * wysiwyg page editor
> > * well documented, extendable code base
> > * flexible site structure (doesn't tell us where things MUST go too
> > much)
> > * open source preferred (LAMP stack but can install other
> > technologies if the solution fits)
> > * vendor / company support if needed
> > * hosted in-house
> > * cheap (this thing isn't going to be saving the world, just running
> > our intranet)
> >
> > My list so far is generally open-source centric, so I'm wondering if
> > I've missed any obvious ones, or if I can have some experiences from
> > people who've installed / configured / used these (or others):
> Of those I have experience in:
> >    * Drupal
> Will do all the above
> >    * Plone
> Will do all the above, but isn't LAMP. It very much has its own (OK,
> *Zope* has its own) way of doing things. Generally needs more
> horsepower to get the same amount done, but provides some really nifty
> APIs, *especially* if you need multi-lingual. Oh, and because it's not
> a simple RDBS backend, getting data in/out is a challenge.
> >    * Joomla
> Should do most of the above - not looked at it for a while. My
> recollection is that it had quite a strict URL schema which may not be
> flexible enough, but that's back when it was Mambo.
> >    * Django
> Isn't a CMS, but a strong application framework with lots of nice
> stuff for publishing. It's Python, rather than PHP. Much of the higher
> level stuff from above will need to be built. But Django's a good
> framework in which to do it.
> I'd also note that pretty much all CMSs will bundle in the wysiwyg
> editor - something like FCKEdit - rather than writing it themselves.
> Cheers
> Martin
> --
>  > Spammers: Send me email -> yumyum at easyweb.co.uk to train my filter
>  > http://dspam.nuclearelephant.com/
> --
> * * Please support the community that supports you.  * *
> http://evolt.org/help_support_evolt/
> For unsubscribe and other options, including the Tip Harvester
> and archives of thelist go to: http://lists.evolt.org
> Workers of the Web, evolt !

More information about the thelist mailing list