This document discusses the author's experience using the content management systems (CMS) WordPress and Plone to build websites. It provides background on the author and both CMS platforms. It then analyzes differences between WordPress and Plone in areas like content types, user and security features, and typical installations. The document also presents facts from a study of 25 recent projects using each CMS. From this, it derives implications for when each CMS is best suited - WordPress for simpler needs, while Plone is better for more advanced requirements involving multiple content types, workflows and user customization. The author hopes both CMS platforms will continue evolving by learning from each other's strengths.

1. やってみたことわかったこと
Some things I learned through experience
WORDPRESS & PLONE

2. To know the "Right Place" for the CMS's
through experience of Plone / Wordpress
website creation
TODAY'S TOPIC
自分が関わってきた
Plone / Wordpress の
サイト構築経験を通して
CMSの適材適所を知る

3. BACKGROUND
About myself
About Both CMS
About Both CMS and my work

4. About myself
WHO AM I
安田善一郎 Zenichiro Yasuda (@zenich)
Ciel Serein LLC / Surface & Architecture
- 7 years in a main framer as a systems engineer
- Found a small company in 1994
Website creation PM and direction
- Since 2004 independent professional
Website creation, UI / UX direction
BACKGROUND

5. About Both CMS
JUST A LOOK
BACKGROUND
History: Since 2001
- b2 cafelog launched
Recent Version : 4.2.2
# downloaded: 19,645,717
(version 4.2, Yesterday)
History: Since 2001
- First release
Recent Version : 4.3.6
# downloaded: ?

6. About Both CMS and my work
PLONE, WORDPRESS AND ME
BACKGROUND
- Since 2005 (2.0.5?)
- Looking for a good
customizable CMS
- Plone was the one with CSS
Not sure but...
- First time I used was
2007 (2.1.3?)
- Became popular
- It was a blog

7. About Both CMS and my work
MY ROLE IN CMS PROJECT
BACKGROUND
- Requirement definition 要件定義
- System / content planning 企画設計
- Direction for creation ディレクション
- Project management 制作進行管理
←things there +
- Development 開発
= Almost everything (except for design
and markup)

8. DIFFERENCES
Based on my knowledge and experience

9. Based on my knowledge and experience
CONTENT TYPES
DIFFERENCES
Plone has many content types
- News, Events, Page, Folder,
Files, Images ...
Extending / building a new
content type in Plone is not
easy.
Wordpress supports
Custom post types &
Custom taxonomies
Needs plugin to manage them
easier

10. Based on my knowledge and experience
CONTENT TYPES
DIFFERENCES
“Pods cms framework”
is a great content type
management plugin
(Can’t live without it...)
Dexterity (may be)

11. Based on my knowledge and experience
USER ROLLS MANAGEMENT
DIFFERENCES
Plone has a good feature to
make things easier like
Users & Groups, Sharing
optiions
Wordpress has enough
functionality for usual needs
Needs plugin to extend them

12. Based on my knowledge and experience
WORKFLOW MANAGEMENT
DIFFERENCES
Plone has many pre-installed
workflow samples
(I think) Easier to extend
content status / workflow
Wordpress has enough
functionality for basic needs
Needs plugin to extend them

13. Based on my knowledge and experience
SECURITY (ACCESS CONTROL)
DIFFERENCES
Plone takes care of access
control for uploaded files and
search results.
Wordpress can not handle
access to uploaded media
files
Needs plugin to handle them
(may be)

14. Based on my knowledge and experience
DOCUMENT SEARCH
DIFFERENCES
Any files uploaded are
searchable like
PDF, DOC, PPT...
Uploaded files are not
searchable
Needs plugin to handle them
(may be)

15. Based on my knowledge and experience
TYPICAL INSTALLATION
DIFFERENCES
Plone
Python (+ zope / CMF / Five)
Varnish
Apache or Nginx
Usually you have to do it by
yourself
Wordpress
PHP
MySQL
Apache
Many many hosting servers
available. Easy to start.

16. Based on my knowledge and experience
ADMIN SCREEN
DIFFERENCES
Included in the public screen Divided from the public screen
Sometimes advantage, sometimes not. (for both)

17. Based on my knowledge and experience
THEMING
テーマのカスタマイズ
DIFFERENCES
(I think) not easy to start Many resources
- Customizable free themes
- Theming tips
Easy to handle where the files
are located

18. FACTS
A study on recent projects

19. A study on recent projects
LIST UP PROJECTS
Picked up recent 25 projects and made a list
which includes
- CMS name (Wordpress / Plone)
- Website type (Public / Private)
- Number of contents
- Number of content types
FACTS
- Number of review stage
- Number of department
- Number of content creators
- Number of login users
- Number of user types

20. A study on recent projects
WEB SITE TYPE
FACTS
Public
公開
Private
イントラ
Total
Wordpress
Plone
15 2 17
5 3 8

21. A study on recent projects
# CONTENTS / # CONTENT TYPES
FACTS
0
15
1 126 251 375 500
# Contents
# Content
types
Wordpress Plone
15
4000 25000
15

22. A study on recent projects
# LOGIN USERS / # USER TYPES
FACTS
1
2
3
4
5
0 5 10 15 20 25
# Login users
# User
types
Wordpress Plone
25 8080 1000010000 20000

23. A study on recent projects
# REVIEW STAGE / # DEPARTMENT
FACTS
# Department
# Review
stage
1
2
3
4
5
0 10 20 30 40
Wordpress Plone

24. IMPLICATIONS
"Right Place" for Plone and Wordpress

25. "Right Place" for Wordpress
WHEN WORDPRESS IS RIGHT
- Quick start needed
- Not so many content types needed
- Usual Draft -> Publish workflow
- Not so many content creators / department
- Review stage is limited
- Less need of customization according to the user type
FACTS

26. "Right Place" for Plone
WHEN PLONE IS RIGHT
- Many content types needed
- Various workflow needed
- Three or more content creators / department
- Review stage is rather complicated
- Need of customization according to the user type
- Document search functionality needed
- Need of care for uploaded content security
- Intranet content share
FACTS

27. I expect both CMS’s to evolve with
involving good part of each other
I HOPE
Plone, Wordpress それぞれが
お互いのいいところを
取り込んで進化してほしいです

28. Thank you very much!
END
ご清聴ありがとうございました
やってみたことわかったこと
Some things I learned through experience
WORDPRESS & PLONE