How CMS architectures affect dev. communities

Julian Egelstaff (29.Feb.2012 at 13:15)
Talk at ConFoo 2012 (English - UK)

Rating: 5 of 5

There are many different kinds of content management systems out there, and from the outside, they might look similar, but under the hood, their architectures are often quite different.

What effect does this difference have on their communities? This presentation will argue that the effect is quite large.

We will examine the architecture of three different CMSs: Drupal, ImpressCMS/XOOPS, and TikiWiki. They represent three very different architectural approaches, from highly modular (Drupal) to monolithic (TikiWiki). Arguably, the nature of the communities around each CMS can be attributed largely to their architecture, and the kind of participation it encourages.

This presentation will include a detailed technical examination of how the CMSs function, some knowledge of PHP will be an asset but not required. The balance of the discussion will be around the communities, and will not require technical knowledge.

Who are you?

Claim talk

By clicking this button you are declaring that you are the speaker responsible for it and a claim request will be sent to the administrator of the event.

If the claim is approved you will be able to edit the information for this talk.

Are you sure?

 
Comments closed.

Comments

Rating: 5 of 5

29.Feb.2012 at 14:45 by Renoir Boulanger (17 comments)

I enjoyed it very much. I think to have other languages CMSes comparsion could also be usefull.

Speaker comment:

02.Mar.2012 at 14:02 by Julian Egelstaff (2 comments)

Thanks Renior! The presentation is available here: http://prezi.com/bemzj02mmypm/how-cms-architecture-affects-dev-communities/

I worked hard to make it stand alone and make sense when viewed by itself. I hope you like it.

--Julian

© Joind.in 2014