Clojurians Log v2

because I'm generating static content I leaned into pre-generating my hiccup components into the config:

;; elements.edn

{:navbar    #ig/ref :mysite.hiccup/navbar
 :footer    #ig/ref :mysite.hiccup/footer
 :head-tags
 [[:link {:type "text/css" :href "/css/reset.css" :rel "stylesheet"}]
  [:meta {:charset "UTF-8"}]
  [:meta {:name "viewport" :content "width=device-width, initial-scale=1.0"}]]}

;; routes.edn
[["/" {:get :mysite.routes/home}]
 ["/about-us" {:get :mysites.routes/about-us
               :title "About Us"}]
 ...
 ]

;; duct.edn
{
  ...

  ;; my navbar component wants the canonical list of routes passed to it
  :mysite.hiccup/navbar
  {:routes #duct/include "routes.edn"}

  :mysite.hiccup/footer
  {}

  :mysite.hiccup/home-page
  {:elements #duct/include "elements.edn"}

  :mysite.routes/home
  {:page-hiccup #ig/ref :mysite.hiccup/home-page}

;; mysite/routes.clj

(defmethod ig/init-key ::page-handler [_ {:keys [page-hiccup]}]
  (constantly page-hiccup))

(derive :mysite.routes/home     ::page-handler)
(derive :mysite.routes/about-us ::page-handler)

Glad it worked out for you! Out of interest, what made you consider using Duct for a static site?

It’s an infrequently updated site, so I kind of hate coming back to it six months later and having to grep around the code base for the small number of inputs that need to change. I believe in the Arachne , Zen-lang, and seemingly Duct philosophy that many of the important parts of our app can live in static EDN files.

And even though I’ve done it before I don’t get joy from wiring up all of the HTTP handler router middleware refresh stuff myself

Thanks for explaining. I hadn't considered that as a use-case, but I can see why Duct might be useful in that case.