Move view logic out of templates about wintersmith

[stephenallred]

Sounds good. I guess the view plugin's render method would have the same parameters as the render method on the content plugin currently?
How would the processed content be exposed to the templates?

Having to encode data processing logic like date ordering in templates has been the only negative I've had using Wintersmith (otherwise it's been brilliant, great work!).

[jnordberg]

Yeah, the processed content would be exposed to the templates by the view, the default view plugin could just be something like:

pageView = (plugin, locals, contents, templates, callback) ->
  template = templates[plugin.template]

  locals.page = plugin
  locals.contents = contents

  template.render locals, callback

[gmaclennan]

Would this allow a view plugin to be written to expose processed data in the content tree? If a template could access "pre-processed" data in the content tree, like in Jekyll, it would simplify template logic and lower the barrier for getting started with Wintersmith.

Would it be possible to develop a paginator with a pageView? Or would this need a different effort?

[jnordberg]

Boom