I think it's a great idea. However, with the number of plugins that you are listing, it's beginning to sound more like Joomla/Drupal which you can already integrate Cake code using the projects Jake/Drake. Mambo are rewriting their project in Cake so maybe you'll be getting the kitchen sink version then.
But for now, I believe the real basics incl. user management and CMS (or blog) would be a real help. Not for the knowledgeable Bakers, who have already rolled their own, but the wannabe Bakers who could just download the most basic app which would encourage them with a 'flying start'. I am learning Cake myself and it is taking so many hours that I'm already down-scaling my plans and looking at other solutions. It seems such a struggle. Even now there are posts mentioning problems with the Blog tutorial, why not give people something which just works, it would be so encouraging to those wanting a quick start. I think it would make a massive difference to the promotion of Cake and thousands of new users might be brought into the fold as they gave it a try. Well, it could only help, couldn't it? On Nov 23, 6:50 am, keymaster <[EMAIL PROTECTED]> wrote: > Well, finally starting to plan what I really should have done some > time ago.... organize an application boilerplate which can be reused > from client to client. > > Just an attempt to be a little more efficient in development, DRY > style. I'm sure many of you have thought the same thing at some time. > > So, in thinking of all the things most clients would need, I came up > with the following list which would go into this boilerplate: > > user management, > ajax support - turning off debug info being displayed during ajax > request, > site offlining, > cron dispatcher, > session expiry management, > access control, > input/url sanitization, > admin panel generation, > cms plugin, > catalog plugin (ie. search, list, detail), > cart plugin, > all the useful omponents/helpers/behaviors and tricks that I can find > on the bakery or wherever, > etc. > > Then as each new client comes along, I pop in the boilerplate app > folder, and in a plug-in I would put the client specific code. That > way, if I ever update the boilerplate, it is easier to migrate over. > Just put in the new boilerplate app folder, and copy in the client > plugin. > > With this lofty goal in mind, I thought I would open up to the > community and see what other people's thinking is. > > What would you put in your boilerplate, and how would you structure > it ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
