Make "draftability" easy to convey to other entities

[ewinslow]

Is this as easy as extending the blog class right now? In any case, that would feel weird to me in some cases. Perhaps a slightly more general class would be useful.

[cash]

It has nothing to do with the class ElggBlog. It is custom code in the save action and the page handlers. There is probably code in the views that keys off the draft/published status as well.

To support generalized draftability, we would need to have a standard piece of metadata to store this state. We could control access to it through the access id rather than adding the metadata to the page handler queries. That limits the effects to the actions and views. You might be able to pull it out of the actions if you keyed off of the create event. We could add an input/draft view so that the field name is always set.

[cash]

I had a thought last night about this. What we're really talking about is providing a mechanism to add CMS smarts to our objects: versioning, publishing, translating. This could be built into the data model or we could layer this on top of Elgg. The second option could be implemented by serializing an object and storing it as annotation (both pages and blogs use annotations to store descriptions). This could be implemented by the ElggObject with a Draft interface.