This is a continued story from previous posts, all tagged web app dev.

So this “non-cms cms” is really just a way of layering controls into each page as its rendered (assuming proper logged-in authority.) Some aspects of the structure that make things easier (maybe):

• The system is not intended to work “out of the box” for the client. Configuration and theme building are expected of the web developer, AKA the initial site setup.
• The project/client specific stuff is cleanly separated into theme folders
• Structurally the web developer has control of how many templates and “content module types” are available when the client is adding pages and content. The ability to add new ones means tons of flexibility.
• Content modules can be added/removed and sorted in their columns. Previously added content can be duplicated elsewhere.

And some aspects that I’m worried about:

• All this flexibility will come at a cost to complexity of the final product
• With the site structure so dynamic, too much will be required from database interaction just to render the page.
• I wonder if I’ve made too many tables: pages/page templates/slots/modules/module templates/blocks/texts/images/… requiring to many queries
• I’ve subverted the Code Igniter default URL handling so that even the first portion after the domain name is reflective of the content (and not just the name of a controller) - will I regret this later?

More soon…

Posted in Process, Web App Dev |

You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.