Templating

[jacobconley]

Why?

• Context object, etc
• Programmatic HTML header that I've wanted forever; HTML head convenience methods  #27
• Global layouts, somehow
• [maybe] Easy partials, via AddParseTree

Other questions

Paths? can maybe use runtime.Caller to get template file relative to whatever is invoking the renderer. How to make that optional, or opt-in somehow - maybe a path prefix but that's kinda goofy i reckon

Layouts? My current thinking is that the user can set a layout on initialization (can also update in the routes), and honestly if there's a situation where there are several distinct layouts and enough pages to where it would be too repetitive to specify, the user should create a new server instance. But I should only accept this as an answer if it's easy to clone server instances, which it should be

[jacobconley]

Should we use Buffalo's Plush or the standard golang template package? What benefit do we provide with templating anyways? We could come up with a convenient HTTP routing template system but it has to be extremely opt-in

Golang templates kick ass. Expounding further upon the purpose in the original issue