e59b0a1c88
They work fine. But I had to go to a lot of trouble to get Yesod to render routes in a pure function. It may instead make more sense to have each alert have an assocated IO action, and a single route that runs the IO action of a given alert id. I just wish I'd realized that before the past several hours of struggling with something Yesod really doesn't want to allow. |
||
|---|---|---|
| .. | ||
| configurators | ||
| dashboard | ||
| documentation | ||
| notifications | ||
| sidebar | ||
| actionbutton.hamlet | ||
| bootstrap.hamlet | ||
| page.cassius | ||
| page.hamlet | ||
| page.julius | ||
| README | ||
These are template files for the git-annex webapp. They use the Shakespearean template library, which is documented here: http://www.yesodweb.com/book/shakespearean-templates Note that for most of the templates, it will use files ending in .hamlet, .julius, and .cassius if they exist. So if you need to add CSS, or javascript, you can create the missing template files.