Comparing strengths of Joomla, Django and other open source communities with Plone

1. The world outside
Plone
Mikko Ohtamaa
Plone Conference 2010

2. Agenda
• Joomla!
• Django
• Lessons to learn

3. Unfortunately
• No world
• No Drupal
• No Wordpress
• No $harepoint

6. Joomla!
The most popular CMS in the world

7. CMS is a thing allowing
you to edit your
website using your web
browser

8. • Open source
• Forked from Mambo (commercial)
2005
• Open Source Matters Inc.
• Runs on Linux+Apache+MySQL+PHP

9. Features
• Admin interface
• Article content
type
• WYSIWYG
editor
• Through-the-
web template
and CSS editor
• User manager
• Two-state
workflow
• Menu editor
• Plug-in manager

10. No-features
• No folders
• No permissions
• No sharing, roles
• No “you-name-it”

11. Demo
http://ploneconf2010.cloudaccess.net/
administrator

14. Core developers
Component
providers
Integrators
Site users
Hosting

17. “They could not stand
Joomla”

18. [20:25:50] x: moo: we moved
from Plone to Joomla. 3 years
on Plone with no hacks.
[20:26:04] x: Problem with
plone is no forums with email
support

19. Django
The web framework for perfectionists with
deadlines

20. Write web
applications
Pythonic way
You don’t need to know SQL

22. Python
development
is fun

23. Python
development
is fun
Django
development
is fun

24. Python
development
is fun
Django
development
is fun
Plone
development
is not fun

25. Features
• Object-relation
mapper (Python
objects in SQL
database)
• Template
engine
• URL mapper
• Forms
• Admin interface
(automatic)
• User manager
• Applications
(extensions)

26. No-features
• No default templates (excl. admin)
• No viewlets
• No traversing (folders), no hierarchy
• No registration

27. Demo

28. Clear path to become a developer
TextTextTextText

29. High quality
reference manual

31. “Plone for web sites,
Django for web
apps”
-Jazkarta

32. CMS on Django
• Lighting Fast CMS by Kai Diefenbach
• Django CMS by Divio
• Various others, especially in-house CMS solutions

33. Issues
• Heterogenous applications
• Subclassing / variations
• Extending admin interface
• Integration story (buildout is coming with Django
packages?)

34. Lessons leart

35. http://www.flickr.com/photos/dunk/498668317 - person in the picture is not related and the picture is only for descriptive purpose
Django developers 2010
Plone developers 2004

36. Django developers 2016
Plone developers 2010
http://www.flickr.com/photos/postbear/3681945685 - person in the picture is not related and the picture is only for descriptive purpose

37. Plone developers 2015
http://www.flickr.com/photos/limonada/14705232 - person in the picture is not related and the picture is only for descriptive purpose

38. Zope tools
are not fun

39. Reference
manuals rock
if someone in Plone community dares to say me
“Check it from the source code”...

40. Reference
manuals rock
if someone in Plone community dares to say me
“Check it from the source code”...
... I teach the person some Finnish

41. Revenue > support >
quality
Components rules

42. • http://linkedin.com/in/ohtis
• http://twitter.com/moo9000
See you on the
other side
http://www.flickr.com/photos/flydime/4671890983

43. Plone needs menu
manager