[Radiant] Radiant replace Pages with Abstract Content Model

[Jacob Burkhart]

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"

If Pages, Snippets, and Layouts all made use of the same underlying 
"content" model, then this would give additional flexibility to 
extension authors to write other kinds of "content" also using this 
model.

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.

Jacob

-- 
Posted via http://www.ruby-forum.com/.