This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex

1. CMS selection

This goal is completed. The work follows at GnomeWeb/CmsSetup

And the winner is... Plone! After a lot of discussion and reviewing, this seems to be the most appropriate CMS for the revamped www.gnome.org here and now. The second option in this tight final has been Midgard, the CMS powered with GNOME libraries. The reasons for choosing Plone rely more on people than code, since both tools could reach all the requirements with hacking and good will.

Three other candidates were dismissed previously and we needed very good arguments to do so. The localization recommendations made by the GNOME i18n team were crucial in the selection. See why not TikiWiki and why not eZ Publish or Drupal. Something learned in detail during this process is that apparently simple tools can match your requirements if you have the knowledge and the resources to do so. At the end this is a reason why we love free software so much.

Thanks to all the people that invested time willing to find the most appropriate CMS for www.gnome.org. Plone/Python hackers and anybody interested in contributing to the wgo revamp can join us at gnome-web-list. RamonNavarro is leading the Plone implementation.

All of the ab ove belongs to the CMS selection process

1.1. CMS requirements for www.gnome.org

This is a list of categorized requirements for the CMS system that will serve www.gnome.org. If you recommend a CMS check this list against its features.

More at GnomeWeb/CmsRequirements/CmsTest

See also GnomeWeb/PlatformIssues

1.2. CMS Platform

Please provide the following info about the CMS candidate

1.3. Security

1.4. URLs

1.5. I18N

1.6. Authoring

1.7. Markup

1.9. Feeds

1.10. Theming

1.11. Expertise

There should be enough expertise in our community to:

1.13. Backup


2024-10-23 11:10