   (:import
    [org.pegdown PegDownProcessor
                 Extensions]))
+
+;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
+;;; Utility Functions
+;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
+
+(defn default-renderer
+  "This is the function used by default to render templates, given data that
+  the template needs to render."
+  [template-file data]
+  (selmer/render-file template-file data))
 
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
 ;;; Routing Setup

(ns cmr.common-app.api-docs
  "This namespace contains helpers for generating and returning a page documenting an application's
  APIs. API Documentation for an application consists of two parts, a welcome page and a single page with
  all of the api documentation.

  ## Welcome Page

  The welcome page is served if you hit the root URL of the application. It usually has the name of
  the application, a short description, and then a link to the documentation. Each application
  should define welcome page as <app-folder>/resources/public/index.html. See search app for an
  example.

  ## API Documentation Markdown

  API documentation is written in markdown in a single file located in <app-folder>/api_docs.md.
  You can refer to %CMR-ENDPOINT% in the documentation. It will be replaced with the public URL of
  the application when the page is served.

  ## Routing

  An application using this namespace for documentation must define routes to load the HTML pages.

  ```
  ;; In namespace definition

      (docs-routes public-protocol relative-root-url))))

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;; Core API Documentation Functions
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

