layout

Ring middleware that allows developer to specify base HTML template.

Installation

Leiningen coordinates:

[ilshad/layout "0.1.0"]

Simplest option

Define wrap-layout middleware for your Ring application:

(ns mypapp
  (:require [ilshad.layout :refer [wrap-layout]]))

; ... define your compojure routes here
(def app
  (-> app*
      ; ... some middlewares
      (wrap-layout layout-template)
	  ; ... other middlewares
	  ))

where layout-template is your function (for example, build with enlive-html/deftemplate):

(ns mypapp
  (:require [net.cgrand.enlive-html :as html]))

(html/deftemplate layout-template "layout.html"
  [request content params]

  ; Compose response from handlers with base template.
  ; Some handler will return string with html, whereas other
  ; handlers will return data structure from enlive's html-snippet.
  [:#main] (if (string? content)
             (html/html-content content)
             (html/content content))

  ; Other things
  [:#menu] (html/content (myapp/build-menu request))
  [:#flash] (html/content (:flash request)))
  
  ; using custom layout params
  [:title] (:title params "Default Title")

This function takes 3 arguments:

• Ring request,
• Response's body from your Ring handler,
• map of custom params you might want to pass into the layout template, see below.

Custom params

Custom params are created with key :layout in Ring handler's response. Say we want to add title param:

(defn frontpage
  [req]
  {:status 200
   :headers {}
   :body "<h1>This is front page</h1>"
   :layout {:title "Welcome!"}})

Any custom params (under :layout) will be passed into your layout template function. Notice, there is 2 reserved keys in the params - :template and :prevent, see below.

Named layout templates

You can define multiple layout templates with middleware and then select them by passing their's names into response (under :layout map). There are 2 rules:

• names are keywords;
• :default template is used by default.

Let's define 2 layout templates: :default and :admin:

(def app
  (-> app*
      ; ... some middlewares
      (wrap-layout {:templates {:default layout-template-1
	                            :admin layout-template-2}})
	  ; ... other middlewares
	  ))

In handler, let's do response with admin layout:

(defn admin-page
  [req]
  {:status 200
   :headers {}
   :body "<h1>Admin console</h1>"
   :layout {:template :admin}})

Prevent layout

Some handlers must be called without wrapping their response's body into layout. There are 2 options how to do this:

• pass :prevent true from handler:

(defn ajax-handler
  [req]
  {:status 200
   :headers {}
   :body "foo bar baaz"
   :layout {:prevent true}})

• or define patterns for URI in middleware (vector of regexps):

(def app
  (-> app*
      ; ... some middlewares
      (wrap-layout {:prevent [#"/static/" #"/api/"]
                    :templates {:default layout-template}})
	  ; ... other middlewares
	  ))

Hiccup example

Hiccup is just working well, both on layout or handler side. Compose Compojure, Hiccup, etc, what how you like.

(defn layout-template
  [request content params]
  (hiccup.page/html5
   [:head
    [:title "Foo"]]
   [:body
    [:h1 "Foo"]
    [:div#main content]]))

(defn welcome-handler []
  (hiccup.core/html
    [:em "bar"]))

Summary

Middleware wrap-template can be used with:

• symbol argument (sole default template);
• or map argument (multiple templates and prevent-layout patterns).

Handlers can pass :layout slot into response with map. This map can contain:

• :template with name of template (also keyword);
• :prevent with value true;
• arbitrary fields (custom params) to pass them into layout template.

License

Copyright © 2013 Ilshad Khabibullin.

Distributed under the Eclipse Public License, the same as Clojure.