Simple - if you're starting from scratch, seriously start over and rethink a lot of the fundamentals.
Mambo's idea of what content is and how it should be organized within a CMS is very outdated and short sighted. Joomla's been making a valiant effort to modernize the Mambo codebase, but it still suffers from several of the same fatal flaws in terms of execution. Why in the world can I only organize content 2 levels deep? Why can I only add content to a single category? In addition, it would be wise to look into broadening Mambo's idea of "content". Drupal does a pretty good job of making it easy to create several different content types (ie blog posts, news items, products, etc) and handle them in different ways without having to make very literal "sections" Why are the security permissions hard coded? I know Joomla's in the middle of a really messy migration to a proper ACL implementation, but they're not anywhere near close yet. Security roles should be flexible, customizable, granular, and hierarchical. Mambo's 8 years old now and while it may be tempting to give Mambo's users something very familiar in execution, you'd just be doing the project a disservice by ignoring the vast innovations that have occurred in the CMS space since Mambo was originally architected. There are lots of good CMSes on the market - both commercial and open source that are doing a lot of really interesting things these days. Do your research, take all the lessons learned from Mambo development over the years and get crackin! Before writing a line of code, you should put a lot of thought and time into the database design. Many fundamental design choices will be made at that point which will be hard to go back on once you've written a significant amount of code. The more planning you do, the better the end product will be. Good luck! - James On Nov 19, 9:47 am, andphe <[EMAIL PROTECTED]> wrote: > Hi all, I'm on Mambo Dev team, and we realize that while we are > planning our major rewrite of Mambo based on CakePHP, we are not > hearing what the CakePHP community have to say. > > Specifically it would be good to have a brainstorm here, about what > the CakePHP users/developers expect on a cake based CMS. > > So, go ahead, lets have fun.... > > Andrés --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
