Docula

Custom Scripts

Guide for injecting custom scripts like Google Tag Manager and analytics into Docula sites using partial template overrides.

Docula lets you inject custom scripts — such as Google Tag Manager, analytics, or any third-party snippet — using partial template overrides. No extra configuration is needed; just create the right override file and add your code.

Table of Contents

Scripts at End of Body

Override includes/scripts.hbs to add scripts that load at the end of every page. This is the recommended placement for analytics and tracking snippets.

Create the override file:

mkdir -p site/templates/modern/includes

Then create site/templates/modern/includes/scripts.hbs:

NOTE

When you override scripts.hbs, it replaces the built-in file entirely. If you still need the default scripts (theme toggle, syntax highlighting, etc.), copy the contents of the original templates/modern/includes/scripts.hbs from the Docula repository and add your custom code alongside it.

Scripts in the Head

Override includes/header.hbs to add scripts or meta tags inside the element. This is useful for snippets that must load before the page renders.

Create site/templates/modern/includes/header.hbs with the original header content plus your additions:

Hosting Scripts Locally

If you prefer to self-host script files, place them in the public/ folder and reference them from your template overrides:

site/
  public/
    js/
      analytics.js
  templates/
    modern/
      includes/
        scripts.hbs

Then in your scripts.hbs override:

Files in site/public/ are copied to the root of the build output, so /js/analytics.js will be available at that path on your site.

Notes

  • This uses the partial template override system. Overrides only apply to built-in templates (modern, classic). If you use templatePath for a fully custom template, add scripts directly in your template files.
  • If you are using the classic template, replace modern with classic in the directory paths above.
Edit this page