BootstrapRoadmap

current issues with roadmap:

• where does the user and user permissions integration come?
• version number is a left hand extraction, should be updated or deleted.

As a starting point we will take the current IsshenCms, remove all sub-modules and sterilize any customer specific additions, so that a basic clean slate is had. This will be Ansuz v0.1. This is now completed

Since the code base is fairly old (written in Rails 1.2), the next step will be to update its dependencies to current versions, including rails (edge), and freeze them to the app, so a turn key solution to cms can be had. In this stage we will also go overthee admin module and make it work. This will be Ansuz v0.2.

The next step will be to integrate external packages, so far these will include the current version of the following:

• silk sprite icon package
• prototype
• possibly some user interface engine such as YUI or Blueprint
• Versioning will be merged from Isotope’s CMS
• (optional) FCKEditor interface will be merged from Isotope’s CMS
• (optional) Auditing will be added from acts_as_audited

This will be Ansuz v0.2.5

Following external package integration, a test suit, written in rspec, will be produced for the entire package. This will be Ansuz v0.3, aka alpha1.

The end goal is to have the CMS be an engine, we will start with it acting as a rough rails application. once this is done, gems and other such will be unfrozen, then listed appropriately so that rake gem:install will do its magic.

The admin section will be the only part that is not a plugin, it will reside at /admin. this part will allow an administrative user to enable and disable any installed plugins on a per page basis.

Aside from basic content presentation, the content part should have no other function. It, and all its children, will be located at /pages/*

Using this hard typing of /admin and /pages we hope to reduce the number of possible url collisions to top level plugins.

For a list of plugins to be eventually implemented, see PlannedPlugins