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 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 -~----------~----~----~----~------~----~------~--~---
