Thanks for the feedback.. > What I see a lot is people looking for a admin backend that actually > works. > A CMS just for the MS. > I think that a fashion way of delivering data to views, and a good UI > work on admin end is what people really seek.
@Rafael, we are aware of the challenge that an usable and accessible backend is, it for sure will get a lot of attention > I guess my ideal cms would be one that didn't use crazy complicated > callback systems with hard to discover override names. Kept many of > the core cake functions, used plain PHP templates with cake's core > helpers, and some extra spice from the mambo team. Supported i18n out > of the box. Allowed the end client to easily do the things they needed > to (update content) and allowed me to do my job (build the darn > thing). @Mark, since we decided to use cakePHP all the spirit of cake will live inside Mambo 5, currently Mambo supports i18n using gettext (the same than cakePHP) but additionally have a component called the Language Manager that allows the user to translate the whole software or modify his translations in any moment. > But you guys know CMS systems probably far better than than any of > us. So I'm sure you'll come up with a good solution? One question is > how are you going to migrate the large code base of contributed > modules (or whatever they are called) into mambo 5? A key question, while we try to keep backward compatibility, Mambo 5 is a total rewrite from scratch and a change in architecture, probably is too soon to say how backward compatible it would be but I guess all extensions will need modifications. > Hi, Andres, take a look at the best features of Wordpress, and you > will have your answer. Clean API, easy theming, and the chance to make > plugins anytime. Just my two cents. @mbavio, Thank you, I'll check wordpress to get your point, currently Mambo supports 4 type of extensions, components = Major extensions, this is the king of extension that do the hard job, so there is components for Image Galleries, Form Generator, Forums, Content, Contacts, Banners, etc modules = Normally help the components to get/give input/output from/ to the user, so you have a menu module, login module, banners module, latest content module, newsflash module, polls modules, etc mambots = Mambots are hooks used to act under certain events (just like wordpress actions), currently Mambo support events for content, system, authentication, search and editors, you can trigger your own events wihtin your components using the API templates = like the Themes on other CMSs, all based on PHP, currently isn't used a template engine, you can have/use more than a single template within your website Probably the terms could change in the way to make it more clear for end users, but this can give you a idea of what currently exists and will be ported. > A huge benefit for the community would be a content repository > behavior. This would be somehow similar to phishys versionable, but > special to content versioning. > > There is a specification for java content > repositories:http://en.wikipedia.org/wiki/Content_repository_API_for_Java > > Java reference implementation:http://jackrabbit.apache.org/ > > And the typo3 team is working on a php implementation (I don't know > anything about the > progress):http://typo3.org/fileadmin/teams/5.0-development/t3dd07-karsten-jcr.pdf > @Timo, thanks a lot for point me to this resource it seems pretty useful > Thanks for sharing information about the mambo development with the > community. Never mind, thank you guys for the feedback, this is a project that can't be build without the cakePHP input. Andrés --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
