Jacob Burkhart wrote: > What about also unifying Snippets and Layouts under a single abstract > model? > > In which case this is no longer true: >> Actually the commonality is: >> >> - available through a url >> - updates the response > > The commonality is simply "user editable content"
Hmm, I do not really see snippets and layouts as content, but they certainly could be and you could even give them a URL. I mean you would give a CSS file a URL or images that are embedded in an article. Why not do the same for layouts and snippets. In fact when using server-side includes, that is exactly how you include layouts and snippets, via URLs. > For example: "Spotlights". I can imagine an extension for managing a > collection of spotlights and setting up rotating spotlights, (And it > could even do things like manage banner ads) But underneaeth it should > use the same Model and the same R:tags that Sinppets, Layouts and Pages > use. And that model should be called Content. Spotlights? I assume you are not talking about the ones used in stage performance ;-) Cheers, Oliver
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
