Horde Website Reorganization

Goal: reorganize the Horde website to combine wiki.horde.org, dev.horde.org, bugs.horde.org, the documentation parts of pear.horde.org, and www.horde.org. The cvs browser will stay at cvs.horde.org (or possibly in the future svn.horde.org or source.horde.org), and the PEAR package interface will remain as pear.horde.org (or possibly packages.horde.org). Everything else will be combined into one website.

This project will initially imply dropping web mirrors of www.horde.org. FTP mirrors will be unaffected, and it's possible that we will get back to a mirror-able architecture at some point in the future.

Bugs

http://bugs.horde.org/ticket/5274

http://bugs.horde.org/ticket/5678

http://bugs.horde.org/ticket/5344

http://bugs.horde.org/ticket/5343

http://bugs.horde.org/ticket/6325

http://bugs.horde.org/ticket/6670

http://bugs.horde.org/ticket/6355

People

ChuckHagenbuch is leading this project and really wants help, especially from anyone who can offer design work.

Description

We want to collect all parts of the Horde site, instead of the current status of things being fractured between the website, dev.horde.org, and the wiki, and people not having a great way of finding useful information in the wiki.

We will create three main logical areas of the site:

• Developers
  • Administrators
  • End users

We don't have a lot of end user content right now; it's possible that area could be dropped?

Questions raised by this include: where do we store the master docs, CVS or the website? We can automate the process either way - either have make-release.php pull down files from the website, or have a cronjob to update the website from CVS. We could write a renderer for rST docs for the website, and store them there.

The CMS

We need some sort of CMS to manage the content of the site and to make some areas user-editable like the current wiki. We may adopt an existing CMS, or we may adapt some of our own existing code. I propose that we create a new app similar to Wicked and the old Giapeto app, with the following feature list:

• Support for different page content-types (wiki, HTML, rST)
  • a GUI HTML editor for html content pages
  • inline preview (instead of wicked's popup - can just be an overlay)
  • permissions like Wicked
  • implicit or explicit hierarchies based on / as a separator
  • use Horde_Routes for URL management
  • use Rdo for data classes
  • store versions of content like wicked does

---

Back to the Project List