1. How to choose an
open source CMS
by Nate Aune (@natea)
presented at BarCampBoston5
MIT Stata Center
April 17, 2010

2. What are your
website goals?
• Improve your SEO
• Make it easier for people to add/edit content
• Create a document collaboration space
• Provide content in multiple languages
• Capture leads and post info to Salesforce
• others?

3. Popular OSS CMSes

4. Important considerations

5. Important considerations
• Community: resources, mailing lists,
events, approachability

6. Important considerations
• Community: resources, mailing lists,
events, approachability
• Extensibility: how many add-ons are
available? how mature are they? are there
add-ons available for what you need?

7. Important considerations
• Community: resources, mailing lists,
events, approachability
• Extensibility: how many add-ons are
available? how mature are they? are there
add-ons available for what you need?
• Scalability: if you expect your site to get a
lot of traffic, will the system easily scale?

8. Important considerations
• Community: resources, mailing lists,
events, approachability
• Extensibility: how many add-ons are
available? how mature are they? are there
add-ons available for what you need?
• Scalability: if you expect your site to get a
lot of traffic, will the system easily scale?
• Language: PHP, Python, Ruby

9. Important considerations
• Community: resources, mailing lists,
events, approachability
• Extensibility: how many add-ons are
available? how mature are they? are there
add-ons available for what you need?
• Scalability: if you expect your site to get a
lot of traffic, will the system easily scale?
• Language: PHP, Python, Ruby

10. Idealware’s
OSS CMS report
http://bit.ly/osscms

12. http://cmsmatrix.org

13. Conduct evaluation of
software
• Each CMS can be downloaded for free
• Put it in front of your non-technical users
• Ask a question on the mailing list or IRC

14. Engage with a vendor
• Guidance on which add-ons to use / which
ones to avoid
• Set things up in a best practice way
• Assist with training your staff

15. Why Drupal, Joomla,
Wordpress?
• Wordpress is a good CMS for blogs
• Joomla! is a good CMS for basic websites
• Drupal is a good CMS for community sites

16. Why Plone?

17. Why Plone?
• Python is a nicer language to work with than PHP

18. Why Plone?
• Python is a nicer language to work with than PHP
• Snapshots of configuration information with GenericSetup

19. Why Plone?
• Python is a nicer language to work with than PHP
• Snapshots of configuration information with GenericSetup
• Repeatable deployments with buildout

20. Why Plone?
• Python is a nicer language to work with than PHP
• Snapshots of configuration information with GenericSetup
• Repeatable deployments with buildout
• Security is the best of any OSS CMS

21. Why Plone?
• Python is a nicer language to work with than PHP
• Snapshots of configuration information with GenericSetup
• Repeatable deployments with buildout
• Security is the best of any OSS CMS
• Built-in scalability with Zeo

22. Why Plone?
• Python is a nicer language to work with than PHP
• Snapshots of configuration information with GenericSetup
• Repeatable deployments with buildout
• Security is the best of any OSS CMS
• Built-in scalability with Zeo
• Very capable document management system

23. Why Plone?
• Python is a nicer language to work with than PHP
• Snapshots of configuration information with GenericSetup
• Repeatable deployments with buildout
• Security is the best of any OSS CMS
• Built-in scalability with Zeo
• Very capable document management system
• Multilingual and unicode support is excellent

24. Why Plone?
• Python is a nicer language to work with than PHP
• Snapshots of configuration information with GenericSetup
• Repeatable deployments with buildout
• Security is the best of any OSS CMS
• Built-in scalability with Zeo
• Very capable document management system
• Multilingual and unicode support is excellent
• Great community!

25. Thanks!
Nate Aune - natea@jazkarta.com
Twitter: natea
Website: www.jazkarta.com
Blog: blog.jazkarta.com