[Radiant] Radiant replace Pages with Abstract Content Model

[Stephane B.]

Hi,

I've read with interest all above messages as I have the same concern 
about how a model should manage contents.

Simplicity is a key of Radiant, and should remains as this. Now, 
extensions open the way to many new features. Even keeping the interface 
user centric, it's important to deal with the need of extending content 
types. The interface doesn't need to relate the content abstraction, but 
it should exists to allow extensions to easily integrate new content 
types and, more important, to globally manage contents (as for a 
search).

It s a good practice to think the interface for users, as it's a good 
practice to think the model for contents.

Why not making everything a content (pages, assets, snippets,...) but 
keeping the model simple? Is a wiki already exists about an Abstract 
Content Model ?

--
Stephane

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