; The shipped templates, installed into <prefix>/share/colitur/templates/
; so a user can render a booklet or a wall calendar straight from an
; installed `colitur`, without a source checkout on hand -- the same
; "runnable documentation" reasoning data/dune already gives
; examples/diocesan-example.sexp. Nothing in colitur's own code path looks
; these up (--template takes a plain, user-given file path, read exactly
; like an overlay file), so this is a convenience install, not something a
; probe function depends on the way [data_dir]/[schema_path] depend on
; data/ef/ and schema/. Task 13.
(install
 (section share)
 (package colitur)
 (files
  (ef/ordo.tex as templates/ef/ordo.tex)
  (ef/ordo.ms as templates/ef/ordo.ms)
  (ef/ordo.html as templates/ef/ordo.html)
  (ef/ordo.adoc as templates/ef/ordo.adoc)
  (ef/ordo.md as templates/ef/ordo.md)
  (ef/ordo.txt as templates/ef/ordo.txt)
  (ef/grid.tex as templates/ef/grid.tex)
  (ef/grid.ms as templates/ef/grid.ms)
  (ef/grid.html as templates/ef/grid.html)))