That seems pretty reasonable if you want to keep things really modular. I say go for it.
On Mar 4, 8:46 pm, Chris <[EMAIL PROTECTED]> wrote: > At my office, we are working to completely rebuild our existing > site,www.sportingnews.com. We have mocked up a rough example of a > page,www.sportingnews.com/nflusing cakephp and we are now ready move on to > building a full fledged cms/blog/forum system. > > My main question is this. We have elements that can be used anywhere > on the site (new clips, recent posts, headlines, etc, etc, the list > goes on for hundreds). Our editors will have the ability to add > elements to pages, move them around etc. > > I would like to know what the cakephp community thinks is the best way > to load all the data needed to power each element. > > Currently, we have one component for every element. That component > operates completely independent from the controller that is calling > it. This allows the element/component to be used by any controller/ > view. The component then builds a data set that we set in the > controller and hand off to the view/element. > > This seems to work, but would like to know if there is a better way of > doing this. > > Thanks, > Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
