From Fedora Project Wiki

DocsProject Plone

Plone is the CMS solution we are deploying for Fedora. It is built on Zope.


  • Flexible way to publish a front page for
  • Content management:
  • Schedule content to publish, expire, archive
  • Organize content (taxonomy)
  • Improved search
  • Granular permissions for content areas
  • Publication workflow:
  • Writer (draft) <=> Editor (technical, grammatical) => publisher (final edit)


1. First iteration installation to serve up the front page and docs

  • Populate with a basic workflow
  • Pull in existing docs (PDF, XHTML)
  • General/initial taxonomy

1. Solve problems and produce second iteration installation

  • Improved workflow
  • Additional docs
  • Improved taxonomy

1. Begin hooking Plone into places to push and pull content 1. Start hacking on the Magic Workflow

Plone Use Cases

DocsProject Specifics

We need to have answers to these use cases and questions. Once we know them, we can start using the Plone CMS to collect and publish work.

  • "I just translated the Translation QSG and it's ready to be published."
  • "I have a DocBook document I wrote but don't want to do the CVS access hoops."
  • "I have a book in CVS and want to give another person permission to edit and publish it."
  • "I have a book in Plone amd I want to give another person permission to edit and publish it."
  • "I have a book in Plone that I want to make available for translation."
  • "I am a packager/developer, and I don't know where I should put my content or how to label it."

Additional Uses

Python-based flexibility and incredible modularity make Plone a no-brainer for many types of community information sharing activities. It is possible to build workflows that interact with SCM, Trac/Bugzilla, and just about every other conceivable part of the project to provide or return content.

Magic Workflow

Imagine:: Click Publish Draft on the Wiki. In the background, the Wiki is converted to DocBook XML, built to XHTML, and posted to the Plone CMS at the start of a workflow as a draft submission. An editor receives an email that a new draft is ready. The editor reads the document, if there are any fixes/suggestions, those are posted, and the writer receives notice of the "denial with suggestions". The writer can edit in the Wiki and republish, which should pick up the same workflow ticket as a new draft on a previous submission. When the editor approves the submission, it is pushed to a publication editor. The publication editor has workflow permission to make actual changes to the text, and a method to push those changes to the XML in the SCM. Once a document is published, the XML source becomes canonical for that version and the PO are made available for translation. A translation follows a similar workflow, with a translation editor in the place of the technical/grammatical editor.

Wiki => XML => XHTML => Plone <=> Editor => Publisher => XHTML, PO

Architecture and Technical Considerations

Platform:: RHEL 5/Fedora Core 6 Plone Version:: 2.9.6-1.fc6 Zope Version:: 2.5.2-1.fc6