I would have to agree with Dr. Sani. You can always pump out a basic cake site pretty quick if they did not want e-commerce but, for me that is a pain in the butt. What I have found is, always try to make plug ins for everything that you can re-use. E-commerce, user login/ auth functions, polls, comments, shout boxes, anything that is not specific to that site. It takes me a while to write a plug in but, well worth it when I have another site to write. I just plug in my user plug in and I don't have to deal with that, etc.
Do the off-the shelf thing and develop those plug-ins, that way next time around, you can unzip a plug in, do a little config and spend the rest of the time making it look fabulous. On Mar 30, 3:05 am, "keymaster" <[EMAIL PROTECTED]> wrote: > I'm in the middle of developing a fair size app for the travel > industry using cake, so am reasonably comfortable at this point with > cake. > > I love it, actually, for what it has taught me, and what it enables me > to accomplish, and am grateful to the skilled and kind developers who > give of their time to make this happen. > > Recently, I've been requested to develop two simple sites for service > businesses. One requires a very basic cms functionality. The other > requires very basic store functionality for 10-20 products. Neither, > at the current time, require huge systems. > > I'm trying to decide which direction to take with these clients. > > On one hand, I can install an opensource cms/shop with a paid template > and within a very short time have a site ready to train them on, and > they can do more than they would ever want to with it. The price would > also be pretty cheap because it is very little labour. However, these > open source products are so overbloated with non-needed features, and > as a result, so much more difficult to support and enhance because of > the code volume, that I am a little apprehensive taking on an elephant > with all the support implications. > > On the other hand, I can develop a cake based system for them. This > route would take longer than delivering an off-the-shelf cms, and as a > result would cost the client more, but in the end I would deliver them > a system much leaner and easier to support and expand. > > This is a classic case of a client who needs some cms functionality, > but not all of drupal or Joomla; or, he needs some ecommerce > functionality but not all of oscommerce or zencart. > > The issue is, I'm not sure what the "right" decision making process is > in deciding which direction to go? What's in the best interest for the > client? > > I'm sure many people are faced with this situation often. What issues > would you consider in making the decision? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
