summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDan Allen <dan.j.allen@gmail.com>2022-01-08 23:49:46 -0700
committerDan Allen <dan.j.allen@gmail.com>2022-01-09 01:30:04 -0700
commitfb22875a53e7e05e8a5a0895b6083acb22ec4cc0 (patch)
treee2f723753545e0d7d7b96cdd331ca9ecfa72dfdb /docs
parent44e321e79c574ebc39f6e4349580a308a25fb0f7 (diff)
cite example for remapping a backend to a different converter in the docs
Diffstat (limited to 'docs')
-rw-r--r--docs/modules/convert/pages/index.adoc1
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/modules/convert/pages/index.adoc b/docs/modules/convert/pages/index.adoc
index b4042b16..45321fb8 100644
--- a/docs/modules/convert/pages/index.adoc
+++ b/docs/modules/convert/pages/index.adoc
@@ -44,4 +44,5 @@ In summary, a converter is a software component that handles the conversion from
The backend represents the user's intent to transform the AsciiDoc document to a given format (e.g., `html5` for HTML 5).
That backend also serves as an identifier that tells the processor which converter to use.
More than one converter can bind to (i.e., stake claim to) the same backend in order to provide the user with alternatives for generating a given output format.
+For example, the backend `pdf` could be satisfied by Asciidoctor PDF, but it may also be mapped to a different implementation.
The last converter that registers itself with a backend wins.