summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDan Allen <dan.j.allen@gmail.com>2021-10-15 23:57:12 -0600
committerDan Allen <dan.j.allen@gmail.com>2021-10-16 06:02:45 -0600
commitd8be74a47ce5c6204a956e3618f22dcf49815f0c (patch)
treedfca874123f8e1fa74241c290ed4af8546d356b2 /docs
parent8d23e1d8cbcfbb6bf84fc64d79224f52924dde7e (diff)
document that converter templates can be shared with AsciidoctorJ, but not Asciidoctor.js, which has its own template converter
Diffstat (limited to 'docs')
-rw-r--r--docs/modules/convert/pages/templates.adoc3
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/modules/convert/pages/templates.adoc b/docs/modules/convert/pages/templates.adoc
index d225cff3..29cdbc90 100644
--- a/docs/modules/convert/pages/templates.adoc
+++ b/docs/modules/convert/pages/templates.adoc
@@ -74,6 +74,9 @@ Templates are used in Asciidoctor to customize the output generated by a convert
We refer to these as converter templates.
Converter templates work in conjunction with the converter over which they are applied.
+You can reuse the same set of templates you develop for Asciidoctor with AsciidoctorJ, making the templates portable between the two runtimes.
+Asciidoctor.js provides its own xref:asciidoctor.js:extend:converter/template-converter.adoc[template converter], which means you have to develop a different set of templates if you're using Asciidoctor.js.
+
There are three keys points to understand about using converter templates in Asciidoctor:
* How Asciidoctor selects the template engine to use.