Archive:WordPress CMS Option

From FedoraProject

Jump to: navigation, search

Contents

Summary

A Little History (from http://wordpress.org/about/)

WordPress was born out of a desire for an elegant, well-architectured personal publishing system built on PHP and MySQL and licensed under the GPL. It is the official successor of b2/cafelog. WordPress is fresh software, but its roots and development go back to 2001. It is a mature and stable product. We hope by focusing on user experience and web standards we can create a tool different from anything else out there.

2005 was a very exciting year for WordPress, as it saw the release of our 1.5 version (introduced themes) which was downloaded over 900,000 times, the start of hosted service WordPress.com to expand WP's reach, the founding of Automattic by several core members of the WP team, and finally the release of version 2.0.

In 2006 we had 1,545,703 downloads, in 2007 we had 3,816,965!

Benefits to Fedora

For Fedora, WordPress provides many benefits including security, plugins and a large feature set. In addition, many people use WordPress as a CMS these days and there is quite a bit of development focused on WordPress as a CMS.

Project Website

http://wordpress.org

Requirements

(from http://codex.wordpress.org/Hosting_WordPress)

  • PHP version 4.3 or greater
  • MySQL version 4.0 or greater
  • (Optional) Apache mod_rewrite module (for clean URIs known as Permalinks)

We recommend Linux with either the Apache or NGINX web-servers as the most robust platforms for running WordPress, but any server that supports PHP and MySQL will do. If your host doesn't support one of these platforms, and mod_rewrite, you will probably be better off switching to one of the many hosting providers that do offer those choices.

Features

Must have

Checkmark.png == Meets the requirement.

Warning.png == Partially meets the requirement.

Stop (medium size).png == Does not meet the requirement.

Requirement Status
Good security record Checkmark.png
Proactive, security minded developer community Checkmark.png
Highly responsive, especially to security issues Checkmark.png
Flexible enough auth system to attach to FAS via the json interface Checkmark.png
RSS Checkmark.png
L10n that doesn't break the translator workflow Stop (medium size).png
Output for Transifex (PO/POT) Warning.png
Content workflow (write <=> edit => publish) Checkmark.png
Internal version control with rollback capability Warning.png
Content expiration (automatic) Warning.png
Multiple roles, e.g. writer, team lead, editor, publisher, managing editor Checkmark.png
Categorize/tag content for easy base organization Checkmark.png
Search that works Checkmark.png
Be a CMS as a core function, not an add-on Checkmark.png
Handle making certain pages or content areas static/non-database driven Checkmark.png
Must not lock us in. Data should be portable to another CMS. Checkmark.png
Packaged for Fedora Checkmark.png

Like to have

Checkmark.png == Meets the requirement.

Warning.png == Partially meets the requirement.

Stop (medium size).png == Does not meet the requirement.

Requirement Status
OpenID Checkmark.png as a plugin
Good WYSIWYG editor Checkmark.png
Easy to organize content by taxonomy, structured and ad hoc Checkmark.png
Support for draft->review->$foo->publish workflows Checkmark.png
Workflow to ship the content for l10n only at certain stages Stop (medium size).png
Workflow go back to a certain stage if a mistake/error is found in the source-language content by the translator Checkmark.png
Translators have a 'review' step in the workflow for translated content before it is published, so that they can see translations in context Warning.png
Modern technology with a vibrant community and likelihood of being popular beyond the next twelve months Checkmark.png
Good federation tools to make it easy to find disparate content through one UI Checkmark.png
One set of things it is great at, not be all things for all people Checkmark.png
Be a modular design (v. monolithic) Checkmark.png
Have an active and large community Checkmark.png
Have support for DocBook Checkmark.png as a plugin

Explanations

Several of the items above have been noted with 'as a plugin' next to them. This implies that either a plugin exists for the feature (usually accompanied by a Checkmark.png).

L10n that doesn't break the translator workflow

I am unclear as to this reference and what it implies. If there is a document that defines this functionality, I can re-explain it to the WordPress developer, Joseph Scott, and he may be able to give a better explanation.

IRC Interview

This information was gained from a chat with Joseph Scott who works for Automattic and is a WordPress developer. This chat was archived and can be read at WordPress IRC Chat Interview.

Contact