Fifteen Things That Rock in Plone 3.0

Alex Limi’s session on Friday at PloneConf 2006. Goal is for release in Mar 2007. I am capturing it as Alex is speaking.¬† Plone is the most powerful CMS, I know. You can find¬† more info about this conference in PloneConf Wiki.

  1. Versioning (History of modifications, replaceable backend, reverting rivisions, diff between revisions)
  2. In-place Staging( Lets you to work on one piece while another is live)
  3. Locking (Uses WebDAV semantics, stealable locks, tells you who locked it, and how long ago)
  4. Easier Sharing (simplerUI)
  5. Link Integrity (Tracks internal link dependency, warns if you delete resources used by other resources)
  6. Generalized Previous/Next (on documents and other resources)
  7. Fieldsets (
  8. Content Rules Engine (Pluggable, UI for admins to respond to events, really cool for categorizing content etc)
  9. Portlets Engine (UI for managing portlets, infrastructure to write advanced portlets)
  10. Indexing support for Word/PDF (out of box)
  11. OpenID Support(decentralized loing/identity system, lets you use URL as a login, in use by sites like LiveJournal, Technorati, plugins for WordPress, MediaWiki)
  12. Workflow improvements (Workflow control panel, web publishing, community, intranet and internet workflows)
  13. All new features using Zope3 (Alex says Plone3 loves Zope3)
  14. Better markup support (wiki syntax support for all markup, New formats Textile, Markdown)
  15. AJAX Support (in-place editing, inline validation, improved UI and widgets, makes Plone more efficient to work with)

Notes
Portlets in Plone currently are just templates. Folder,User, Group

2 thoughts on “Fifteen Things That Rock in Plone 3.0”

  1. I know people who build websites out of WordPress (especially since WP allows group blogging). It lets you store different types of assets – pages, images and other files.

    It depends on which features of CMS you need. It does not have a workflow (useful if there is an editor for all content. Here are some limitations but can probably overcome (I am not familiar with the architecture of the product).

    – No workflow (but can probably be added,if you are hosting it)
    – No versioning (Can probably interfaced to subversion or some other similar product)
    – User defined content types (can be built on XHTML+ microformats since they already have done XFN)

    You may want to look at CMS matrix http://www.cmsmatrix.org/matrix/cms-matrix for more ideas.

Comments are closed.