apex-ruby 1.0.6 → 1.0.8

data/ext/apex_ext/apex_src/man/apex-plugins.7

@@ -1,456 +1,541 @@
-.\" Automatically generated by Pandoc 3.8.3
-.\"
-.TH "APEX\-PLUGINS" "7" "December 2025" ""
+.TH "NAME" "1" "1 January 1970" ""
+
 .SH NAME
+
+.PP
 apex\-plugins \- Apex plugin system for extending Markdown processing
+
 .SH DESCRIPTION
-Apex supports a lightweight plugin system that lets you add new syntax
-and post\-processing behavior without patching the core.
-Plugins can be small scripts (Ruby, Python, etc.)
-or simple declarative regex rules defined in YAML.
+
+.PP
+Apex supports a lightweight plugin system that lets you add new syntax and post\-processing behavior without patching the core. Plugins can be small scripts (Ruby, Python, etc.) or simple declarative regex rules defined in YAML.
+
 .PP
-Plugins are disabled by default so Apex\(cqs performance and behavior
-are unchanged unless you explicitly opt in.
+Plugins are disabled by default so Apex’s performance and behavior are unchanged unless you explicitly opt in.
+
 .SH ENABLING PLUGINS
+
 .SS Command\-line flags
+
 .IP \(bu 2
-\f[B]Enable plugins\f[R]: \f[CR]apex \-\-plugins input.md\f[R]
+\f[B]Enable plugins\f[]: \fRapex \-\-plugins input.md\f[]
+
 .IP \(bu 2
-\f[B]Disable plugins\f[R]: \f[CR]apex \-\-no\-plugins input.md\f[R]
+\f[B]Disable plugins\f[]: \fRapex \-\-no\-plugins input.md\f[]
+
 .SS Metadata keys
-In the document\(cqs front matter, any of these keys are recognized
-(case\-insensitive):
+
+.PP
+In the document’s front matter, any of these keys are recognized (case\-insensitive):
+
 .IP \(bu 2
-\f[CR]plugins\f[R]
+\fRplugins\f[]
+
 .IP \(bu 2
-\f[CR]enable\-plugins\f[R]
+\fRenable\-plugins\f[]
+
 .IP \(bu 2
-\f[CR]enable_plugins\f[R]
+\fRenable_plugins\f[]
+
 .PP
 Example:
-.IP
-.EX
+
+.PP
+.nf
+\fR
 \-\-\-
-title\f[B]:\f[R] Plugin demo
-plugins\f[B]:\f[R] true
+title: Plugin demo
+plugins: true
 \-\-\-
-.EE
+
+\f[]
+.fi
+
 .SS Precedence
-If metadata enables or disables plugins, you can still override it from
-the CLI:
+
+.PP
+If metadata enables or disables plugins, you can still override it from the CLI:
+
 .IP \(bu 2
-\f[CR]\-\-plugins\f[R] forces plugins \f[B]on\f[R]
+\fR\-\-plugins\f[] forces plugins \f[B]on\f[]
+
 .IP \(bu 2
-\f[CR]\-\-no\-plugins\f[R] forces plugins \f[B]off\f[R]
+\fR\-\-no\-plugins\f[] forces plugins \f[B]off\f[]
+
 .PP
 CLI flags always win over metadata.
+
 .SH PLUGIN LOCATIONS
+
+.PP
 Plugins are discovered from two locations, in this order:
-.IP "1." 3
-\f[B]Project\-local plugins\f[R]
-.RS 4
+
+.IP "1." 4
+\f[B]Project\-local plugins\f[]
+
 .IP \(bu 2
-Directory: \f[CR].apex/plugins/\f[R] in the same project as your
-documents
+Directory: \fR.apex/plugins/\f[] in the same project as your documents
+
 .IP \(bu 2
 Structure: one subdirectory per plugin, for example:
-.RS 2
+
 .IP \(bu 2
-\f[CR].apex/plugins/kbd/plugin.yml\f[R]
+\fR.apex/plugins/kbd/plugin.yml\f[]
+
 .IP \(bu 2
-\f[CR].apex/plugins/kbd/kbd_plugin.rb\f[R]
-.RE
-.RE
-.IP "2." 3
-\f[B]Global (user) plugins\f[R]
-.RS 4
+\fR.apex/plugins/kbd/kbd_plugin.rb\f[]
+
+.IP "2." 4
+\f[B]Global (user) plugins\f[]
+
 .IP \(bu 2
-If \f[CR]$XDG_CONFIG_HOME\f[R] is set:
-\f[CR]$XDG_CONFIG_HOME/apex/plugins/\f[R]
+If \fR$XDG_CONFIG_HOME\f[] is set: \fR$XDG_CONFIG_HOME/apex/plugins/\f[]
+
 .IP \(bu 2
-Otherwise: \f[CR]\(ti/.config/apex/plugins/\f[R]
+Otherwise: \fR~/.config/apex/plugins/\f[]
+
 .IP \(bu 2
 Same structure: one subdirectory per plugin
-.RE
+
 .PP
-\f[B]Plugin IDs must be unique.\f[R] If a project plugin and a global
-plugin share the same \f[CR]id\f[R], the project plugin wins and the
-global one is ignored.
+\f[B]Plugin IDs must be unique.\f[] If a project plugin and a global plugin share the same \fRid\f[], the project plugin wins and the global one is ignored.
+
 .SH PROCESSING PHASES
-Apex exposes several phases in its pipeline.
-Plugins can hook into one or more phases:
+
+.PP
+Apex exposes several phases in its pipeline. Plugins can hook into one or more phases:
+
 .IP \(bu 2
-\f[B]\f[CB]pre_parse\f[B]\f[R]
-.RS 2
+\f[B]\fRpre_parse\f[]\f[]
+
 .IP \(bu 2
 Runs on the raw Markdown text before it is parsed.
+
 .IP \(bu 2
-Good for: custom syntax (e.g.\ \f[CR]{% kbd ... %}\f[R]), textual
-rewrites, adding/removing markup before Apex sees it
-.RE
+Good for: custom syntax (e.g. \fRAPEX_LIQUID_TAG_0\f[]), textual rewrites, adding/removing markup before Apex sees it
+
 .IP \(bu 2
-\f[B]\f[CB]post_render\f[B]\f[R]
-.RS 2
+\f[B]\fRpost_render\f[]\f[]
+
 .IP \(bu 2
 Runs on the final HTML output after Apex finishes rendering.
+
 .IP \(bu 2
-Good for: wrapping elements in spans/divs, adding CSS classes, simple
-HTML post\-processing (e.g.\ turning \f[CR]:emoji:\f[R] into
-\f[CR]<span>\f[R])
-.RE
+Good for: wrapping elements in spans/divs, adding CSS classes, simple HTML post\-processing (e.g. turning \fR:memo:\f[] into \fR<span>\f[])
+
 .PP
 Internally, plugins for each phase are run in a deterministic order:
-.IP "1." 3
-Sorted by priority (lower numbers first; default is \f[CR]100\f[R]).
-.IP "2." 3
-Ties broken by plugin \f[CR]id\f[R] (lexicographically).
+
+.IP "1." 4
+Sorted by priority (lower numbers first; default is \fR100\f[]).
+
+.IP "2." 4
+Ties broken by plugin \fRid\f[] (lexicographically).
+
 .SH PLUGIN MANIFEST
+
+.PP
 Each plugin is defined by a manifest file:
+
 .IP \(bu 2
-\f[B]File name\f[R]: \f[CR]plugin.yml\f[R]
+\f[B]File name\f[]: \fRplugin.yml\f[]
+
 .IP \(bu 2
-\f[B]Location\f[R]: inside the plugin\(cqs directory
+\f[B]Location\f[]: inside the plugin’s directory
+
 .PP
 At minimum, a plugin needs:
-.IP
-.EX
+
+.PP
+.nf
+\fR
 \-\-\-
-id\f[B]:\f[R] my\-plugin
-phase\f[B]:\f[R] pre_parse\f[I]           # or post_render\f[R]
-priority\f[B]:\f[R] 100\f[I]              # optional, lower runs earlier\f[R]
+id: my\-plugin
+phase: pre_parse           # or post_render
+priority: 100              # optional, lower runs earlier
 \-\-\-
-.EE
+
+\f[]
+.fi
+
 .PP
 From there, you choose one of two plugin types:
+
 .IP \(bu 2
-\f[B]External handler plugin\f[R] \- Runs an external command (Ruby,
-Python, shell, etc.).
-Declared with a \f[CR]handler.command\f[R] field.
+\f[B]External handler plugin\f[] \- Runs an external command (Ruby, Python, shell, etc.). Declared with a \fRhandler.command\f[] field.
+
 .IP \(bu 2
-\f[B]Declarative regex plugin\f[R] \- No external code; in\-process
-regex search/replace.
-Declared with \f[CR]pattern\f[R] and \f[CR]replacement\f[R] fields.
+\f[B]Declarative regex plugin\f[] \- No external code; in\-process regex search/replace. Declared with \fRpattern\f[] and \fRreplacement\f[] fields.
+
 .PP
-You can\(cqt mix both styles in a single plugin; if
-\f[CR]handler.command\f[R] is present, the plugin is treated as
-external.
+You can’t mix both styles in a single plugin; if \fRhandler.command\f[] is present, the plugin is treated as external.
+
 .SS Metadata fields
-To support plugin directories, automatic installation, and future
-auto\-update tools, Apex understands several optional metadata fields in
-\f[CR]plugin.yml\f[R]:
+
+.PP
+To support plugin directories, automatic installation, and future auto\-update tools, Apex understands several optional metadata fields in \fRplugin.yml\f[]:
+
 .IP \(bu 2
-\f[B]\f[CB]title\f[B]\f[R]: Short, human\-friendly name for the plugin
+\f[B]\fRtitle\f[]\f[]: Short, human\-friendly name for the plugin
+
 .IP \(bu 2
-\f[B]\f[CB]author\f[B]\f[R]: Free\-form author string
+\f[B]\fRauthor\f[]\f[]: Free\-form author string
+
 .IP \(bu 2
-\f[B]\f[CB]description\f[B]\f[R]: One\-two sentence description of what
-the plugin does
+\f[B]\fRdescription\f[]\f[]: One\-two sentence description of what the plugin does
+
 .IP \(bu 2
-\f[B]\f[CB]homepage\f[B]\f[R]: Informational URL where users can learn
-more about the plugin
+\f[B]\fRhomepage\f[]\f[]: Informational URL where users can learn more about the plugin
+
 .IP \(bu 2
-\f[B]\f[CB]repo\f[B]\f[R]: Canonical Git URL for the plugin repository,
-used by Apex when installing plugins
+\f[B]\fRrepo\f[]\f[]: Canonical Git URL for the plugin repository, used by Apex when installing plugins
+
 .IP \(bu 2
-\f[B]\f[CB]post_install\f[B]\f[R]: Optional command that Apex will run
-after cloning the plugin during \f[CR]\-\-install\-plugin\f[R]
+\f[B]\fRpost_install\f[]\f[]: Optional command that Apex will run after cloning the plugin during \fR\-\-install\-plugin\f[]
+
 .PP
-Only \f[CR]id\f[R], \f[CR]phase\f[R], and either
-\f[CR]handler.command\f[R] (for external plugins) or
-\f[CR]pattern\f[R]/\f[CR]replacement\f[R] (for declarative plugins) are
-required for execution.
+Only \fRid\f[], \fRphase\f[], and either \fRhandler.command\f[] (for external plugins) or \fRpattern\f[]/\fRreplacement\f[] (for declarative plugins) are required for execution.
+
 .SH EXTERNAL HANDLER PLUGINS
-An external handler plugin defines a command to run, which receives JSON
-on stdin and writes the transformed text to stdout.
+
+.PP
+An external handler plugin defines a command to run, which receives JSON on stdin and writes the transformed text to stdout.
+
 .SS Manifest example
-.IP
-.EX
+
+.PP
+.nf
+\fR
 \-\-\-
-id\f[B]:\f[R] kbd
-title\f[B]:\f[R] Keyboard Shortcuts
-author\f[B]:\f[R] Brett Terpstra
-description\f[B]:\f[R] Render {% kbd ... %} key combos to HTML
-homepage\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-kbd\-plugin
-repo\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-kbd\-plugin.git
-phase\f[B]:\f[R] pre_parse
-priority\f[B]:\f[R] 100
-timeout_ms\f[B]:\f[R] 0\f[I]        # optional\f[R]
-handler\f[B]:\f[R]
-  command\f[B]:\f[R] \(dqruby kbd_plugin.rb\(dq
+id: kbd
+title: Keyboard Shortcuts
+author: Brett Terpstra
+description: Render APEX_LIQUID_TAG_1 key combos to HTML
+homepage: https://github.com/ApexMarkdown/apex\-kbd\-plugin
+repo: https://github.com/ApexMarkdown/apex\-kbd\-plugin.git
+phase: pre_parse
+priority: 100
+timeout_ms: 0        # optional
+handler:
+  command: "ruby kbd_plugin.rb"
 \-\-\-
-.EE
+
+\f[]
+.fi
+
 .SS JSON protocol
-For text phases (\f[CR]pre_parse\f[R], \f[CR]post_render\f[R]), Apex
-sends your command a JSON object on stdin:
-.IP
-.EX
+
+.PP
+For text phases (\fRpre_parse\f[], \fRpost_render\f[]), Apex sends your command a JSON object on stdin:
+
+.PP
+.nf
+\fR
 {
-  \(dqversion\(dq: 1,
-  \(dqplugin_id\(dq: \(dqkbd\(dq,
-  \(dqphase\(dq: \(dqpre_parse\(dq,
-  \(dqtext\(dq: \(dqraw or rendered text here\(dq
+  "version": 1,
+  "plugin_id": "kbd",
+  "phase": "pre_parse",
+  "text": "raw or rendered text here"
 }
-.EE
+
+\f[]
+.fi
+
 .PP
 Your plugin should:
-.IP "1." 3
+
+.IP "1." 4
 Read all of stdin.
-.IP "2." 3
+
+.IP "2." 4
 Parse the JSON.
-.IP "3." 3
-Transform the \f[CR]text\f[R] field.
-.IP "4." 3
+
+.IP "3." 4
+Transform the \fRtext\f[] field.
+
+.IP "4." 4
 Print the new text only to stdout (no extra JSON, headers, or logging).
+
 .PP
-If your plugin fails, times out, or prints nothing, Apex will treat it
-as a no\-op and continue gracefully.
+If your plugin fails, times out, or prints nothing, Apex will treat it as a no\-op and continue gracefully.
+
 .SH DECLARATIVE REGEX PLUGINS
-For many cases, you don\(cqt need a script at all.
-A declarative regex plugin uses \f[CR]regex.h\f[R] inside Apex for fast
-in\-process search/replace.
+
+.PP
+For many cases, you don’t need a script at all. A declarative regex plugin uses \fRregex.h\f[] inside Apex for fast in\-process search/replace.
+
 .SS Manifest example
-.IP
-.EX
+
+.PP
+.nf
+\fR
 \-\-\-
-id\f[B]:\f[R] emoji\-span
-title\f[B]:\f[R] Emoji span wrapper
-author\f[B]:\f[R] Brett Terpstra
-description\f[B]:\f[R] Wrap :emoji: markers in a span for styling
-homepage\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-emoji\-plugin
-repo\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-emoji\-plugin.git
-phase\f[B]:\f[R] post_render
-pattern\f[B]:\f[R] \(dq(:[a\-zA\-Z0\-9_+\-]+:)\(dq
-replacement\f[B]:\f[R] \(dq<span class=\(rs\(dqemoji\(rs\(dq>$1</span>\(dq
-flags\f[B]:\f[R] \(dqi\(dq\f[I]          # optional: e.g. i, m, s\f[R]
-priority\f[B]:\f[R] 200
-timeout_ms\f[B]:\f[R] 0
+id: emoji\-span
+title: Emoji span wrapper
+author: Brett Terpstra
+description: Wrap :memo: markers in a span for styling
+homepage: https://github.com/ApexMarkdown/apex\-emoji\-plugin
+repo: https://github.com/ApexMarkdown/apex\-emoji\-plugin.git
+phase: post_render
+pattern: "(:[a\-zA\-Z0\-9_+\-]+:)"
+replacement: "<span class=\e"emoji\e">$1</span>"
+flags: "i"          # optional: e.g. i, m, s
+priority: 200
+timeout_ms: 0
 \-\-\-
-.EE
+
+\f[]
+.fi
+
 .IP \(bu 2
-\f[B]\f[CB]pattern\f[B]\f[R]: POSIX regular expression (compiled via
-\f[CR]regcomp\f[R]).
+\f[B]\fRpattern\f[]\f[]: POSIX regular expression (compiled via \fRregcomp\f[]).
+
 .IP \(bu 2
-\f[B]\f[CB]replacement\f[B]\f[R]: Replacement string with capture groups
-like \f[CR]$1\f[R], \f[CR]$2\f[R], etc.
-Runs repeatedly across the text until no more matches.
+\f[B]\fRreplacement\f[]\f[]: Replacement string with capture groups like \fR$1\f[], \fR$2\f[], etc. Runs repeatedly across the text until no more matches.
+
 .IP \(bu 2
-\f[B]\f[CB]flags\f[B]\f[R] (optional): Currently supports \f[CR]i\f[R]
-(case\-insensitive), \f[CR]m\f[R] (multi\-line), \f[CR]s\f[R] (dot
-matches newline).
+\f[B]\fRflags\f[]\f[] (optional): Currently supports \fRi\f[] (case\-insensitive), \fRm\f[] (multi\-line), \fRs\f[] (dot matches newline).
+
 .PP
-This is ideal when you only need straightforward pattern substitution
-and performance matters.
+This is ideal when you only need straightforward pattern substitution and performance matters.
+
 .SH PLUGIN BUNDLES
-Sometimes it is convenient for a single repository to provide multiple
-related plugins as a bundle.
-Apex supports a bundle syntax in \f[CR]plugin.yml\f[R] when built with
-full YAML (libyaml) support.
+
+.PP
+Sometimes it is convenient for a single repository to provide multiple related plugins as a bundle. Apex supports a bundle syntax in \fRplugin.yml\f[] when built with full YAML (libyaml) support.
+
 .SS Bundle structure
+
+.PP
 A bundle manifest has:
+
 .IP \(bu 2
 Top\-level metadata that applies to the bundle as a whole.
+
 .IP \(bu 2
-A \f[CR]bundle:\f[R] key whose value is a YAML sequence (array) of
-per\-plugin configs.
+A \fRbundle:\f[] key whose value is a YAML sequence (array) of per\-plugin configs.
+
 .PP
 Example:
-.IP
-.EX
+
+.PP
+.nf
+\fR
 \-\-\-
-id\f[B]:\f[R] documentation
-title\f[B]:\f[R] Documentation helpers
-author\f[B]:\f[R] Brett Terpstra
-description\f[B]:\f[R] A bundle of documentation\-related helpers
-homepage\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-plugin\-documentation
-repo\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-plugin\-documentation.git
-
-bundle\f[B]:\f[R]
-  \f[B]\-\f[R] id\f[B]:\f[R] kbd
-    title\f[B]:\f[R] Keyboard Shortcuts
-    description\f[B]:\f[R] Render {% kbd ... %} key combos to HTML <kbd> elements
-    phase\f[B]:\f[R] pre_parse
-    priority\f[B]:\f[R] 100
-    handler\f[B]:\f[R]
-      command\f[B]:\f[R] \(dqruby kbd_plugin.rb\(dq
-
-  \f[B]\-\f[R] id\f[B]:\f[R] menubar
-    title\f[B]:\f[R] Menubar Paths
-    description\f[B]:\f[R] Render {% menubar File, Open %} to a styled menu path
-    phase\f[B]:\f[R] pre_parse
-    handler\f[B]:\f[R]
-      command\f[B]:\f[R] \(dqruby menubar_plugin.rb\(dq
+id: documentation
+title: Documentation helpers
+author: Brett Terpstra
+description: A bundle of documentation\-related helpers
+homepage: https://github.com/ApexMarkdown/apex\-plugin\-documentation
+repo: https://github.com/ApexMarkdown/apex\-plugin\-documentation.git
+bundle:
+  \- id: kbd
+    title: Keyboard Shortcuts
+    description: Render APEX_LIQUID_TAG_2 key combos to HTML <kbd> elements
+    phase: pre_parse
+    priority: 100
+    handler:
+      command: "ruby kbd_plugin.rb"
+  \- id: menubar
+    title: Menubar Paths
+    description: Render APEX_LIQUID_TAG_3 to a styled menu path
+    phase: pre_parse
+    handler:
+      command: "ruby menubar_plugin.rb"
 \-\-\-
-.EE
+
+\f[]
+.fi
+
 .PP
-Apex will treat this as three distinct plugins: \f[CR]kbd\f[R],
-\f[CR]menubar\f[R], and \f[CR]prefspane\f[R], all sourced from the same
-repository and manifest.
+Apex will treat this as three distinct plugins: \fRkbd\f[], \fRmenubar\f[], and \fRprefspane\f[], all sourced from the same repository and manifest.
+
 .SH ENVIRONMENT VARIABLES
+
+.PP
 When Apex runs an external handler plugin, it sets:
+
 .IP \(bu 2
-\f[B]\f[CB]APEX_PLUGIN_DIR\f[B]\f[R]
-.RS 2
+\f[B]\fRAPEX_PLUGIN_DIR\f[]\f[]
+
 .IP \(bu 2
-Filesystem path to the plugin\(cqs directory (where
-\f[CR]plugin.yml\f[R] lives).
+Filesystem path to the plugin’s directory (where \fRplugin.yml\f[] lives).
+
 .IP \(bu 2
 Useful for loading sidecar files, templates, etc.
-.RE
+
 .IP \(bu 2
-\f[B]\f[CB]APEX_SUPPORT_DIR\f[B]\f[R]
-.RS 2
+\f[B]\fRAPEX_SUPPORT_DIR\f[]\f[]
+
 .IP \(bu 2
-Base support directory: \f[CR]$XDG_CONFIG_HOME/apex/support/\f[R] or
-\f[CR]\(ti/.config/apex/support/\f[R]
+Base support directory: \fR$XDG_CONFIG_HOME/apex/support/\f[] or \fR~/.config/apex/support/\f[]
+
 .IP \(bu 2
-For each plugin, Apex creates: \f[CR]APEX_SUPPORT_DIR/<plugin\-id>/\f[R]
+For each plugin, Apex creates: \fRAPEX_SUPPORT_DIR/<plugin\-id>/\f[]
+
 .IP \(bu 2
 You can safely write caches, logs, or temporary files there.
-.RE
+
 .IP \(bu 2
-\f[B]\f[CB]APEX_FILE_PATH\f[B]\f[R]
-.RS 2
+\f[B]\fRAPEX_FILE_PATH\f[]\f[]
+
 .IP \(bu 2
-When Apex is invoked on a file, this is the original path that was
-passed on the command line.
+When Apex is invoked on a file, this is the original path that was passed on the command line.
+
 .IP \(bu 2
-When Apex reads from stdin, \f[CR]APEX_FILE_PATH\f[R] is set to the
-current \f[CR]base_directory\f[R] (if one was set) or an empty string.
-.RE
+When Apex reads from stdin, \fRAPEX_FILE_PATH\f[] is set to the current \fRbase_directory\f[] (if one was set) or an empty string.
+
 .PP
-All of these variables apply only during the external command\(cqs
-execution and are restored afterward.
+All of these variables apply only during the external command’s execution and are restored afterward.
+
 .SH INSTALLING PLUGINS
-Apex can install plugins directly from a central directory or from Git
-URLs.
+
+.PP
+Apex can install plugins directly from a central directory or from Git URLs.
+
 .SS Listing available plugins
-.IP
-.EX
+
+.PP
+.nf
+\fR
 apex \-\-list\-plugins
-.EE
+
+\f[]
+.fi
+
 .PP
-This command fetches the plugin directory and prints a listing of
-installed and available plugins.
+This command fetches the plugin directory and prints a listing of installed and available plugins.
+
 .SS Installing a plugin
-The \f[CR]\-\-install\-plugin\f[R] command accepts three types of
-arguments:
-.IP "1." 3
-\f[B]Plugin ID from the directory\f[R] (recommended for curated
-plugins):
-.RS 4
-.IP
-.EX
+
+.PP
+The \fR\-\-install\-plugin\f[] command accepts three types of arguments:
+
+.IP "1." 4
+\f[B]Plugin ID from the directory\f[] (recommended for curated plugins):
 apex \-\-install\-plugin kbd
-.EE
-.RE
-.IP "2." 3
-\f[B]Full Git URL\f[R] (for plugins not in the directory):
-.RS 4
-.IP
-.EX
+
+
+.IP "2." 4
+\f[B]Full Git URL\f[] (for plugins not in the directory):
 apex \-\-install\-plugin https://github.com/ttscoff/apex\-plugin\-kbd.git
-.EE
-.RE
-.IP "3." 3
-\f[B]GitHub shorthand\f[R] (\f[CR]user/repo\f[R] format):
-.RS 4
-.IP
-.EX
+
+
+.IP "3." 4
+\f[B]GitHub shorthand\f[] (\fRuser/repo\f[] format):
 apex \-\-install\-plugin ttscoff/apex\-plugin\-kbd
-.EE
-.RE
+
+
 .PP
-When installing from a direct Git URL or GitHub shorthand (i.e.,
-anything outside the curated directory), Apex will prompt for
-confirmation since plugins execute unverified code.
+When installing from a direct Git URL or GitHub shorthand (i.e., anything outside the curated directory), Apex will prompt for confirmation since plugins execute unverified code.
+
 .SS Uninstalling a plugin
-.IP
-.EX
+
+.PP
+.nf
+\fR
 apex \-\-uninstall\-plugin kbd
-.EE
-.PP
-The \f[CR]\-\-uninstall\-plugin\f[R] command verifies that the plugin
-directory exists, prompts for confirmation, and removes the plugin\(cqs
-directory.
-Support data under \f[CR].../apex/support/<plugin\-id>/\f[R] is left
-intact.
-.PP
-This command only works for plugins installed in the user plugin
-directory.
-Project\-local plugins (in \f[CR].apex/plugins/\f[R]) must be removed
-manually.
+
+\f[]
+.fi
+
+.PP
+The \fR\-\-uninstall\-plugin\f[] command verifies that the plugin directory exists, prompts for confirmation, and removes the plugin’s directory. Support data under \fR.../apex/support/<plugin\-id>/\f[] is left intact.
+
+.PP
+This command only works for plugins installed in the user plugin directory. Project\-local plugins (in \fR.apex/plugins/\f[]) must be removed manually.
+
 .SH EXAMPLES
-.SS Example: \f[CR]kbd\f[R] liquid tag plugin
-This example shows how to support a liquid\-style
-\f[CR]{% kbd ... %}\f[R] syntax, turning key combos into
-\f[CR]<kbd>\f[R] markup.
+
+.SS Example: \fRkbd\f[] liquid tag plugin
+
+.PP
+This example shows how to support a liquid\-style \fRAPEX_LIQUID_TAG_4\f[] syntax, turning key combos into \fR<kbd>\f[] markup.
+
 .SS Directory layout
-.IP
-.EX
+
+.PP
+.nf
+\fR
 \&.apex/
   plugins/
     kbd/
       plugin.yml
       kbd_plugin.rb
-.EE
-.SS \f[CR]plugin.yml\f[R]
-.IP
-.EX
+
+\f[]
+.fi
+
+.SS \fRplugin.yml\f[]
+
+.PP
+.nf
+\fR
 \-\-\-
-id\f[B]:\f[R] kbd
-title\f[B]:\f[R] Keyboard Shortcuts
-author\f[B]:\f[R] Brett Terpstra
-description\f[B]:\f[R] Render {% kbd ... %} key combos to HTML <kbd> elements
-homepage\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-kbd\-plugin
-repo\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-kbd\-plugin.git
-phase\f[B]:\f[R] pre_parse
-priority\f[B]:\f[R] 100
-timeout_ms\f[B]:\f[R] 0
-handler\f[B]:\f[R]
-  command\f[B]:\f[R] \(dqruby kbd_plugin.rb\(dq
+id: kbd
+title: Keyboard Shortcuts
+author: Brett Terpstra
+description: Render APEX_LIQUID_TAG_5 key combos to HTML <kbd> elements
+homepage: https://github.com/ApexMarkdown/apex\-kbd\-plugin
+repo: https://github.com/ApexMarkdown/apex\-kbd\-plugin.git
+phase: pre_parse
+priority: 100
+timeout_ms: 0
+handler:
+  command: "ruby kbd_plugin.rb"
 \-\-\-
-.EE
-.PP
-The Ruby script reads JSON from stdin, extracts \f[CR]text\f[R],
-replaces each \f[CR]{% kbd ... %}\f[R] occurrence with properly
-formatted \f[CR]<kbd>\f[R] HTML, and prints the full transformed text to
-stdout.
-.SS Example: \f[CR]:emoji:\f[R] span plugin (declarative)
-This plugin turns \f[CR]:emoji:\f[R] tokens in the final HTML into
-\f[CR]<span class=\(dqemoji\(dq>:emoji:</span>\f[R].
-.SS \f[CR]plugin.yml\f[R]
-.IP
-.EX
+
+\f[]
+.fi
+
+.PP
+The Ruby script reads JSON from stdin, extracts \fRtext\f[], replaces each \fRAPEX_LIQUID_TAG_6\f[] occurrence with properly formatted \fR<kbd>\f[] HTML, and prints the full transformed text to stdout.
+
+.SS Example: \fR:memo:\f[] span plugin (declarative)
+
+.PP
+This plugin turns \fR:memo:\f[] tokens in the final HTML into \fR<span class="emoji">:memo:</span>\f[].
+
+.SS \fRplugin.yml\f[]
+
+.PP
+.nf
+\fR
 \-\-\-
-id\f[B]:\f[R] emoji\-span
-title\f[B]:\f[R] Emoji span wrapper
-author\f[B]:\f[R] Brett Terpstra
-description\f[B]:\f[R] Wrap :emoji: markers in a span for styling
-homepage\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-emoji\-plugin
-repo\f[B]:\f[R] https://github.com/ApexMarkdown/apex\-emoji\-plugin.git
-phase\f[B]:\f[R] post_render
-pattern\f[B]:\f[R] \(dq(:[a\-zA\-Z0\-9_+\-]+:)\(dq
-replacement\f[B]:\f[R] \(dq<span class=\(rs\(dqemoji\(rs\(dq>$1</span>\(dq
-flags\f[B]:\f[R] \(dqi\(dq
-priority\f[B]:\f[R] 200
-timeout_ms\f[B]:\f[R] 0
+id: emoji\-span
+title: Emoji span wrapper
+author: Brett Terpstra
+description: Wrap :memo: markers in a span for styling
+homepage: https://github.com/ApexMarkdown/apex\-emoji\-plugin
+repo: https://github.com/ApexMarkdown/apex\-emoji\-plugin.git
+phase: post_render
+pattern: "(:[a\-zA\-Z0\-9_+\-]+:)"
+replacement: "<span class=\e"emoji\e">$1</span>"
+flags: "i"
+priority: 200
+timeout_ms: 0
 \-\-\-
-.EE
+
+\f[]
+.fi
+
 .PP
-Because this is a declarative plugin, no external command is run.
-Apex compiles the regex and runs the replacements internally.
+Because this is a declarative plugin, no external command is run. Apex compiles the regex and runs the replacements internally.
+
 .SH SEE ALSO
-\f[B]apex\f[R](1), \f[B]apex\-config\f[R](5)
+
 .PP
-For complete documentation, see the \c
-.UR https://github.com/ttscoff/apex/wiki
-Apex Wiki
-.UE \c
-\&.
+\f[B]apex\f[](1), \f[B]apex\-config\f[](5)
+
+.PP
+For complete documentation, see the Apex Wiki (https://github.com/ttscoff/apex/wiki).
+
 .SH AUTHOR
+
+.PP
 Brett Terpstra
+
 .SH COPYRIGHT
-Copyright (c) 2025 Brett Terpstra.
-Licensed under MIT License.
-.SH AUTHORS
-Brett Terpstra.
+
+.PP
+Copyright (c) 2025 Brett Terpstra. Licensed under MIT License.