4 ms·
Care to go into more detail? How are you handling storage, deployment, frontend. How useful are Shakespearean templates?
by minikomi 12y ago
Care to go into more detail? How are you handling storage, deployment, frontend. How useful are Shakespearean templates?
- dllthomas 12y agoWell, I've a couple projects on Yesod, with some variation, but I'll focus on the one that has users outside my family. Storage is Postgres; deployment is some overly specific (and slightly too manual) scripts I put together before Keter was mature (and haven't touched since); front end is mostly flat HTML generated from Hamlet (or markdown, through pandoc), gussied up with some JS where appropriate, but definitely more of a progressive-enhancement approach than a single page app. With regards to Shakespearean templates, the languages for JS and CSS (Julius and Cassius/Lucius) are - in practice - of only mild use on their own. Hamlet is a bigger win - and, in particular, the ability to package up all three into a single widget to be embedded in arbitrary Hamlet, is great. And all the type safety is a nice bonus. One thing it does need is more exhaustive documentation - I don't think there's anywhere that actually specifies the "embed tag attributes from this list" or "generate a URL with parameters" sigils, save the source and mailing list. What documentation does exist is pretty solid, mind you, there's just some omissions.
- minikomi 12y agoThanks for the reply. I've done a cursory run through of the "book", and wondered how close it was to an actual use of the framework in development.