The Etomite Blog

Etomite Development Highlights

Upcoming Changes To The Etomite CMS Package

Tentative Changes
This list will grow over time in an effort to convey the direction in which the Etomite CMS project is evolving. Only the general concepts will be listed with the possible inclusion of more in-depth specifics relating to some areas.

• Separation of logic and presentation
• No more frameset for the manager
• Conservative use of AJAX features within the manager
• More modular design implementation
• Combined functionality of front end and back end code
• Separate WYSIWYG editor integration files for each editor
• All new Look-n-Feel
• Skinnable
• Dare I mention multiple site capabilities and possibly multiple servers
• The Etomite Class will be located in a separate file (Done)
• The config.inc.php file will be incorporated into the new index.php file (Done)
• File Manager will be a Plug-In, possibly with multiple candidates
• Most of the current manager components will be stored as snippets
• CVS or SVN code management for better multi-development support

More to come…

Considerations yet to be decided

• Is there a need for IN_ETOMITE_SYSTEM and IN_ETOMITE_PARSER or will being an authenticated user suffice?
• Will having manager components stored in the database have adverse effects on performance or security?
• Is it worth providing site statistics at all or should that task be delegated to other third-party applications?
• Should the manager logging be an optional module rather than fully integrated?

More to come…