Do we need to rethink article types?

[allanjamesvestal]

The current ones seem like they'd need a bit of review to me.

[myersjustinc]

The existing ones are very much a product of the 'eater's needs at the time that model was written. I'd be up for rethinking them or even making it relate back to an ArticleType model of some sort to make it easier to customize. Other alternatives?

[allanjamesvestal]

I like this idea. But more broadly: can we combine this with #43 and just have a 'types of content' model? We'd only have a few fields on it — probably a M2M to contenttypes.ContentType that were sub-classes of core.Content, a verbose name and an internal (possibly slugified) name.

[myersjustinc]

Sure. The sheer amount of normalization in this project (all over the place, not just here--but this made me think of it) makes me wonder how best to optimize this thing for heavy load, though. There should be a pretty extensive look at Brubeck's caching setup (and query optimization) at some point.