Comparisons Wiki vs CMS

1. Comparisons Wiki vs. CMS
By
Krishnapriya

2. Presentation Overview
•
•
•
•
•
•
•
What is wiki? and What is CMS?
Features of wiki and CMS
Strengths and weaknesses
Comparison of Features
Common features in Both
Exclusive Features of Plone
Challenges

3. What is wiki?
Wiki : a visitor-edited resource such as an
encyclopaedia.
Example :
Wiki Nature: 1. All wikis start off as a single blank page
2. Pages are created and connected by hyperlinks
3. No ownership of pages; anyone can change the
work of others

4. What is CMS?
CMS : server-based software that holds and publishes all
types of content, and often has multiple options as to
how the website appears and functions.
Example :
CMS Nature: as the CMS creates the page framework and
privileged users can paste content in.

5. Differences between Wiki and CMS
Wiki
1.
2.
3.
4.
5.
Collaborative
No one owns content
Anyone can edit other people’s
work A person owns their post
Perpetual work in progress
Good for collaborative group
work
CMS
1.
2.
3.
4.
5.
Broadcast
A person or an organization owns
their posts
Only author can edit their own work
(others can comment)
Posts are permanent
Good for disseminating information

6. Features of wiki and CMS

8. Plone core
Features

9. Strengths and weaknesses

10. Strengths and weaknesses in Wiki
Strengths
1.
2.
3.
Is completely free to use and
contribute
There is no review before
modifications are accepted
Covers an incredibly broad range of
topics
Weaknesses
1.
2.
3.
4.
Anyone can create, edit, or delete
Wikipedia articles.
There are some mistakes on their
contents since it is open to every
one and people could edit their
articles. So the content is not 100%
reliable. If I am looking for
something important I get some
general info from wikipedia and
double check it from other places.
Incomplete articles exist
high-quality articles are poorly
maintained
Cont……..

11. Strengths and weaknesses in Wiki
Strengths
Weaknesses
5.
6.
7.
8.
9.
Needs a lot of work for a very important article, but
just paring down and have appropriate links to
other skeleton articles might do too.also helpful
search functionality
Mediawiki has loads of hacker level tools - from
other people's extensions to PHP and other
programming tools - but none or very few are ready
to go out of the box.
No support for Image Maps. Would be
tremendously useful. There was one wiki, PHPWiki,
that had them at one time, but MediaWIki doesn't.
No LDAP support / no third party authentication
supportwhich means Yet Another Username and
Password - truly sucks.
Ref: http://www.wikimatrix.org/forum/t359-what-major-disadvantages-mediawiki

12. Strengths and weaknesses in Plone CMS
Strengths
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Object oriented database structure
HTML-5 and CSS3 support
J-query and Ajax based
Dynamic switching languages
Batteries Included
Platform independent
Powerful Workflow Engine
Clustering capabilities
Built-in Image Handling
Pluggable Authentication
World-class Support
Instant, Full-text Searching
Built-in Image Handling
Weaknesses
1.
2.
3.
Single database file
Compatibility problem with add-ons
when migrating to higher versions
Steeper learning curve when you
first start out

13. Strengths and weaknesses in Plone CMS
Strengths
Weaknesses
14.Accessibility Standards Compliant
(support visitors with disabilities, W3C’s
WAI-AA and the U.S. Government 508
standards)
15.Hundreds of add-on products are
available
16.search engine friendly
17.Built on Python and Zope, which are
highly secure platforms,Plone has a
technological edge that has helped it
attain the best security track record of
any major CMS
18. (Plone isn’t vulnerable to SQL
Injection attacks, which are one of the
most common security problems that
affect PHP/MySQL-based)
(Source: Common Vulnerabilities and Exposures dictionary list ).

14. Comparison of Features

15. Wikipedia (Media Wiki)
Plone
Look and Feel:
1.Skins
2.User Styles
3.Printable Versions
4.Auto Number Headings (optional)
5.Generate an automatic table of contents
6.XHTML/HTML 5
7.Human readable url
8.Local url (not available for all lang.,)
9.“Stub” threshold
10.Intra-Page Anchors
11.Automatically turn ISB numbers
Look and Feel:
1.Skins/Themes
2.One click uploads for theming
3.Automatically formatted for printing
4.Auto Number Headings
5.Auto generated table of contents
6.XHTML/HTML 5
7.Human readable url
8.Tiny url
9.Presentation mode for content
10.Cross-platform
11.Simple installer packages for multiple platforms
Multimedia and Extensions:
1.File upload feature
2.Mathematical formulas using LaTeX syntax
3.Automatic resizing Images
4.Easy Timeline (Timeline)
5.WikiHiero (render hieroglyphs from a text written according to the Hieroglyph
coding manual syntax.)
6.Video support by html5
Multimedia and Extensions:
1.File upload feature
2.Mathematical formulas using LaTeX syntax (Warn..)
3.Automatic image scaling and thumbnail generation
4.Timeline (Quintagroup Analytics Tool for Plone)
5.Turn a folder into photo gallery
6.Video support via Plumi
Keeping Track of Edits:
1.Watchlist
2.User Contributions
3.Related changes
4.Side by side differences
5.Real names
6.On-page credits
7.Extended recent changes
Keeping Track of Edits:
1.Versioning, comparing history and reverting content
2.User contributions, personalization, user profiles and folders
3.Link and reference integrity checking
4.Working Copy support + Workflow + Check out (in)
5.Real names
6.Collaboration and sharing
7.Time based publishing
8.Dexterity

16. Wikipedia (Media Wiki)
Structures and syntax:
1.Restricted use of html
2.Editing syntax based on UseMod
3.Namespaces
4.Discussion (Talk)
5.Template
6.Transclusion
7.Link to individual sections
8.Micro format support
9.Subpages
10.Word - extension linking
11.Parenthetical hiding
12.Dynamic data
13.Multiple categories
Editing:
1.Edit toolbar
2.Edit preview
3.Handles edit conflicts
4.Mark edits as minor (user can decide to hide from recent
changes list)
5.Section editing
6.Double Click editing
7.Edit Summary (Shows recent changes)
Plone
Structures and syntax:
1.HTML filtering
2.Support for multiple mark-up formats
3.Namespaces (Folders)
4.Discussion
5.Adjustable templates
6.Portlets engine
7.Link to individual sections
8.Micro format support (e.g., calendars, events,..)
9.Automatic previous/next navigation (Pagination)
10.Word – extension linking (if plone wiki enables)
11.Accessibility compliant
12.Flexible navigation and always-updated site maps
13.Rules engine for content (triggers)
14.Powerful standard content types
15.Drag and drop reordering of content
16.Wiki support
Editing:
1.Easy-to-use, powerful graphical page editor (WYSIWYG Editor:
Kupu, Epoz, FCK editor, and TinyMCE and supports external
editor)
2.Edit preview
3.Automatic locking and unlocking
4.Cut/copy/paste operations on content
5.Inline editing through the web
6.In-context editing (avoids separate admin interface)

17. Wikipedia (Media Wiki)
Spam and Vandalism:
1.Anti-spam features
2.Meta: Spam blacklist
3.Manual: Combating vandalism
Discussions:
1.Talk pages
2.Emailing users
3.Message notification
4.Automatic signature
Multilanguage support:
1.Many Languages
2.Inter language (linking articles in different languages)
a) Each language requires its own database.
3.UTF-8 support
Backend:
1.Database-driven
2.Parser caching
3.Output caching
4.Cookie-based
5.All revisions
6.RSS
7.RDF Metadata
Plone
Security:
1.Field Level Security
2.Localized workflow configuration
Discussions:
1.Discussions and commenting
2.Comment capabilities on any content
3.Mailing system
4.Blogging
Multilanguage support:
1.Multilingual content management
2.Switch to another language (LinguaPlone)
3.UTF-8 support
Backend:
1.Authentication back-end via PAS/LDAP/SSO/Auth_tkt
2.Backup support (hot backup, cold backup)
3.Caching proxy integration
4.WebDAV and FTP support
5.XML exports of site configurations
6.Resource compression
7.RSS Indication

18. Wikipedia (Media Wiki)
Permissions:
1.Different rights for anonymous users, signed in users, sysops,
bureaucrats and developers.
2.Signed in users
a) move and rename pages
b) upload files
c) have and use a watchlist
d) mark edits as minor edits (e.g., typo correction)
3.Sysops (Admins)
a) protect pages from editing
b) delete and undelete pages
c) edit protected pages
d) ban users by IP address
e) Ban users by username (option is enabled)
4.Bureaucrats
a) create sypsos
b) rename users
c) flag bots
5.Developers
a) lock the database
b) Run various maintenance tasks
6.Other Permission schemes (e.g., only signed users can edit
pages)
Plone
Permissions:
Note: May be more permissions available, depending on what
products do we have installed!
1.Anonymous
a) Access content info., (publish state)
b) View (publish state)
2.Authenticated
a) Access content info., (publish state)
b) View (publish state)
3.Manger
a) Access content info., (publish, private, pending,
visible state)
b) Modify portal content (publish, private, pending,
visible state)
c) View (publish, private, pending, visible state)
4.Member
a) Access content info., (publish state)
b) View (publish state)
5.Owner
a) Access content info., (publish, private, pending,
visible state)
b) Modify portal content (publish, private, pending,
visible state)
c) View (publish, private, pending, visible state)
6.Reviewer
a) Access content info., (publish, pending, visible state)
b) Modify portal content (publish, pending state)
c) View (publish, pending, visible state)

19. Permissions in Wikipedia
Anonymous New /Login
Account:
Create/Add
Delete/Remove
Activities:
Block
Unblock
Grant
Revoke
Import
Upload
Rollback
Over sighter
Check user
Rename user
Edit Media wiki Interface
Edit wikimedia interface
Pages:
Create
Read
Edit
Mark changes (Minor)
Purge
Move
Delete
Spl. Pages/ Protected pages
Auto Confirmed
Admin (Sysop)
Yes
Bureaucrats
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes (Protect)
Yes (Semi-protect)
Yes (Protect)
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Stewards

20. Wikipedia (Media Wiki)
Plone
Search and Queries:
1.Full text search
2.What links here (view pages that link to the current page backlinks)
3.Query API (allows scripted access to various metadata)
Search and Queries:
1.Full text and Live search in Portlet
2.Contextual search
3.Advance search
4.Dynamic search results on search page as you type
5.Any search can be turned into RSS
6.possible external search integration (e.g. SOLR)
Techiee:
1.Latest version (1.19.2)
2.PHP
3.MySQL, PostgreSQL, SQLite
Techiee:
1.Latest version (4.2.1)
2.Python/Zope
3.MySQL, PostgreSQL, SQLite, Oracle, ZODB, via Zope
Others:
1.Random article
2.Time zone configures
3.Extension support
Others:
1.Time zone configuration
2.Workflow capabilities
3.Scheduled content expiration and publication
4.Support, development, hosting & training via 300+ providers
5.Free add-on products
6.Geo tagging
7.Sub sites
8.Extensible content types
9.Create your own forms
10.Personal dashboard
11.There is an upgrade path to newer versions
12.Add-Ons support

21. Common Features in wiki and CMS

22. Common Features in Both
•
•
•
•
•
•
•
•
•
•
LiveSearch
Outstanding multilingual content management
Cut/copy/paste operations on content
Easy collaboration and sharing (On-page credits)
Versioning, history and reverting content(Related changes)
Inline editing ( using DOJO editor )
Working Copy support (using svn subversion concept)
Link and reference integrity checking (Related changes )
Flexible authentication back-end (Eg., LDAP support)
Full-text indexing of Word and PDF documents ( Plone directly
supports it using its one of the most powerful features, Search.
Media wiki supports full text search engines.)

23. Common Features in Both
•
•
•
•
•
•
•
•
•
•
•
Collections
Support for the search engine Sitemap protocol
Support for multiple mark-up formats (XHTML- or HTML5-)
Auto-generated tables of contents
Portlets engine (Interface/ Sidebar)
Caching
XML exports of site configurations ( Backing up a Wiki and importing
XML dumps)(Backup)
Content is automatically formatted for printing (Printable versions )
RSS Support
Automatic image scaling and thumbnail generation
Cross-platform

24. Exclusive Features in Plone

25. Exclusive Features of Plone
•
•
•
•
•
•
•
•
Automatic locking and unlocking
Powerful workflow capabilities
Presentation mode for content
Wiki support
Automatic previous/next navigation
Rules engine for content
Time-based publishing
Human-readable URLs

26. Exclusive Features of Plone
•
•
•
•
•
•
•
Resource compression
Powerful caching proxy integration
Drag and drop reordering of content
Localized workflow configuration
Adjustable templates on content
Comment capabilities on any content
Can upload audio/ video files

27. Why and why not Wiki?
Why Wiki
•Easy to use
•Web-based
•Anyone can make changes
• Version control
• free and open-source
Why not Wiki?
•Too open (trust issues)
•Concerns about ownership of content
• Disorganized
•Vandalism and spam
Wikis aren't for everyone. If control is a major issue with the site you're
developing, then a wiki may not be right for your project.

28. Why and Why not CMS?
Why CMS
•
•
•
•
•
•
•
Simplicity of Use
Complete Solution
Content of many different types
can organized and presented in
many different ways
to concern about Trust and
Security
Additional functions via plugins
Content is completely separated
from presentation
For complex workflow and Role
based mechanism
Why not CMS?
• website never has any content
changes
• A CMS must have a webmaster to
oversee security and functionality
issues
• Freeform art-based websites are
not ideally suited to a CMS.

29. Challenges

30. Challenges
• In case of multiple language portals what may
be the landing page of the Main Portal
• What will be the Quality of the Portal
• In case of Crowdsourcing, Authenticity of the
content
• Bringing all the Plone user roles in a single
analytics
• Rate of quality article production
• Concern about ownership of content

31. References
How Wikipedia Works by Phoebe Ayers, Charles Matthews, Ben Yates
Wikimedia foundation 2012-13 annual plan
IEEE paper on Real-time Aggregation of Wikipedia Data for Visual Analytics
http://plone.org/products/plone/features/old/3.0/referencemanual-all-pages
http://www.idealware.org/custom-resources/tips/comparing-open-source-cmsswordpress-joomla-drupal-and-plone
http://simple.wikipedia.org/wiki/Wikipedia:User_access_levels
Wikipedia (Media Wiki) Features:
(http://www.mediawiki.org/wiki/Manual:MediaWiki_feature_list)
Wikipedia (Media Wiki) List of Permissions in detail
(http://www.mediawiki.org/wiki/Manual:User_rights#List_of_permissions)
Plone Features (http://plone.org/products/plone/features/old/3.0)
Plone Features (http://maurits.vanrees.org/weblog/archive/2012/05/brain-stormingplone-features)
Plone Theming (http://www.sixfeetup.com/blog/5-key-enhancements-in-plone-4-2)
http://www.a3webtech.com/index.php/compare-cms-wiki-blog-forum.html
http://en.wikipedia.org/wiki/Wikipedia:Why_Wikipedia_is_not_so_great
Why Use A Content Management System To Develop A Website?
(http://www.superwebgroup.com/why-use-a-content-management-system-to-develop-awebsite/)
Compare CMS vs Wiki vs Blog vs Forum(http://www.a3webtech.com/index.php/comparecms-wiki-blog-forum.html )