Fix plugins_in_modules: update product names, links, and layout

- Add layout: default frontmatter
- Replace Puppet Server/agent with OpenVox Server/agent
- Fix {{facter}} broken links to point to /openfact/latest/
- Fix /guides/custom_types.html and /guides/custom_functions.html to local pages
- Remove stale Puppet 5.3.4 pluginsync note
- Replace "master" with "primary server" in locale reference
- Remove {:.concept} markers
- Replace "Puppet loads" with "OpenVox loads"

Signed-off-by: Michael Harp <mike@mikeharp.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: miharp

docs/_openvox_8x/plugins_in_modules.markdown

@@ -1,44 +1,40 @@
 ---
+layout: default
 title: Plug-ins in Modules
 ---
 
 [modules]: ./modules_fundamentals.html
 [environment]: ./environments.html
 [modulepath]: ./dirs_modulepath.html
-[external facts]: {{facter}}/custom_facts.html#external-facts
+[external facts]: /openfact/latest/custom_facts.html#external-facts
 [vardir]: ./dirs_vardir.html
-[custom facts]: {{facter}}/custom_facts.html
-[custom resource types and providers]: /guides/custom_types.html
-[ruby_functions]: /guides/custom_functions.html
+[custom facts]: /openfact/latest/custom_facts.html
+[custom resource types and providers]: ./custom_types.html
+[ruby_functions]: ./functions_ruby_overview.html
 [puppet_functions]: ./lang_write_functions_in_puppet.html
 [custom augeas lenses]: https://github.com/hercules-team/augeas/wiki/Create-a-lens-from-bottom-to-top
 
-Puppet supports several kinds of **plug-ins,** which can be distributed in modules. These plug-ins enable new features for managing your nodes. Plug-ins are often included in modules downloaded from the Puppet Forge, and you can also develop your own.
+OpenVox supports several kinds of **plug-ins,** which can be distributed in modules. These plug-ins enable new features for managing your nodes. Plug-ins are often included in modules downloaded from the Puppet Forge, and you can also develop your own.
 
-{:.concept}
 ## Installing plug-ins
 
 Plug-ins are automatically enabled when you install the module that contains them. You don't have to do anything else: once a module is installed in an environment's modulepath, its plug-ins are available when managing nodes in that environment.
 
-{:.concept}
 ### Auto-download of agent-side plug-ins (pluginsync)
 
-Some plug-ins are used by Puppet Server, which can load them directly from modules. But other plug-ins (facts, custom resource types and providers) are used by Puppet agent, which doesn't have direct access to the server's modules.
+Some plug-ins are used by OpenVox Server, which can load them directly from modules. But other plug-ins (facts, custom resource types and providers) are used by OpenVox agent, which doesn't have direct access to the server's modules.
 
-To enable this, Puppet agent automatically downloads plug-ins from the server at the start of each agent run. Those plug-ins are then available during the run.
+To enable this, OpenVox agent automatically downloads plug-ins from the server at the start of each agent run. Those plug-ins are then available during the run.
 
-Puppet agent syncs plug-in files from _every_ module in its environment's modulepath, regardless of whether that node uses any classes from a given module, as well as any translations available for each module regardless of the agent's or master's locale.
+OpenVox agent syncs plug-in files from _every_ module in its environment's modulepath, regardless of whether that node uses any classes from a given module, as well as any translations available for each module regardless of the agent's or primary server's locale.
 
 In other words, even if you don't declare any classes from the `stdlib` module, nodes will still use `stdlib`'s custom facts. Also, even if your agent's locale is set to en-US, if the module has translations for other locales, the agent will download all of those translations.
 
-> **Note:** Puppet 5.3.4 added pluginsync of module translations. Agents running Puppet 5.3.4 or newer that connect to masters running older versions of Puppet do not automatically download translations.
-
-{:.concept}
 ### Technical details of pluginsync
 
 Pluginsync takes advantage of the same file serving features used by the `file` resource type.
 
-Puppet Server creates special file server mount points for pluginsync, and populates them with the aggregate contents of certain subdirectories of modules. Before doing an agent run, Puppet agent recursively manages the contents of those mount points into cache directories on disk. The agent performs the following functions:
+OpenVox Server creates special file server mount points for pluginsync, and populates them with the aggregate contents of certain subdirectories of modules. Before doing an agent run, OpenVox agent recursively manages the contents of those mount points into cache directories on disk. The agent performs the following functions:
 
 1. Sends GET requests to `/puppet/v3/file_metadatas/<MOUNT POINT>`,
 2. Compares the resulting checksums and ownership info to local files,
@@ -54,12 +50,11 @@ Plug-in type       | Module subdirectory | Mount point   | Agent directory
 Ruby plug-ins      | `<MODULE>/lib`      | `plugins`     | `<VARDIR>/lib`
 Translations       | `<MODULE>/locales`  | `locales`     | `<VARDIR>/locales`
 
-(`<VARDIR>` is Puppet agent's [cache directory][vardir], which is located at `/var/opt/puppetlabs/puppet/cache`, `%PROGRAMDATA%\PuppetLabs\puppet\cache`, or `~/.puppetlabs/opt/puppet/cache`.)
+(`<VARDIR>` is OpenVox agent's [cache directory][vardir], which is located at `/var/opt/puppetlabs/puppet/cache`, `%PROGRAMDATA%\PuppetLabs\puppet\cache`, or `~/.puppetlabs/opt/puppet/cache`.)
 
-{:.concept}
 ## Types of plug-ins
 
-Puppet supports several kinds of plug-ins:
+OpenVox supports several kinds of plug-ins:
 
 * [Custom facts][] (written in Ruby).
 * [External facts][] (executable scripts or static data).
@@ -69,9 +64,8 @@ Puppet supports several kinds of plug-ins:
 * [Custom Augeas lenses][].
 * Miscellaneous utility Ruby code used by other plug-ins.
 
-Facts and Augeas lenses are used solely by Puppet agent. Functions are used solely by Puppet Server. Resource types and providers are used by both. (Note that Puppet apply acts as both agent and server.)
+Facts and Augeas lenses are used solely by OpenVox agent. Functions are used solely by OpenVox Server. Resource types and providers are used by both. (Note that Puppet apply acts as both agent and server.)
 
-{:.concept}
 ## Adding plug-ins to a module
 
 To add plug-ins to a module, put them in the following directories:
@@ -115,12 +109,11 @@ To illustrate, a module that included every type of plug-in would have a directo
         -   `datacenter.py` (an executable script that returns fact data.)
     -   `locales`
 
-{:.concept}
 ## Issues with server-side plug-ins
 
 If you encounter problems with conflicting versions of the same plug-in in different environments, you can fix these issues as described below.
 
-Environments aren't completely isolated for certain kinds of plug-ins. If a plug-in of the same name exists in different versions in multiple environments, Puppet loads the plug-in from the first environment to use that plug-in, then continues to use that version of the plug-in for all subsequent environments.
+Environments aren't completely isolated for certain kinds of plug-ins. If a plug-in of the same name exists in different versions in multiple environments, OpenVox loads the plug-in from the first environment to use that plug-in, then continues to use that version of the plug-in for all subsequent environments.
 
 This issue can occur with the following plug-in types: