To be more specific: Layouts are all of the HTML that the view file's html gets wrapped with. A single theme can have as many (or few) of these as necessary. Elements are shared view files which contain content that can be used anywhere. In your context, these will most likely be non-interactive blog widgets that can be utilized in any combination, like a table of contents. Helpers are similar to elements, but contain php logic (actions) like controllers. In your context, these can be interactive blog widgets like Pages are for static content that doesn't require a controller or model.
Overall, a theme is a collection of any number of these. In your case, an end user's "theme" should consist of: * a single layout (the HTML each blog post's content is wrapped in) * related CSS (probably best to save in the db and either pass to $scripts_for_layout in app_controller or output directly in the layout) If you share app-level helpers and elements as "blog widgets", your end users can just "plug them in" to their layouts. Additionally, you can also give end users the ability to create a layout for the administrative interface, as well. This is where a single theme having multiple layouts can come in handy. -- 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=.
