I have some similar experience, put here try to be helpful
I am in a team:
1. 1 designer: No experience with Clojure, little knowledge about
programming, but knowing HTML & CSS well
2. 1 fronend developer: No experience with Clojure, knowing JS & HTML
well,
3. 2 Clojure coder.
Another tip, I have extracted the support for nesting html templates using
enlive from http://clojurescriptone.com. What that gives you is the support
for "sandboxing" all the templates under a given url i.e templates/* so
that the designers can work with HTML-only but in a DRY fashion.
What I
Thanks! Those are great ideas.
On 10 Sty, 21:11, Sean Corfield wrote:
> My first thought is: don't bother compiling the code, just run it
> "live" from source (and maybe provide a way to easily reload the
> templates (such as a URL parameter).
>
> What I've done in my FW/1 framework (convention-
My first thought is: don't bother compiling the code, just run it
"live" from source (and maybe provide a way to easily reload the
templates (such as a URL parameter).
What I've done in my FW/1 framework (convention-based MVC, built on
Ring and Enlive) is to have a mode that auto-reloads templates
So, I am working on a web app that is buillt with Clojure/Ring/Jetty
and, importantly, Enlive. My directory structure is like this:
/resources
/public
/css
/js
/img
/templates
/src
/discovery
core.clj
The great thing about Enlive is that the template
