Migrate plugins

Signed-off-by: nook24 <[email protected]>

Author: nook24

.vitepress/config.mts

@@ -92,6 +92,7 @@ export default defineConfig({
               { text: 'Object definitions', link: '/documentation/usersguide/objectdefinitions' },
               { text: 'CGI Configuration File Options', link: '/documentation/usersguide/configcgi' },
               { text: 'Authentication And Authorization CGIs', link: '/documentation/usersguide/cgiauth' },
+              { text: 'Plugins', link: '/documentation/usersguide/plugins' },
 
               { text: 'Naemon Logo', link: '/logo' }
             ]

…gacy/documentation/usersguide/plugins.md src/documentation/usersguide/plugins.mdlegacy/documentation/usersguide/plugins.md renamed to src/documentation/usersguide/plugins.md legacy/documentation/usersguide/plugins.md renamed to src/documentation/usersguide/plugins.md

@@ -1,61 +1,55 @@
----
-layout: doctoc
-title: Plugins
----
-<span class="glyphicon glyphicon-arrow-right"></span> See Also: <a href="pluginapi.html">Plugin API</a>, <a href="embeddedperl.html">Embedded Perl Interpreter Overview</a>, <a href="activechecks.html">Active Checks</a>
+# Plugins
 
-### Introduction
+## Introduction
 
 Unlike many other monitoring tools, Naemon does not include any internal mechanisms for checking the status of hosts and services on your network.  Instead, Naemon relies on external programs (called plugins) to do all the dirty work.
 
-### What Are Plugins?
+## What Are Plugins?
 
 Plugins are compiled executables or scripts (Perl scripts, shell scripts, etc.) that can be run from a command line to check the status or a host or service.  Naemon uses the results from plugins to determine the current status of hosts and services on your network.
 
-Naemon will execute a plugin whenever there is a need to check the status of a service or host.  The plugin does <i>something</i> (notice the very general term) to perform the check and then simply returns the results to Naemon.  Naemon will process the results that it receives from the plugin and take any necessary actions (running <a href="eventhandlers.html">event handlers</a>, sending out <a href="notifications.html">notifications</a>, etc).
+Naemon will execute a plugin whenever there is a need to check the status of a service or host.  The plugin does *something* (notice the very general term) to perform the check and then simply returns the results to Naemon.  Naemon will process the results that it receives from the plugin and take any necessary actions (running [event handlers](eventhandlers), sending out [notifications](notifications), etc).
 
-### Plugins As An Abstraction Layer
+## Plugins As An Abstraction Layer
 
-<img src="images/svg/plugins.svg" class="svg-image" border="0" style="float: right;" alt="Plugins">
+![Plugins](/images/usersguide/svg/plugins.svg) {.img-bg}
 
 Plugins act as an abstraction layer between the monitoring logic present in the Naemon daemon and the actual services and hosts that are being monitored.
 
-The upside of this type of plugin architecture is that you can monitor just about anything you can think of.  If you can automate the process of checking something, you can monitor it with Naemon.  There are already a lot of plugins that have been created in order to monitor basic resources such as processor load, disk usage, ping rates, etc.  If you want to monitor something else, take a look at the documentation on <a href="pluginapi.html">writing plugins</a> and roll your own.  Its simple!
+The upside of this type of plugin architecture is that you can monitor just about anything you can think of.  If you can automate the process of checking something, you can monitor it with Naemon.  There are already a lot of plugins that have been created in order to monitor basic resources such as processor load, disk usage, ping rates, etc.  If you want to monitor something else, take a look at the documentation on [writing plugins](pluginapi) and roll your own.  Its simple!
 
-The downside to this type of plugin architecture is the fact that Naemon has absolutely no idea what it is that you're monitoring.  You could be monitoring network traffic statistics, data error rates, room temperate, CPU voltage, fan speed, processor load, disk space, or the ability of your super-fantastic toaster to properly brown your bread in the morning...  Naemon doesn't understand the specifics of what's being monitored - it just tracks changes in the <i>state</i> of those resources.  Only the plugins themselves know exactly what they're monitoring and how to perform the actual checks.
+The downside to this type of plugin architecture is the fact that Naemon has absolutely no idea what it is that you're monitoring.  You could be monitoring network traffic statistics, data error rates, room temperate, CPU voltage, fan speed, processor load, disk space, or the ability of your super-fantastic toaster to properly brown your bread in the morning...  Naemon doesn't understand the specifics of what's being monitored - it just tracks changes in the *state* of those resources.  Only the plugins themselves know exactly what they're monitoring and how to perform the actual checks.
 
-### What Plugins Are Available?
+## What Plugins Are Available?
 
 There are plugins currently available to monitor many different kinds of devices and services, including:
 
-<ul>
-<li>HTTP, POP3, IMAP, FTP, SSH, DHCP</li>
-<li>CPU Load, Disk Usage, Memory Usage, Current Users</li>
-<li>Unix/Linux, Windows, and Netware Servers</li>
-<li>Routers and Switches</li>
-<li>etc.</li>
-</ul>
 
-### Obtaining Plugins
+- HTTP, POP3, IMAP, FTP, SSH, DHCP
+- CPU Load, Disk Usage, Memory Usage, Current Users
+- Unix/Linux, Windows, and Netware Servers
+- Routers and Switches
+- etc.
+
+
+## Obtaining Plugins
 
 Plugins are not distributed with Naemon, but you can download Naemon plugins and many additional plugins created and maintained by Naemon and Nagios users from the following locations:
 
-<ul>
-<li>Monitoring Plugins Project: <a href="http://monitoring-plugins.org">http://monitoring-plugins.org</a></li>
-<li>Nagios Plugins Project: <a href="https://nagios-plugins.org/">https://nagios-plugins.org/</a></li>
-<li>Nagios Exchange: <a href="http://exchange.nagios.org/">http://exchange.nagios.org/</a></li>
-</ul>
 
-### How Do I Use Plugin <i>X</i>?
+- Monitoring Plugins Project: [https://www.monitoring-plugins.org/](https://www.monitoring-plugins.org/)
+- Nagios Exchange: [https://exchange.nagios.org/](https://exchange.nagios.org/)
+
+
+## How Do I Use Plugin *X*?
 
-Most all plugins will display basic usage information when you execute them using '-h' or '--help' on the command line.  For example, if you want to know how the check_http plugin works or what options it accepts, you should try executing the following command:
+Most all plugins will display basic usage information when you execute them using `-h` or `--help` on the command line.  For example, if you want to know how the check_http plugin works or what options it accepts, you should try executing the following command:
 
-<pre>
+```bash
 ./check_http --help
-</pre>
+```
 
-<a name="howto"></a>
 
-### Plugin API
+## Plugin API {#howto}
 
-You can find information on the technical aspects of plugins, as well as how to go about creating your own custom plugins <a href="pluginapi.html">here</a>.
+You can find information on the technical aspects of plugins, as well as how to go about creating your own custom plugins [here](pluginapi).

src/documentation/usersguide/toc.md

@@ -79,7 +79,7 @@
 
 ## The Basics {#basics}
 
-[Plugins](plugins)
+[Plugins](plugins) :white_check_mark:
 
 [Macros and how they work](macros)