Try switching to askama templates

Author: msuchane

Cargo.lock

@@ -17,6 +17,7 @@ clap = "2"
 regex = "1"
 log = "0.4"
 simplelog = "0.10"
+askama = "0.8"
 
 
 [package.metadata.rpm.cargo]

Cargo.toml

@@ -0,0 +1,3 @@
+[general]
+# Directories to search for templates, relative to the crate root.
+dirs = ["data/templates"]

askama.toml

@@ -4,7 +4,7 @@ For more information about nesting assemblies, see: https://redhat-documentation
 See also the complementary step on the last line of this file.
 ////
 
-ifdef::context[:parent-context-of-${module_id}: {context}]
+ifdef::context[:parent-context-of-{{module_id}}: {context}]
 
 ////
 Base the file name and the ID on the assembly title. For example:
@@ -16,17 +16,17 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 ////
 
 ifndef::context[]
-[id="${module_id}"]
+[id="{{module_id}}"]
 endif::[]
 ifdef::context[]
-[id="${module_id}_{context}"]
+[id="{{module_id}}_{context}"]
 endif::[]
-= ${module_title}
+= {{module_title}}
 ////
 If the assembly covers a task, start the title with a verb in the gerund form, such as Creating or Configuring.
 ////
 
-:context: ${module_id}
+:context: {{module_id}}
 
 ////
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
@@ -53,7 +53,7 @@ The following include statements pull in the module files that comprise the asse
 include::modules/TEMPLATE_CONCEPT_explaining_a_concept.adoc[leveloffset=+1]
 ////
 
-${include_statements}
+{{include_statements}}
 
 ////
 [leveloffset=+1] ensures that when a module title is a level 1 heading (= Title), the heading will be interpreted as a level-2 heading (== Title) in the assembly. Use [leveloffset=+2] and [leveloffset=+3] to nest modules in an assembly.
@@ -78,6 +78,6 @@ Optional. Delete if not used.
 ////
 Restore the context to what it was before this assembly.
 ////
-ifdef::parent-context-of-${module_id}[:context: {parent-context-of-${module_id}}]
-ifndef::parent-context-of-${module_id}[:!context:]
+ifdef::parent-context-of-{{module_id}}[:context: {parent-context-of-{{module_id}}}]
+ifndef::parent-context-of-{{module_id}}[:!context:]
 

data/templates/assembly.adoc

@@ -11,8 +11,8 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
 ////
 
-[id="${module_id}_{context}"]
-= ${module_title}
+[id="{{module_id}}_{context}"]
+= {{module_title}}
 ////
 In the title of concept modules, include nouns or noun phrases that are used in the body text. This helps readers and search engines find the information quickly. Do not start the title of concept modules with a verb. See also _Wording of headings_ in _The IBM Style Guide_.
 ////

data/templates/concept.adoc

@@ -9,8 +9,8 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 ////
 
-[id="${module_id}_{context}"]
-= ${module_title}
+[id="{{module_id}}_{context}"]
+= {{module_title}}
 ////
 Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.
 ////

data/templates/procedure.adoc

@@ -9,8 +9,8 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 ////
 
-[id="${module_id}_{context}"]
-= ${module_title}
+[id="{{module_id}}_{context}"]
+= {{module_title}}
 ////
 In the title of a reference module, include nouns that are used in the body text. For example, "Keyboard shortcuts for ___" or "Command options for ___." This helps readers and search engines find the information quickly.
 ////