Design and implement DisplayPackager

[aplayford]

DisplayPackager will make it easy for news organizations to switch the underlying base templates that power a DisplayFactory page. In addition, this should provide a home for any other sitewide settings that control display and require admin toggles.

For now, that might be as simple as providing a custom template path for a project's page to extend. But we should think about what other settings might be useful here down the road. (Memcached-based caching, for example?)

[jeremyjbowers]

I'd like to pitch in on this.

[aplayford]

Please! Here's the extent of my thinking on this, which you are welcome to improve:

• Users should be able to quickly and easily customize a display to fit within their existing CMS look and style. That should probably be done by them writing a small template, which DisplayFactory templates inherit from.
• A site should be able to have multiple wraps. For example, washingtonpost.com vs Washington Post Politics.
• The DisplayPackager model could point to that template file, so web producers can "pick" the site's style as long as a developer has gone in and created the right base templates in advance. (Web producers probably don't need the ability to add DisplayPackagers, so the hard work can be done in code.)
• We'll need some fancy view logic or smart template tags to make that magic inheritance happen.

What I don't know: How this relates to analytics and ad embeds, which might need to be per-project (but otherwise would seem to fit naturally here).

[aplayford]

And Jeremy, if you want it, I am happy to relinquish the ticket; I took this yesterday in lieu of writing a description but I have attachment to this over anything else.