(initial creation) |
m (removed the generic admonition) |
||
| Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
A Little History (from [http://wordpress.org/about/ http://wordpress.org/about/]) | A Little History (from [http://wordpress.org/about/ http://wordpress.org/about/]) | ||
Revision as of 18:23, 25 January 2009
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
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
== Meets the requirement.
== Partially meets the requirement.
.png){kind=small}
== Does not meet the requirement.
| Requirement | Status |
|---|---|
| Good security record |
|
| Proactive, security minded developer community |
|
| Highly responsive, especially to security issues |
|
| Flexible enough auth system to attach to FAS via the json interface |
|
| RSS |
|
| L10n that doesn't break the translator workflow |
|
| Output for Transifex (PO/POT) |
|
| Content workflow (write <=> edit => publish) |
|
| Internal version control with rollback capability |
|
| Content expiration (automatic) |
|
| Multiple roles, e.g. writer, team lead, editor, publisher, managing editor |
|
| Categorize/tag content for easy base organization |
|
| Search that works |
|
| Be a CMS as a core function, not an add-on |
|
| Handle making certain pages or content areas static/non-database driven |
|
| Must not lock us in. Data should be portable to another CMS. |
|
| Packaged for Fedora |
|
Like to have
== Meets the requirement.
== Partially meets the requirement.
== Does not meet the requirement.
| Requirement | Status |
|---|---|
| OpenID | as a plugin
|
| Good WYSIWYG editor |
|
| Easy to organize content by taxonomy, structured and ad hoc |
|
| Support for draft->review->$foo->publish workflows | could be written as a plugin
|
| Workflow to ship the content for l10n only at certain stages |
|
| Workflow go back to a certain stage if a mistake/error is found in the source-language content by the translator |
|
| Translators have a 'review' step in the workflow for translated content before it is published, so that they can see translations in context |
|
| Modern technology with a vibrant community and likelihood of being popular beyond the next twelve months |
|
| Good federation tools to make it easy to find disparate content through one UI |
|
| One set of things it is great at, not be all things for all people |
|
| Be a modular design (v. monolithic) |
|
| Have an active and large community |
|
| Have support for DocBook | 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 ). Some state 'could be written as a plugin' because it is unknown whether that exists, but the functionality is possible. (usually accompanied by a ).
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.
Contact
- Fedora Contributor: Clint Savage
- WordPress Contact: (at) randomnetworks (d0t) com Joseph Scott