The Plan

Here are the steps we need to follow to keep the project moving in a positive direction, which is forward.

Step 1 - The Core is Your Friend

The start of Wormhole CMS must be the development of the core. This will be the the single most important piece of the puzzle.

For any project to be successful it must have a solid foundation.

The following things should be accomplished for this step.

  1. Easy to install (along with easy-to-follow instructions for many hosting services) - Ruby on Rails can be challenging for lessor-geeks to install, so installation of the core should be made as easy as possible for future users. During the basic install the central “Chunk” table is created. In addition, a method to update versions will be tested.
  2. A basic “Front-Page” that is displayed when going to the site address.

Features in this step

  • Easy Installation
  • Solid, stable core
  • Central “chunk” table
  • Easy version update
  • First page display

Step 2 - Knock, Knock

In this step we create an admin login and the ability to install, and uninstall, a module. It’s important to note that the admin login will be the beginning of the basic user authentication system.

The following things should be accomplished for this step.

  1. A basic “Admin Page” - Albeit at this point this will be somewhat sparse.
  2. Basic user authentication
  3. Install/uninstall a simple module

Features in this step

  • Admin page
  • Ability for Admin/users to login
  • Module installation/removal process

Step 3 - Who Are You?

Creation/installation of user module

Old Plan

Working on a users extension for Radiant - After finding out how the page caching works this might prove to be more difficult then first thought.

Hold on to your hats. We’re now possibly combining our previous Wormhole design ideas with Radiant to create some sort of hybrid.

Since a lot of data on a website is the same (title, body, post date, etc…) we began the process by wanting a single ”Chunk Table” where most of the data will be stored. These “chunks” will then be identified by a tag as to what they are. A tag for the news extension, one for the links extension, and so on.

As an extension gets called it goes through the chunk table and pulls out its data only.

This will help in many aspects of controlling the data, one important way is in the searching of data available on the site.

I’ll let you know how things are going and which direction we plan to head as the days move along…

Near Future

Extensions (in no particular order)

  • Comments/Forums
  • Downloads
  • Links
  • Gallery
  • Random Quotes

Far Future

An awesome CMS!