diff --git a/docs/PLUGINS_DEV.md b/docs/PLUGINS_DEV.md
index 1dd93ed1..87b7df5a 100755
--- a/docs/PLUGINS_DEV.md
+++ b/docs/PLUGINS_DEV.md
@@ -1,22 +1,42 @@
-# Creating a custom plugin
+# Plugin Development Guide
 
-NetAlertX comes with a plugin system to feed events from third-party scripts into the UI and then send notifications, if desired. The highlighted core functionality this plugin system supports, is:
-
-* dynamic creation of a simple UI to interact with the discovered objects,
-* filtering of displayed values in the Devices UI
-* surface settings of plugins in the UI,
-* different column types for reported values to e.g. link back to a device
-* import objects into existing NetAlertX database tables
-
-> (Currently, update/overwriting of existing objects is only supported for devices via the `CurrentScan` table.)
-
-> [!NOTE]
-> For a high-level overview of how the `config.json` is used and it's lifecycle check the [config.json Lifecycle in NetAlertX Guide](PLUGINS_DEV_CONFIG.md).
-
-### 🎥 Watch the video:
+This comprehensive guide covers how to build plugins for NetAlertX.
 
 > [!TIP]
-> Read this guide [Development environment setup guide](./DEV_ENV_SETUP.md) to set up your local environment for development. 👩‍💻
+> **New to plugin development?** Start with the [Quick Start Guide](PLUGINS_DEV_QUICK_START.md) to get a working plugin in 5 minutes.
+
+NetAlertX comes with a plugin system to feed events from third-party scripts into the UI and then send notifications, if desired. The highlighted core functionality this plugin system supports:
+
+* **Dynamic UI generation** - Automatically create tables for discovered objects
+* **Data filtering** - Filter and link values in the Devices UI
+* **User settings** - Surface plugin configuration in the Settings UI
+* **Rich display types** - Color-coded badges, links, formatted text, and more
+* **Database integration** - Import plugin data into NetAlertX tables like `CurrentScan` or `Devices`
+
+> [!NOTE]
+> For a high-level overview of how the `config.json` is used and its lifecycle, see the [config.json Lifecycle Guide](PLUGINS_DEV_CONFIG.md).
+
+## Quick Links
+
+### 🚀 Getting Started
+- **[Quick Start Guide](PLUGINS_DEV_QUICK_START.md)** - Create a working plugin in 5 minutes
+- **[Development Environment Setup](./DEV_ENV_SETUP.md)** - Set up your local development environment
+
+### 📚 Core Concepts
+- **[Data Contract](PLUGINS_DEV_DATA_CONTRACT.md)** - The exact output format plugins must follow (9-13 columns, pipe-delimited)
+- **[Data Sources](PLUGINS_DEV_DATASOURCES.md)** - How plugins retrieve data (scripts, databases, templates)
+- **[Plugin Settings System](PLUGINS_DEV_SETTINGS.md)** - Let users configure your plugin via the UI
+- **[UI Components](PLUGINS_DEV_UI_COMPONENTS.md)** - Display plugin results with color coding, links, and more
+
+### 🏗️ Architecture
+- **[Plugin Config Lifecycle](PLUGINS_DEV_CONFIG.md)** - How `config.json` is loaded and used
+- **[Full Plugin Development Reference](#full-reference-below)** - Comprehensive details on all aspects
+
+### 🐛 Troubleshooting
+- **[Debugging Plugins](DEBUG_PLUGINS.md)** - Troubleshoot plugin issues
+- **[Plugin Examples](../front/plugins)** - Study existing plugins as reference implementations
+
+### 🎥 Video Tutorial
 
 [![Watch the video](./img/YouTube_thumbnail.png)](https://youtu.be/cdbxlwiWhv8)
 
@@ -26,768 +46,295 @@ NetAlertX comes with a plugin system to feed events from third-party scripts int
 |----------------------|----------------------| ----------------------|
 | ![Screen 4][screen4] |  ![Screen 5][screen5] |
 
-## Use cases
+## Use Cases
 
-Example use cases for plugins could be:
+Plugins are infinitely flexible. Here are some examples:
 
-* Monitor a web service and alert me if it's down
-* Import devices from dhcp.leases files instead/complementary to using PiHole or arp-scans
-* Creating ad-hoc UI tables from existing data in the NetAlertX database, e.g. to show all open ports on devices, to list devices that disconnected in the last hour, etc.
-* Using other device discovery methods on the network and importing the data as new devices
-* Creating a script to create FAKE devices based on user input via custom settings
-* ...at this point the limitation is mostly the creativity rather than the capability (there might be edge cases and a need to support more form controls for user input off custom settings, but you probably get the idea)
+* **Device Discovery** - Scan networks using ARP, mDNS, DHCP leases, or custom protocols
+* **Service Monitoring** - Monitor web services, APIs, or network services for availability
+* **Integration** - Import devices from PiHole, Home Assistant, Unifi, or other systems
+* **Enrichment** - Add data like geolocation, threat intelligence, or asset metadata
+* **Alerting** - Send notifications to Slack, Discord, Telegram, email, or webhooks
+* **Reporting** - Generate insights from existing NetAlertX database (open ports, recent changes, etc.)
+* **Custom Logic** - Create fake devices, trigger automations, or implement custom heuristics
 
-If you wish to develop a plugin, please check the existing plugin structure. Once the settings are saved by the user they need to be removed from the `app.conf` file manually if you want to re-initialize them from the `config.json` of the plugin.
+If you can imagine it and script it, you can build a plugin.
 
-## ⚠ Disclaimer
+## Limitations & Notes
 
-Please read the below carefully if you'd like to contribute with a plugin yourself. This documentation file might be outdated, so double-check the existing plugins as well.
+- Plugin data is deduplicated hourly (same Primary ID + Secondary ID + User Data = duplicate removed)
+- Currently, only `CurrentScan` table supports update/overwrite of existing objects
+- Plugin results must follow the strict [Data Contract](PLUGINS_DEV_DATA_CONTRACT.md)
+- Plugins run with the same permissions as the NetAlertX process
+- External dependencies must be installed in the container
 
-## Plugin development quick start
+## Plugin Development Workflow
 
-1. Create a new folder for your plugin (e.g. `my_plugin`)
-1. Copy the files from the `__template` folder into the newly created folder
-1. Update the relevant attributes in the `config.json` file, especially `code_name` and `unique_prefix`, e.g.:
-  - `"code_name": "my_plugin"` - must match the folder name
-  - `"unique_prefix": "MYPLG"` - has to be unique, upper case letters only
-1. Update the `RUN` setting to point to your script file
-1. Update the rest of the `config.json` sections and implement the actual data retrieval in our python script
+### Step 1: Understand the Basics
+1. Read [Quick Start Guide](PLUGINS_DEV_QUICK_START.md) - 5 minute overview
+2. Study the [Data Contract](PLUGINS_DEV_DATA_CONTRACT.md) - Understand the output format
+3. Choose a [Data Source](PLUGINS_DEV_DATASOURCES.md) - Where does your data come from?
 
-## Plugin file structure overview
+### Step 2: Create Your Plugin
+1. Copy the `__template` plugin folder (see below for structure)
+2. Update `config.json` with your plugin metadata
+3. Implement `script.py` (or configure alternative data source)
+4. Test locally in the devcontainer
 
-> ⚠️Folder name must be the same as the code name value in: `"code_name": "<value>"`
-> Unique prefix needs to be unique compared to the other settings prefixes, e.g.: the prefix `APPRISE` is already in use.
+### Step 3: Configure & Display
+1. Define [Settings](PLUGINS_DEV_SETTINGS.md) for user configuration
+2. Design [UI Components](PLUGINS_DEV_UI_COMPONENTS.md) for result display
+3. Map to database tables if needed (for notifications, etc.)
 
-  | File | Required (plugin type) | Description |
-  |----------------------|----------------------|----------------------|
-  | `config.json` | yes | Contains the plugin configuration (manifest) including the settings available to the user. |
-  | `script.py` |  no | The Python script itself. You may call any valid linux command.  |
-  | `last_result.<prefix>.log` | no | The file used to interface between NetAlertX and the plugin. Required for a script plugin if you want to feed data into the app. Stored in the `/api/log/plugins/` |
-  | `README.md` | yes | Any setup considerations or overview  |
+### Step 4: Deploy & Test
+1. Restart the backend
+2. Test via Settings → Plugin Settings
+3. Verify results in UI and logs
+4. Check `/tmp/log/plugins/last_result.<PREFIX>.log`
+
+See [Quick Start Guide](PLUGINS_DEV_QUICK_START.md) for detailed step-by-step instructions.
+
+## Plugin File Structure
+
+Every plugin lives in its own folder under `/app/front/plugins/`.
+
+> **Important:** Folder name must match the `"code_name"` value in `config.json`
+
+```
+/app/front/plugins/
+├── __template/          # Copy this as a starting point
+│   ├── config.json      # Plugin manifest (configuration)
+│   ├── script.py        # Your plugin logic (optional, depends on data_source)
+│   └── README.md        # Setup and usage documentation
+├── my_plugin/           # Your new plugin
+│   ├── config.json      # REQUIRED - Plugin manifest
+│   ├── script.py        # OPTIONAL - Python script (if using script data source)
+│   ├── README.md        # REQUIRED - Documentation for users
+│   └── other_files...   # Your supporting files
+```
+
+## Plugin Manifest (config.json)
+
+The `config.json` file is the **plugin manifest** - it tells NetAlertX everything about your plugin:
+
+- **Metadata:** Plugin name, description, icon
+- **Execution:** When to run, what command to run, timeout
+- **Settings:** User-configurable options
+- **Data contract:** Column definitions and how to display results
+- **Integration:** Database mappings, notifications, filters
+
+**Example minimal config.json:**
+
+```json
+{
+  "code_name": "my_plugin",
+  "unique_prefix": "MYPLN",
+  "display_name": [{"language_code": "en_us", "string": "My Plugin"}],
+  "description": [{"language_code": "en_us", "string": "My awesome plugin"}],
+  "icon": "fa-plug",
+  "data_source": "script",
+  "execution_order": "Layer_0",
+  "settings": [
+    {
+      "function": "RUN",
+      "type": {"dataType": "string", "elements": [{"elementType": "select", "elementOptions": [], "transformers": []}]},
+      "default_value": "disabled",
+      "options": ["disabled", "once", "schedule"],
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "When to run"}]
+    },
+    {
+      "function": "CMD",
+      "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+      "default_value": "python3 /app/front/plugins/my_plugin/script.py",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "Command"}]
+    }
+  ],
+  "database_column_definitions": []
+}
+```
+
+> For comprehensive `config.json` documentation, see [PLUGINS_DEV_CONFIG.md](PLUGINS_DEV_CONFIG.md)
+
+## Full Reference (Below)
+
+The sections below provide complete reference documentation for all plugin development topics. Use the quick links above to jump to specific sections, or read sequentially for a deep dive.
 
 More on specifics below.
 
-### Column order and values (plugins interface contract)
+---
 
-> [!IMPORTANT]
-> Spend some time reading and trying to understand the below table. This is the interface between the Plugins and the core application. The application expets 9 or 13 values The first 9 values are mandatory. The next 4 values (`HelpVal1` to `HelpVal4`) are optional. However, if you use any of these optional values (e.g., `HelpVal1`), you need to supply all optional values (e.g., `HelpVal2`, `HelpVal3`, and `HelpVal4`). If a value is not used, it should be padded with `null`.
+## Data Contract & Output Format
 
-  | Order | Represented Column | Value Required | Description |
-  |----------------------|----------------------|----------------------|----------------------|
-  | 0 | `Object_PrimaryID` | yes | The primary ID used to group Events under. |
-  | 1 | `Object_SecondaryID` | no | Optional secondary ID to create a relationship beween other entities, such as a MAC address |
-  | 2 | `DateTime` | yes | When the event occured in the format `2023-01-02 15:56:30` |
-  | 3 | `Watched_Value1` | yes | A value that is watched and users can receive notifications if it changed compared to the previously saved entry. For example IP address |
-  | 4 | `Watched_Value2` | no | As above |
-  | 5 | `Watched_Value3` | no | As above  |
-  | 6 | `Watched_Value4` | no | As above  |
-  | 7 | `Extra` | no | Any other data you want to pass and display in NetAlertX and the notifications |
-  | 8 | `ForeignKey` | no | A foreign key that can be used to link to the parent object (usually a MAC address) |
-  | 9 | `HelpVal1` | no | (optional) A helper value |
-  | 10 | `HelpVal2` | no | (optional) A helper value |
-  | 11 | `HelpVal3` | no | (optional) A helper value |
-  | 12 | `HelpVal4` | no | (optional) A helper value |
+For detailed information on plugin output format, see **[PLUGINS_DEV_DATA_CONTRACT.md](PLUGINS_DEV_DATA_CONTRACT.md)**.
 
+Quick reference:
+- **Format:** Pipe-delimited (`|`) text file
+- **Location:** `/tmp/log/plugins/last_result.<PREFIX>.log`
+- **Columns:** 9 required + 4 optional = 13 maximum
+- **Helper:** Use `plugin_helper.py` for easy formatting
 
-> [!NOTE]
-> De-duplication is run once an hour on the `Plugins_Objects` database table and duplicate entries with the same value in columns `Object_PrimaryID`, `Object_SecondaryID`, `Plugin` (auto-filled based on `unique_prefix` of the plugin), `UserData` (can be populated with the `"type": "textbox_save"` column type) are removed.
+### The 9 Mandatory Columns
 
-# config.json structure
+| Column | Name | Required | Example |
+|--------|------|----------|---------|
+| 0 | Object_PrimaryID | **YES** | `"device_name"` or `"192.168.1.1"` |
+| 1 | Object_SecondaryID | no | `"secondary_id"` or `null` |
+| 2 | DateTime | **YES** | `"2023-01-02 15:56:30"` |
+| 3 | Watched_Value1 | **YES** | `"online"` or `"200"` |
+| 4 | Watched_Value2 | no | `"ip_address"` or `null` |
+| 5 | Watched_Value3 | no | `null` |
+| 6 | Watched_Value4 | no | `null` |
+| 7 | Extra | no | `"additional data"` or `null` |
+| 8 | ForeignKey | no | `"aa:bb:cc:dd:ee:ff"` or `null` |
 
-The `config.json` file is the manifest of the plugin. It contains mainly settings definitions and the mapping of Plugin objects to NetAlertX objects.
+See [Data Contract](PLUGINS_DEV_DATA_CONTRACT.md) for examples, validation, and debugging tips.
 
-## Execution order
+---
 
-The execution order is used to specify when a plugin is executed. This is useful if a plugin has access and surfaces more information than others. If a device is detected by 2 plugins and inserted into the `CurrentScan` table, the plugin with the higher priority (e.g.: `Level_0` is a higher priority than `Level_1`) will insert it's values first. These values (devices) will be then prioritized over any values inserted later.
+## Config.json: Settings & Configuration
+
+For detailed settings documentation, see **[PLUGINS_DEV_SETTINGS.md](PLUGINS_DEV_SETTINGS.md)** and **[PLUGINS_DEV_DATASOURCES.md](PLUGINS_DEV_DATASOURCES.md)**.
+
+### Setting Object Structure
+
+Every setting in your plugin has this structure:
 
 ```json
 {
-    "execution_order" : "Layer_0"
+  "function": "UNIQUE_CODE",
+  "type": {"dataType": "string", "elements": [...]},
+  "default_value": "...",
+  "options": [...],
+  "localized": ["name", "description"],
+  "name": [{"language_code": "en_us", "string": "Display Name"}],
+  "description": [{"language_code": "en_us", "string": "Help text"}]
 }
 ```
 
-## Supported data sources
+### Reserved Function Names
 
-Currently, these data sources are supported (valid `data_source` value).
+These control core plugin behavior:
 
-| Name | `data_source` value | Needs to return a "table"* | Overview (more details on this page below) |
-|----------------------|----------------------|----------------------|----------------------|
-| Script | `script` | no | Executes any linux command in the `CMD` setting. |
-| NetAlertX DB query | `app-db-query` | yes | Executes a SQL query on the NetAlertX database in the `CMD` setting. |
-| Template | `template` | no | Used to generate internal settings, such as default values. |
-| External SQLite DB query | `sqlite-db-query` | yes | Executes a SQL query from the `CMD` setting on an external SQLite database mapped in the `DB_PATH` setting.  |
-| Plugin type | `plugin_type` | no | Specifies the type of the plugin and in which section the Plugin settings are displayed ( one of `general/system/scanner/other/publisher` ). |
+| Function | Purpose | Required | Options |
+|----------|---------|----------|---------|
+| `RUN` | When to execute | **YES** | `disabled`, `once`, `schedule`, `always_after_scan`, `before_name_updates`, `on_new_device` |
+| `RUN_SCHD` | Cron schedule | If `RUN=schedule` | Cron format: `"0 * * * *"` |
+| `CMD` | Command to run | **YES** | Shell command or script path |
+| `RUN_TIMEOUT` | Max execution time | optional | Seconds: `"60"` |
+| `WATCH` | Monitor for changes | optional | Column names |
+| `REPORT_ON` | When to notify | optional | `new`, `watched-changed`, `watched-not-changed`, `missing-in-last-scan` |
+| `DB_PATH` | External DB path | If using SQLite | `/path/to/db.db` |
 
-> * "Needs to return a "table" means that the application expects a `last_result.<prefix>.log` file with some results. It's not a blocker, however warnings in the `app.log` might be logged.
+See [PLUGINS_DEV_SETTINGS.md](PLUGINS_DEV_SETTINGS.md) for full component types and examples.
 
-> 🔎Example
->```json
->"data_source":  "app-db-query"
->```
-If you want to display plugin objects or import devices into the app, data sources have to return a "table" of the exact structure as outlined above.
+---
 
-You can show or hide the UI on the "Plugins" page and "Plugins" tab for a plugin on devices via the `show_ui` property:
+## Filters & Data Display
 
-> 🔎Example
->```json
-> "show_ui": true,
-> ```
+For comprehensive display configuration, see **[PLUGINS_DEV_UI_COMPONENTS.md](PLUGINS_DEV_UI_COMPONENTS.md)**.
 
-### "data_source":  "script"
+### Filters
 
- If the `data_source` is set to `script` the `CMD` setting (that you specify in the `settings` array section in the `config.json`) contains an executable Linux command, that usually generates a `last_result.<prefix>.log` file (not required if you don't import any data into the app). The `last_result.<prefix>.log` file needs to be saved in `/api/log/plugins`.
+Control which rows display in the UI:
 
-> [!IMPORTANT]
-> A lot of the work is taken care of by the [`plugin_helper.py` library](/front/plugins/plugin_helper.py). You don't need to manage the `last_result.<prefix>.log` file if using the helper objects. Check other `script.py` of other plugins for details.
-
- The content of the `last_result.<prefix>.log` file needs to contain the columns as defined in the "Column order and values" section above. The order of columns can't be changed. After every scan it should contain only the results from the latest scan/execution.
-
-- The format of the `last_result.<prefix>.log` is a `csv`-like file with the pipe `|` as a separator.
-- 9 (nine) values need to be supplied, so every line needs to contain 8 pipe separators. Empty values are represented by `null`.
-- Don't render "headers" for these "columns".
-Every scan result/event entry needs to be on a new line.
-- You can find which "columns" need to be present, and if the value is required or optional, in the "Column order and values" section.
-- The order of these "columns" can't be changed.
-
-#### 🔎 last_result.prefix.log examples
-
-Valid CSV:
-
-```csv
-
-https://www.google.com|null|2023-01-02 15:56:30|200|0.7898|null|null|null|null
-https://www.duckduckgo.com|192.168.0.1|2023-01-02 15:56:30|200|0.9898|null|null|Best search engine|ff:ee:ff:11:ff:11
-
-```
-
-Invalid CSV with different errors on each line:
-
-```csv
-
-https://www.google.com|null|2023-01-02 15:56:30|200|0.7898||null|null|null
-https://www.duckduckgo.com|null|2023-01-02 15:56:30|200|0.9898|null|null|Best search engine|
-|https://www.duckduckgo.com|null|2023-01-02 15:56:30|200|0.9898|null|null|Best search engine|null
-null|192.168.1.1|2023-01-02 15:56:30|200|0.9898|null|null|Best search engine
-https://www.duckduckgo.com|192.168.1.1|2023-01-02 15:56:30|null|0.9898|null|null|Best search engine
-https://www.google.com|null|2023-01-02 15:56:30|200|0.7898|||
-https://www.google.com|null|2023-01-02 15:56:30|200|0.7898|
-
-```
-
-### "data_source":  "app-db-query"
-
-If the `data_source` is set to `app-db-query`, the `CMD` setting needs to contain a SQL query rendering the columns as defined in the "Column order and values" section above. The order of columns is important.
-
-This SQL query is executed on the `app.db` SQLite database file.
-
->  🔎Example
->
-> SQL query example:
->
-> ```SQL
-> SELECT  dv.devName as Object_PrimaryID,
->     cast(dv.devLastIP as VARCHAR(100)) || ':' || cast( SUBSTR(ns.Port ,0, INSTR(ns.Port , '/')) as VARCHAR(100)) as Object_SecondaryID,
->     datetime() as DateTime,
->     ns.Service as Watched_Value1,
->     ns.State as Watched_Value2,
->     'null' as Watched_Value3,
->     'null' as Watched_Value4,
->     ns.Extra as Extra,
->     dv.devMac as ForeignKey
-> FROM
->     (SELECT * FROM Nmap_Scan) ns
-> LEFT JOIN
->     (SELECT devName, devMac, devLastIP FROM Devices) dv
-> ON ns.MAC = dv.devMac
-> ```
->
-> Required `CMD` setting example with above query (you can set `"type": "label"` if you want it to make uneditable in the UI):
->
-> ```json
-> {
->             "function": "CMD",
->            "type": {"dataType":"string", "elements": [{"elementType" : "input", "elementOptions" : [] ,"transformers": []}]},
->            "default_value":"SELECT  dv.devName as Object_PrimaryID, cast(dv.devLastIP as VARCHAR(100)) || ':' || cast( SUBSTR(ns.Port ,0, INSTR(ns.Port , '/')) as VARCHAR(100)) as Object_SecondaryID,  datetime() as DateTime,  ns.Service as Watched_Value1,        ns.State as Watched_Value2,        'null' as Watched_Value3,        'null' as Watched_Value4,        ns.Extra as Extra        FROM (SELECT * FROM Nmap_Scan) ns LEFT JOIN (SELECT devName, devMac, devLastIP FROM Devices) dv   ON ns.MAC = dv.devMac",
->            "options": [],
->            "localized": ["name", "description"],
->            "name" : [{
->                "language_code":"en_us",
->                "string" : "SQL to run"
->            }],
->             "description": [{
->                 "language_code":"en_us",
->                 "string" : "This SQL query is used to populate the coresponding UI tables under the Plugins section."
->             }]
->         }
-> ```
-
-### "data_source":  "template"
-
-In most cases, it is used to initialize settings. Check the `newdev_template` plugin for details.
-
-### "data_source":  "sqlite-db-query"
-
-You can execute a SQL query on an external database connected to the current NetAlertX database via a temporary `EXTERNAL_<unique prefix>.` prefix.
-
-For example for `PIHOLE` (`"unique_prefix": "PIHOLE"`) it is `EXTERNAL_PIHOLE.`. The external SQLite database file has to be mapped in the container to the path specified in the `DB_PATH` setting:
-
->  🔎Example
->
->```json
->  ...
->{
->        "function": "DB_PATH",
->        "type": {"dataType":"string", "elements": [{"elementType" : "input", "elementOptions" : [{"readonly": "true"}] ,"transformers": []}]},
->        "default_value":"/etc/pihole/pihole-FTL.db",
->        "options": [],
->        "localized": ["name", "description"],
->        "name" : [{
->            "language_code":"en_us",
->            "string" : "DB Path"
->        }],
->        "description": [{
->            "language_code":"en_us",
->            "string" : "Required setting for the <code>sqlite-db-query</code> plugin type. Is used to mount an external SQLite database and execute the SQL query stored in the <code>CMD</code> setting."
->        }]
->    }
->  ...
->```
-
-The actual SQL query you want to execute is then stored as a `CMD` setting, similar to a Plugin of the `app-db-query` plugin type. The format has to adhere to the format outlined in the "Column order and values" section above.
-
->  🔎Example
->
-> Notice the `EXTERNAL_PIHOLE.` prefix.
->
->```json
->{
->      "function": "CMD",
->      "type": {"dataType":"string", "elements": [{"elementType" : "input", "elementOptions" : [] ,"transformers": []}]},
->      "default_value":"SELECT hwaddr as Object_PrimaryID, cast('http://' || (SELECT ip FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC, ip LIMIT 1) as VARCHAR(100)) || ':' || cast( SUBSTR((SELECT name FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC, ip LIMIT 1), 0, INSTR((SELECT name FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC, ip LIMIT 1), '/')) as VARCHAR(100)) as Object_SecondaryID, datetime() as DateTime, macVendor as Watched_Value1, lastQuery as Watched_Value2, (SELECT name FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC, ip LIMIT 1) as Watched_Value3, 'null' as Watched_Value4, '' as Extra, hwaddr as ForeignKey FROM EXTERNAL_PIHOLE.network WHERE hwaddr NOT LIKE 'ip-%' AND hwaddr <> '00:00:00:00:00:00';            ",
->      "options": [],
->      "localized": ["name", "description"],
->      "name" : [{
->          "language_code":"en_us",
->          "string" : "SQL to run"
->      }],
->      "description": [{
->          "language_code":"en_us",
->          "string" : "This SQL query is used to populate the coresponding UI tables under the Plugins section. This particular one selects data from a mapped PiHole SQLite database and maps it to the corresponding Plugin columns."
->      }]
->  }
->  ```
-
-## 🕳 Filters
-
-Plugin entries can be filtered in the UI based on values entered into filter fields. The `txtMacFilter` textbox/field contains the Mac address of the currently viewed device, or simply a Mac address that's available in the `mac` query string (`<url>?mac=aa:22:aa:22:aa:22:aa`).
-
-  | Property | Required | Description |
-  |----------------------|----------------------|----------------------|
-  | `compare_column` | yes | Plugin column name that's value is used for comparison (**Left** side of the equation) |
-  | `compare_operator` |  yes | JavaScript comparison operator |
-  | `compare_field_id` | yes | The `id` of a input text field containing a value is used for comparison (**Right** side of the equation)|
-  | `compare_js_template` | yes | JavaScript code used to convert left and right side of the equation. `{value}` is replaced with input values. |
-  | `compare_use_quotes` | yes | If `true` then the end result of the `compare_js_template` i swrapped in `"` quotes. Use to compare strings. |
-
-  Filters are only applied if a filter is specified, and the `txtMacFilter` is not `undefined`, or empty (`--`).
-
-> 🔎Example:
->
-> ```json
->     "data_filters": [
->         {
->             "compare_column" : "Object_PrimaryID",
->             "compare_operator" : "==",
->             "compare_field_id": "txtMacFilter",
->             "compare_js_template": "'{value}'.toString()",
->             "compare_use_quotes": true
->         }
->     ],
-> ```
->
->1. On the `pluginsCore.php` page is an input field with the id `txtMacFilter`:
->
->```html
-><input class="form-control" id="txtMacFilter" type="text" value="--">
->```
->
->2. This input field is initialized via the `&mac=` query string.
->
->3. The app then proceeds to use this Mac value from this field and compares it to the value of the `Object_PrimaryID` database field. The `compare_operator` is `==`.
->
->4. Both values, from the database field `Object_PrimaryID` and from the `txtMacFilter` are wrapped and evaluated with the `compare_js_template`, that is `'{value}.toString()'`.
->
->5. `compare_use_quotes` is set to `true` so `'{value}'.toString()` is wrappe dinto `"` quotes.
->
->6. This results in for example this code:
->
->```javascript
->    // left part of the expression coming from compare_column and right from the input field
->    // notice the added quotes ()") around the left and right part of teh expression
->    "eval('ac:82:ac:82:ac:82".toString()')" == "eval('ac:82:ac:82:ac:82".toString()')"
->```
->
-
-
-### 🗺 Mapping the plugin results into a database table
-
-Plugin results are always inserted into the standard `Plugin_Objects` database table. Optionally, NetAlertX can take the results of the plugin execution, and insert these results into an additional database table. This is enabled by with the property `"mapped_to_table"` in the `config.json` file. The mapping of the columns is defined in the `database_column_definitions` array.
-
-> [!NOTE]
-> If results are mapped to the `CurrentScan` table, the data is then included into the regular scan loop, so for example notification for devices are sent out.
-
-
->🔍 Example:
->
->For example, this approach is used to implement the `DHCPLSS` plugin. The script parses all supplied "dhcp.leases" files, gets the results in the generic table format outlined in the "Column order and values" section above, takes individual values, and inserts them into the `CurrentScan` database table in the NetAlertX database. All this is achieved by:
->
->1. Specifying the database table into which the results are inserted by defining `"mapped_to_table": "CurrentScan"` in the root of the `config.json` file as shown below:
->
->```json
->{
->    "code_name": "dhcp_leases",
->    "unique_prefix": "DHCPLSS",
->    ...
->    "data_source":  "script",
->    "localized": ["display_name", "description", "icon"],
->    "mapped_to_table": "CurrentScan",
->    ...
->}
->```
->2. Defining the target column with the `mapped_to_column` property for individual columns in the `database_column_definitions` array of the `config.json` file. For example in the `DHCPLSS` plugin, I needed to map the value of the `Object_PrimaryID` column returned by the plugin, to the `cur_MAC` column in the NetAlertX database table `CurrentScan`. Notice the  `"mapped_to_column": "cur_MAC"` key-value pair in the sample below.
->
->```json
->{
->            "column": "Object_PrimaryID",
->            "mapped_to_column": "cur_MAC",
->            "css_classes": "col-sm-2",
->            "show": true,
->            "type": "device_mac",
->            "default_value":"",
->            "options": [],
->            "localized": ["name"],
->            "name":[{
->                "language_code":"en_us",
->                "string" : "MAC address"
->                }]
->        }
->```
->
->3.  That's it. The app takes care of the rest. It loops thru the objects discovered by the plugin, takes the results line-by-line, and inserts them into the database table specified in `"mapped_to_table"`. The columns are translated from the generic plugin columns to the target table columns via the `"mapped_to_column"` property in the column definitions.
-
-> [!NOTE]
-> You can create a column mapping with a default value via the `mapped_to_column_data` property. This means that the value of the given column will always be this value. That also means that the `"column": "NameDoesntMatter"` is not important as there is no database source column.
-
-
->🔍 Example:
->
->```json
->{
->            "column": "NameDoesntMatter",
->            "mapped_to_column": "cur_ScanMethod",
->            "mapped_to_column_data": {
->                "value": "DHCPLSS"
->            },
->            "css_classes": "col-sm-2",
->            "show": true,
->            "type": "device_mac",
->            "default_value":"",
->            "options": [],
->            "localized": ["name"],
->            "name":[{
->                "language_code":"en_us",
->                "string" : "MAC address"
->                }]
->        }
->```
-
-#### params
-
-> [!IMPORTANT]
-> An esier way to access settings in scripts is the `get_setting_value` method.
-> ```python
-> from helper import get_setting_value
->
->   ...
->   NTFY_TOPIC = get_setting_value('NTFY_TOPIC')
->   ...
->
-> ```
-
-The `params` array in the `config.json` is used to enable the user to change the parameters of the executed script. For example, the user wants to monitor a specific URL.
-
-> 🔎 Example:
-> Passing user-defined settings to a command. Let's say, you want to have a script, that is called with a user-defined parameter called `urls`:
->
-> ```bash
-> root@server# python3 /app/front/plugins/website_monitor/script.py urls=https://google.com,https://duck.com
-> ```
-
-* You can allow the user to add URLs to a setting with the `function` property set to a custom name, such as `urls_to_check` (this is not a reserved name from the section "Supported settings `function` values" below).
-* You specify the parameter `urls` in the `params` section of the `config.json` the following way (`WEBMON_` is the plugin prefix automatically added to all the settings):
 ```json
 {
-    "params" : [
-        {
-            "name"  : "urls",
-            "type"  : "setting",
-            "value" : "WEBMON_urls_to_check"
-        }]
+  "data_filters": [
+    {
+      "compare_column": "Object_PrimaryID",
+      "compare_operator": "==",
+      "compare_field_id": "txtMacFilter",
+      "compare_js_template": "'{value}'.toString()",
+      "compare_use_quotes": true
+    }
+  ]
 }
 ```
-* Then you use this setting as an input parameter for your command in the `CMD` setting. Notice `urls={urls}` in the below json:
 
-```json
- {
-            "function": "CMD",
-            "type": {"dataType":"string", "elements": [{"elementType" : "input", "elementOptions" : [] ,"transformers": []}]},
-            "default_value":"python3 /app/front/plugins/website_monitor/script.py urls={urls}",
-            "options": [],
-            "localized": ["name", "description"],
-            "name" : [{
-                "language_code":"en_us",
-                "string" : "Command"
-            }],
-            "description": [{
-                "language_code":"en_us",
-                "string" : "Command to run"
-            }]
-        }
-```
-
-During script execution, the app will take the command `"python3 /app/front/plugins/website_monitor/script.py urls={urls}"`, take the `{urls}` wildcard and replace it with the value from the `WEBMON_urls_to_check` setting. This is because:
-
-1. The app checks the `params` entries
-2. It finds `"name"  : "urls"`
-3. Checks the type of the `urls` params and finds `"type"  : "setting"`
-4. Gets the setting name from  `"value" : "WEBMON_urls_to_check"`
-   - IMPORTANT: in the `config.json` this setting is identified by `"function":"urls_to_check"`, not `"function":"WEBMON_urls_to_check"`
-   - You can also use a global setting, or a setting from a different plugin
-5. The app gets the user defined value from the setting with the code name `WEBMON_urls_to_check`
-   - let's say the setting with the code name  `WEBMON_urls_to_check` contains 2 values entered by the user:
-   - `WEBMON_urls_to_check=['https://google.com','https://duck.com']`
-6. The app takes the value from `WEBMON_urls_to_check` and replaces the `{urls}` wildcard in the setting where `"function":"CMD"`, so you go from:
-   - `python3 /app/front/plugins/website_monitor/script.py urls={urls}`
-   - to
-   - `python3 /app/front/plugins/website_monitor/script.py urls=https://google.com,https://duck.com`
-
-Below are some general additional notes, when defining `params`:
-
-- `"name":"name_value"` - is used as a wildcard replacement in the `CMD` setting value by using curly brackets `{name_value}`. The wildcard is replaced by the result of the `"value" : "param_value"` and `"type":"type_value"` combo configuration below.
-- `"type":"<sql|setting>"` - is used to specify the type of the params, currently only 2 supported (`sql`,`setting`).
-  - `"type":"sql"` - will execute the SQL query specified in the `value` property. The sql query needs to return only one column. The column is flattened and separated by commas (`,`), e.g: `SELECT devMac from DEVICES` -> `Internet,74:ac:74:ac:74:ac,44:44:74:ac:74:ac`. This is then used to replace the wildcards in the `CMD` setting.
-  - `"type":"setting"` - The setting code name. A combination of the value from `unique_prefix` + `_` + `function` value, or otherwise the code name you can find in the Settings page under the Setting display name, e.g. `PIHOLE_RUN`.
-- `"value": "param_value"` - Needs to contain a setting code name or SQL query without wildcards.
-- `"timeoutMultiplier" : true` - used to indicate if the value should multiply the max timeout for the whole script run by the number of values in the given parameter.
-- `"base64": true` - use base64 encoding to pass the value to the script (e.g. if there are spaces)
+See [UI Components: Filters](PLUGINS_DEV_UI_COMPONENTS.md#filters) for full documentation.
 
 
-> 🔎Example:
->
-> ```json
-> {
->     "params" : [{
->            "name"              : "ips",
->            "type"              : "sql",
->            "value"             : "SELECT devLastIP from DEVICES",
->            "timeoutMultiplier" : true
->        },
->        {
->            "name"              : "macs",
->            "type"              : "sql",
->            "value"             : "SELECT devMac from DEVICES"
->        },
->        {
->            "name"              : "timeout",
->            "type"              : "setting",
->            "value"             : "NMAP_RUN_TIMEOUT"
->        },
->        {
->            "name"              : "args",
->            "type"              : "setting",
->            "value"             : "NMAP_ARGS",
->            "base64"            : true
->        }]
-> }
-> ```
+---
 
+## Database Mapping
 
-#### ⚙ Setting object structure
-
-> [!NOTE]
-> The settings flow and when Plugin specific settings are applied is described under the [Settings system](./SETTINGS_SYSTEM.md).
-
-Required attributes are:
-
-| Property | Description |
-| -------- | ----------- |
-| `"function"` | Specifies the function the setting drives or a simple unique code name. See Supported settings function values for options. |
-| `"type"` | Specifies the form control used for the setting displayed in the Settings page and what values are accepted. Supported options include: |
-|  | - `{"dataType":"string", "elements": [{"elementType" : "input", "elementOptions" : [{"type":"password"}] ,"transformers": ["sha256"]}]}` |
-| `"localized"` | A list of properties on the current JSON level that need to be localized. |
-| `"name"` | Displayed on the Settings page. An array of localized strings. See Localized strings below. |
-| `"description"` | Displayed on the Settings page. An array of localized strings. See Localized strings below. |
-| (optional) `"events"` | Specifies whether to generate an execution button next to the input field of the setting. Supported values: |
-|  | - `"test"` - For notification plugins testing |
-|  | - `"run"` - Regular plugins testing |
-| (optional) `"override_value"` | Used to determine a user-defined override for the setting. Useful for template-based plugins, where you can choose to leave the current value or override it with the value defined in the setting. (Work in progress) |
-| (optional) `"events"` | Used to trigger the plugin. Usually used on the `RUN` setting. Not fully tested in all scenarios. Will show a play button next to the setting. After clicking, an event is generated for the backend in the `Parameters` database table to process the front-end event on the next run. |
-
-### UI Component Types Documentation
-
-This section outlines the structure and types of UI components, primarily used to build HTML forms or interactive elements dynamically. Each UI component has a `"type"` which defines its structure, behavior, and rendering options.
-
-#### UI Component JSON Structure
-The UI component is defined as a JSON object containing a list of `elements`. Each element specifies how it should behave, with properties like `elementType`, `elementOptions`, and any associated `transformers` to modify the data. The example below demonstrates how a component with two elements (`span` and `select`) is structured:
+To import plugin data into NetAlertX tables for device discovery or notifications:
 
 ```json
 {
-      "function": "devIcon",
-      "type": {
-        "dataType": "string",
-        "elements": [
-          {
-            "elementType": "span",
-            "elementOptions": [
-              { "cssClasses": "input-group-addon iconPreview" },
-              { "getStringKey": "Gen_SelectToPreview" },
-              { "customId": "NEWDEV_devIcon_preview" }
-            ],
-            "transformers": []
-          },
-          {
-            "elementType": "select",
-            "elementHasInputValue": 1,
-            "elementOptions": [
-              { "cssClasses": "col-xs-12" },
-              {
-                "onChange": "updateIconPreview(this)"
-              },
-              { "customParams": "NEWDEV_devIcon,NEWDEV_devIcon_preview" }
-            ],
-            "transformers": []
-          }
-        ]
-      }
+  "mapped_to_table": "CurrentScan",
+  "database_column_definitions": [
+    {
+      "column": "Object_PrimaryID",
+      "mapped_to_column": "cur_MAC",
+      "show": true,
+      "type": "device_mac",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "MAC Address"}]
+    }
+  ]
 }
-
 ```
 
-### Rendering Logic
+See [UI Components: Database Mapping](PLUGINS_DEV_UI_COMPONENTS.md#mapping-to-database-tables) for full documentation.
 
-The code snippet provided demonstrates how the elements are iterated over to generate their corresponding HTML. Depending on the `elementType`, different HTML tags (like `<select>`, `<input>`, `<textarea>`, `<button>`, etc.) are created with the respective attributes such as `onChange`, `my-data-type`, and `class` based on the provided `elementOptions`. Events can also be attached to elements like buttons or select inputs.
-
-### Key Element Types
-
-- **`select`**: Renders a dropdown list. Additional options like `isMultiSelect` and event handlers (e.g., `onChange`) can be attached.
-- **`input`**: Handles various types of input fields, including checkboxes, text, and others, with customizable attributes like `readOnly`, `placeholder`, etc.
-- **`button`**: Generates clickable buttons with custom event handlers (`onClick`), icons, or labels.
-- **`textarea`**: Creates a multi-line input box for text input.
-- **`span`**: Used for inline text or content with customizable classes and data attributes.
-
-Each element may also have associated events (e.g., running a scan or triggering a notification) defined under `Events`.
-
-
-##### Supported settings `function` values
-
-You can have any `"function": "my_custom_name"` custom name, however, the ones listed below have a specific functionality attached to them.
-
-| Setting | Description |
-| ------- | ----------- |
-| `RUN` | (required) Specifies when the service is executed. |
-|  | Supported Options: |
-|  | - "disabled" - do not run |
-|  | - "once" - run on app start or on settings saved |
-|  | - "schedule" - if included, then a `RUN_SCHD` setting needs to be specified to determine the schedule |
-|  | - "always_after_scan" - run always after a scan is finished |
-|  | - "before_name_updates" - run before device names are updated (for name discovery plugins) |
-|  | - "on_new_device" - run when a new device is detected |
-|  | - "before_config_save" - run before the config is marked as saved. Useful if your plugin needs to modify the `app.conf` file. |
-| `RUN_SCHD` | (required if you include "schedule" in the above `RUN` function) Cron-like scheduling is used if the `RUN` setting is set to `schedule`. |
-| `CMD` | (required) Specifies the command that should be executed. |
-| `API_SQL` | (not implemented) Generates a `table_` + `code_name` + `.json` file as per [API docs](./API.md). |
-| `RUN_TIMEOUT` | (optional) Specifies the maximum execution time of the script. If not specified, a default value of 10 seconds is used to prevent hanging. |
-| `WATCH` | (optional) Specifies which database columns are watched for changes for this particular plugin. If not specified, no notifications are sent. |
-| `REPORT_ON` | (optional) Specifies when to send a notification. Supported options are: |
-|  | - `new` means a new unique (unique combination of PrimaryId and SecondaryId) object was discovered. |
-|  | - `watched-changed` - means that selected `Watched_ValueN` columns changed |
-|  | - `watched-not-changed` - reports even on events where selected `Watched_ValueN` did not change |
-|  | - `missing-in-last-scan` - if the object is missing compared to previous scans |
-
-
-> 🔎 Example:
->
-> ```json
-> {
->     "function": "RUN",
->     "type": {"dataType":"string", "elements": [{"elementType" : "select", "elementOptions" : [] ,"transformers": []}]},
->     "default_value":"disabled",
->     "options": ["disabled", "once", "schedule", "always_after_scan", "on_new_device"],
->     "localized": ["name", "description"],
->     "name" :[{
->         "language_code":"en_us",
->         "string" : "When to run"
->     }],
->     "description": [{
->         "language_code":"en_us",
->         "string" : "Enable a regular scan of your services. If you select <code>schedule</code> the scheduling settings from below are applied. If you select <code>once</code> the scan is run only once on start of the application (container) for the time specified in <a href=\"#WEBMON_RUN_TIMEOUT\"><code>WEBMON_RUN_TIMEOUT</code> setting</a>."
->     }]
-> }
-> ```
-
-##### 🌍Localized strings
-
-- `"language_code":"<en_us|es_es|de_de>"`  - code name of the language string. Only these three are currently supported. At least the `"language_code":"en_us"` variant has to be defined.
-- `"string"`  - The string to be displayed in the given language.
-
-> 🔎 Example:
->
-> ```json
->
->     {
->         "language_code":"en_us",
->         "string" : "When to run"
->     }
->
-> ```
-
-##### UI settings in database_column_definitions
-
-The UI will adjust how columns are displayed in the UI based on the resolvers definition of the `database_column_definitions` object. These are the supported form controls and related functionality:
-
-- Only columns with `"show": true` and also with at least an English translation will be shown in the UI.
-
-| Supported Types | Description |
-| -------------- | ----------- |
-| `label` | Displays a column only. |
-| `textarea_readonly` | Generates a read only text area and cleans up the text to display it somewhat formatted with new lines preserved. |
-| See below for information on `threshold`, `replace`. | |
-|  |  |
-| `options` Property | Used in conjunction with types like `threshold`, `replace`, `regex`. |
-| `options_params` Property | Used in conjunction with a `"options": "[{value}]"` template and `text.select`/`list.select`. Can specify SQL query (needs to return 2 columns `SELECT devName as name, devMac as id`) or Setting (not tested) to populate the dropdown. Check example below or have a look at the `NEWDEV` plugin `config.json` file. |
-| `threshold` | The `options` array contains objects ordered from the lowest `maximum` to the highest. The corresponding `hexColor` is used for the value background color if it's less than the specified `maximum` but more than the previous one in the `options` array. |
-| `replace` | The `options` array contains objects with an `equals` property, which is compared to the "value." If the values are the same, the string in `replacement` is displayed in the UI instead of the actual "value". |
-| `regex` | Applies a regex to the value.  The `options` array contains objects with an `type` (must be set to `regex`) and `param` (must contain the regex itself) property. |
-|  |  |
-| Type Definitions |  |
-| `device_mac` | The value is considered to be a MAC address, and a link pointing to the device with the given MAC address is generated. |
-| `device_ip` | The value is considered to be an IP address. A link pointing to the device with the given IP is generated. The IP is checked against the last detected IP address and translated into a MAC address, which is then used for the link itself. |
-| `device_name_mac` | The value is considered to be a MAC address, and a link pointing to the device with the given MAC is generated. The link label is resolved as the target device name. |
-| `url` | The value is considered to be a URL, so a link is generated. |
-| `textbox_save` | Generates an editable and saveable text box that saves values in the database. Primarily intended for the `UserData` database column in the `Plugins_Objects` table. |
-| `url_http_https` | Generates two links with the `https` and `http` prefix as lock icons. |
-| `eval` | Evaluates as JavaScript. Use the variable `value` to use the given column value as input (e.g. `'<b>${value}<b>'` (replace ' with ` in your code) ) |
-
-
-> [!NOTE]
-> Supports chaining. You can chain multiple resolvers with `.`. For example `regex.url_http_https`. This will apply the `regex` resolver and then the `url_http_https` resolver.
-
-
-```json
-        "function": "devType",
-        "type": {"dataType":"string", "elements": [{"elementType" : "select", "elementOptions" : [] ,"transformers": []}]},
-        "maxLength": 30,
-        "default_value": "",
-        "options": ["{value}"],
-        "options_params" : [
-            {
-                "name"  : "value",
-                "type"  : "sql",
-                "value" : "SELECT '' as id, '' as name UNION SELECT devType as id, devType as name FROM (SELECT devType FROM Devices UNION SELECT 'Smartphone' UNION SELECT 'Tablet' UNION SELECT 'Laptop' UNION SELECT 'PC' UNION SELECT 'Printer' UNION SELECT 'Server' UNION SELECT 'NAS' UNION SELECT 'Domotic' UNION SELECT 'Game Console' UNION SELECT 'SmartTV' UNION SELECT 'Clock' UNION SELECT 'House Appliance' UNION SELECT 'Phone' UNION SELECT 'AP' UNION SELECT 'Gateway' UNION SELECT 'Firewall' UNION SELECT 'Switch' UNION SELECT 'WLAN' UNION SELECT 'Router' UNION SELECT 'Other') AS all_devices ORDER BY id;"
-            },
-            {
-                "name"  : "uilang",
-                "type"  : "setting",
-                "value" : "UI_LANG"
-            }
-        ]
-```
+### Static Value Mapping
 
+To always map a static value (not read from plugin output):
 
 ```json
 {
-            "column": "Watched_Value1",
-            "css_classes": "col-sm-2",
-            "show": true,
-            "type": "threshold",
-            "default_value":"",
-            "options": [
-                {
-                    "maximum": 199,
-                    "hexColor": "#792D86"
-                },
-                {
-                    "maximum": 299,
-                    "hexColor": "#5B862D"
-                },
-                {
-                    "maximum": 399,
-                    "hexColor": "#7D862D"
-                },
-                {
-                    "maximum": 499,
-                    "hexColor": "#BF6440"
-                },
-                {
-                    "maximum": 599,
-                    "hexColor": "#D33115"
-                }
-            ],
-            "localized": ["name"],
-            "name":[{
-                "language_code":"en_us",
-                "string" : "Status code"
-                }]
-        },
-        {
-            "column": "Status",
-            "show": true,
-            "type": "replace",
-            "default_value":"",
-            "options": [
-                {
-                    "equals": "watched-not-changed",
-                    "replacement": "<i class='fa-solid fa-square-check'></i>"
-                },
-                {
-                    "equals": "watched-changed",
-                    "replacement": "<i class='fa-solid fa-triangle-exclamation'></i>"
-                },
-                {
-                    "equals": "new",
-                    "replacement": "<i class='fa-solid fa-circle-plus'></i>"
-                }
-            ],
-            "localized": ["name"],
-            "name":[{
-                "language_code":"en_us",
-                "string" : "Status"
-                }]
-        },
-        {
-            "column": "Watched_Value3",
-            "css_classes": "col-sm-1",
-            "show": true,
-            "type": "regex.url_http_https",
-            "default_value":"",
-            "options": [
-                {
-                    "type": "regex",
-                    "param": "([\\d.:]+)"
-                }
-            ],
-            "localized": ["name"],
-            "name":[{
-                "language_code":"en_us",
-                "string" : "HTTP/s links"
-                },
-	    	    {
-                "language_code":"es_es",
-                "string" : "N/A"
-                }]
-        }
+  "column": "NameDoesntMatter",
+  "mapped_to_column": "cur_ScanMethod",
+  "mapped_to_column_data": {
+    "value": "MYPLN"
+  }
+}
 ```
 
+---
+
+## UI Component Types
+
+Plugin results are displayed in the web interface using various component types. See **[PLUGINS_DEV_UI_COMPONENTS.md](PLUGINS_DEV_UI_COMPONENTS.md)** for complete documentation.
+
+### Common Display Types
+
+**Read settings in your Python script:**
+
+```python
+from helper import get_setting_value
+
+# Read a setting by code name (prefix + function)
+api_url = get_setting_value('MYPLN_API_URL')
+api_key = get_setting_value('MYPLN_API_KEY')
+watch_columns = get_setting_value('MYPLN_WATCH')
+
+print(f"Connecting to {api_url}")
+```
+
+**Pass settings as command parameters:**
+
+Define `params` in config to pass settings as script arguments:
+
+```json
+{
+  "params": [
+    {
+      "name": "api_url",
+      "type": "setting",
+      "value": "MYPLN_API_URL"
+    }
+  ]
+}
+```
+
+Then use in `CMD`: `python3 script.py --url={api_url}`
+
+See [PLUGINS_DEV_SETTINGS.md](PLUGINS_DEV_SETTINGS.md) for complete settings documentation, and [PLUGINS_DEV_DATASOURCES.md](PLUGINS_DEV_DATASOURCES.md) for data source details.
+
 [screen1]: https://raw.githubusercontent.com/jokob-sk/NetAlertX/main/docs/img/plugins.png                    "Screen 1"
 [screen2]: https://raw.githubusercontent.com/jokob-sk/NetAlertX/main/docs/img/plugins_settings.png           "Screen 2"
 [screen3]: https://raw.githubusercontent.com/jokob-sk/NetAlertX/main/docs/img/plugins_json_settings.png      "Screen 3"
diff --git a/docs/PLUGINS_DEV_DATASOURCES.md b/docs/PLUGINS_DEV_DATASOURCES.md
new file mode 100644
index 00000000..a1fa853c
--- /dev/null
+++ b/docs/PLUGINS_DEV_DATASOURCES.md
@@ -0,0 +1,403 @@
+# Plugin Data Sources
+
+Learn how to configure different data sources for your plugin.
+
+## Overview
+
+Data sources determine **where the plugin gets its data** and **what format it returns**. NetAlertX supports multiple data source types, each suited for different use cases.
+
+| Data Source | Type | Purpose | Returns | Example |
+|-------------|------|---------|---------|---------|
+| `script` | Code Execution | Execute Linux commands or Python scripts | Pipeline | Scan network, collect metrics, call APIs |
+| `app-db-query` | Database Query | Query the NetAlertX database | Result set | Show devices, open ports, recent events |
+| `sqlite-db-query` | External DB | Query external SQLite databases | Result set | PiHole database, external logs |
+| `template` | Template | Generate values from templates | Values | Initialize default settings |
+| `plugin_type` | Metadata | Declare plugin category | Metadata | Classify plugin (scanner, publisher, etc.) |
+
+## Data Source: `script`
+
+Execute any Linux command or Python script and capture its output.
+
+### Configuration
+
+```json
+{
+  "data_source": "script",
+  "show_ui": true,
+  "mapped_to_table": "Plugins_Objects"
+}
+```
+
+### How It Works
+
+1. Command specified in `CMD` setting is executed
+2. Script writes results to `/tmp/log/plugins/last_result.<PREFIX>.log`
+3. Core reads file and parses pipe-delimited results
+4. Results inserted into database
+
+### Example: Simple Python Script
+
+```json
+{
+  "function": "CMD",
+  "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+  "default_value": "python3 /app/front/plugins/my_plugin/script.py",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Command"}]
+}
+```
+
+### Example: Bash Script
+
+```json
+{
+  "function": "CMD",
+  "default_value": "bash /app/front/plugins/my_plugin/script.sh",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Command"}]
+}
+```
+
+### Best Practices
+
+- **Always use absolute paths** (e.g., `/app/front/plugins/...`)
+- **Use `plugin_helper.py`** for output formatting
+- **Add timeouts** via `RUN_TIMEOUT` setting (default: 60s)
+- **Log errors** to `/tmp/log/plugins/*.log`
+- **Handle missing dependencies gracefully**
+
+### Output Format
+
+Must write to: `/tmp/log/plugins/last_result.<PREFIX>.log`
+
+Format: Pipe-delimited, 9 or 13 columns
+
+See [Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md) for exact format
+
+---
+
+## Data Source: `app-db-query`
+
+Query the NetAlertX SQLite database and display results.
+
+### Configuration
+
+```json
+{
+  "data_source": "app-db-query",
+  "show_ui": true,
+  "mapped_to_table": "Plugins_Objects"
+}
+```
+
+### How It Works
+
+1. SQL query specified in `CMD` setting is executed against `app.db`
+2. Results parsed according to column definitions
+3. Inserted into plugin display/database
+
+### SQL Query Requirements
+
+- Must return exactly **9 or 13 columns** matching the [data contract](PLUGINS_DEV_DATA_CONTRACT.md)
+- Column names must match (order matters!)
+- Must be **readable SQLite SQL** (not vendor-specific)
+
+### Example: Open Ports from Nmap
+
+```json
+{
+  "function": "CMD",
+  "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+  "default_value": "SELECT dv.devName as Object_PrimaryID, cast(dv.devLastIP as VARCHAR(100)) || ':' || cast(SUBSTR(ns.Port, 0, INSTR(ns.Port, '/')) as VARCHAR(100)) as Object_SecondaryID, datetime() as DateTime, ns.Service as Watched_Value1, ns.State as Watched_Value2, null as Watched_Value3, null as Watched_Value4, ns.Extra as Extra, dv.devMac as ForeignKey FROM (SELECT * FROM Nmap_Scan) ns LEFT JOIN (SELECT devName, devMac, devLastIP FROM Devices) dv ON ns.MAC = dv.devMac",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "SQL to run"}],
+  "description": [{"language_code": "en_us", "string": "This SQL query populates the plugin table"}]
+}
+```
+
+### Example: Recent Device Events
+
+```sql
+SELECT
+  e.EventValue as Object_PrimaryID,
+  d.devName as Object_SecondaryID,
+  e.EventDateTime as DateTime,
+  e.EventType as Watched_Value1,
+  d.devLastIP as Watched_Value2,
+  null as Watched_Value3,
+  null as Watched_Value4,
+  e.EventDetails as Extra,
+  d.devMac as ForeignKey
+FROM
+  Events e
+LEFT JOIN
+  Devices d ON e.DeviceMac = d.devMac
+WHERE
+  e.EventDateTime > datetime('now', '-24 hours')
+ORDER BY
+  e.EventDateTime DESC
+```
+
+### Common Columns
+
+**Devices Table:**
+- `devMac` - Device MAC address
+- `devName` - Device name
+- `devLastIP` - Last known IP
+- `devType` - Device type
+- `devStatus` - Online/offline status
+- `devVendor` - Hardware vendor
+
+**CurrentScan Table:**
+- `cur_MAC` - MAC address
+- `cur_IP` - IP address
+- `cur_ScanMethod` - How it was discovered
+
+**Nmap_Scan Table:**
+- `MAC` - Device MAC
+- `Port` - Port number
+- `Service` - Service name
+- `State` - open/closed/filtered
+- `Extra` - Additional notes
+
+**Events Table:**
+- `EventType` - Event type
+- `EventValue` - Event value
+- `EventDateTime` - When it occurred
+- `DeviceMac` - Associated device
+
+---
+
+## Data Source: `sqlite-db-query`
+
+Query an **external SQLite database** mounted in the container.
+
+### Configuration
+
+First, define the database path in a setting:
+
+```json
+{
+  "function": "DB_PATH",
+  "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+  "default_value": "/etc/pihole/pihole-FTL.db",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Database path"}],
+  "description": [{"language_code": "en_us", "string": "Path to external SQLite database"}]
+}
+```
+
+Then set data source and query:
+
+```json
+{
+  "data_source": "sqlite-db-query",
+  "show_ui": true
+}
+```
+
+### How It Works
+
+1. External database file path specified in `DB_PATH` setting
+2. Database mounted at that path (e.g., via Docker volume)
+3. SQL query executed against external database using `EXTERNAL_<PREFIX>.` prefix
+4. Results returned in standard format
+
+### SQL Query Example: PiHole Data
+
+```json
+{
+  "function": "CMD",
+  "default_value": "SELECT hwaddr as Object_PrimaryID, cast('http://' || (SELECT ip FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC LIMIT 1) as VARCHAR(100)) || ':' || cast(SUBSTR((SELECT name FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC LIMIT 1), 0, INSTR((SELECT name FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC LIMIT 1), '/')) as VARCHAR(100)) as Object_SecondaryID, datetime() as DateTime, macVendor as Watched_Value1, lastQuery as Watched_Value2, (SELECT name FROM EXTERNAL_PIHOLE.network_addresses WHERE network_id = id ORDER BY lastseen DESC LIMIT 1) as Watched_Value3, null as Watched_Value4, '' as Extra, hwaddr as ForeignKey FROM EXTERNAL_PIHOLE.network WHERE hwaddr NOT LIKE 'ip-%' AND hwaddr <> '00:00:00:00:00:00'",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "SQL to run"}]
+}
+```
+
+### Key Points
+
+- **Prefix all external tables** with `EXTERNAL_<PREFIX>.`
+  - For PiHole (`PIHOLE` prefix): `EXTERNAL_PIHOLE.network`
+  - For custom database (`CUSTOM` prefix): `EXTERNAL_CUSTOM.my_table`
+- **Database must be valid SQLite**
+- **Path must be accessible** inside the container
+- **No columns beyond the data contract** required
+
+### Docker Volume Setup
+
+To mount external database in docker-compose:
+
+```yaml
+services:
+  netalertx:
+    volumes:
+      - /path/on/host/pihole-FTL.db:/etc/pihole/pihole-FTL.db:ro
+```
+
+---
+
+## Data Source: `template`
+
+Generate values from a template. Usually used for initialization and default settings.
+
+### Configuration
+
+```json
+{
+  "data_source": "template"
+}
+```
+
+### How It Works
+
+- **Not widely used** in standard plugins
+- Used internally for generating default values
+- Check `newdev_template` plugin for implementation example
+
+### Example: Default Device Template
+
+```json
+{
+  "function": "DEFAULT_DEVICE_PROPERTIES",
+  "type": {"dataType": "string", "elements": [{"elementType": "textarea", "elementOptions": [], "transformers": []}]},
+  "default_value": "type=Unknown|vendor=Unknown",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Default properties"}]
+}
+```
+
+---
+
+## Data Source: `plugin_type`
+
+Declare the plugin category. Controls where settings appear in the UI.
+
+### Configuration
+
+```json
+{
+  "data_source": "plugin_type",
+  "value": "scanner"
+}
+```
+
+### Supported Values
+
+| Value | Section | Purpose |
+|-------|---------|---------|
+| `scanner` | Device Scanners | Discovers devices on network |
+| `system` | System Plugins | Core system functionality |
+| `publisher` | Notification/Alert Plugins | Sends notifications/alerts |
+| `importer` | Data Importers | Imports devices from external sources |
+| `other` | Other Plugins | Miscellaneous functionality |
+
+### Example
+
+```json
+{
+  "settings": [
+    {
+      "function": "plugin_type",
+      "type": {"dataType": "string", "elements": []},
+      "default_value": "scanner",
+      "options": ["scanner"],
+      "data_source": "plugin_type",
+      "value": "scanner",
+      "localized": []
+    }
+  ]
+}
+```
+
+---
+
+## Execution Order
+
+Control plugin execution priority. Higher priority plugins run first.
+
+```json
+{
+  "execution_order": "Layer_0"
+}
+```
+
+### Levels (highest to lowest priority)
+
+- `Layer_0` - Highest priority (run first)
+- `Layer_1`
+- `Layer_2`
+- ...
+
+### Example: Multi-Source Device Discovery
+
+```json
+{
+  "code_name": "device_scanner",
+  "unique_prefix": "DEVSCAN",
+  "execution_order": "Layer_0",
+  "data_source": "script",
+  "mapped_to_table": "CurrentScan"
+}
+```
+---
+
+## Performance Considerations
+
+### Script Source
+- **Pros:** Flexible, can call external tools
+- **Cons:** Slower than database queries
+- **Optimization:** Add caching, use timeouts
+- **Default timeout:** 60 seconds (set `RUN_TIMEOUT`)
+
+### Database Query Source
+- **Pros:** Fast, native query optimization
+- **Cons:** Limited to SQL capabilities
+- **Optimization:** Use indexes, avoid complex joins
+- **Timeout:** Usually instant
+
+### External DB Query Source
+- **Pros:** Direct access to external data
+- **Cons:** Network latency, external availability
+- **Optimization:** Use indexes in external DB, selective queries
+- **Timeout:** Depends on DB response time
+
+---
+
+## Debugging Data Sources
+
+### Check Script Output
+
+```bash
+# Run script manually
+python3 /app/front/plugins/my_plugin/script.py
+
+# Check result file
+cat /tmp/log/plugins/last_result.MYPREFIX.log
+```
+
+### Test SQL Query
+
+```bash
+# Connect to app database
+sqlite3 /data/db/app.db
+
+# Run query
+sqlite> SELECT ... ;
+```
+
+### Monitor Execution
+
+```bash
+# Watch backend logs
+tail -f /tmp/log/stdout.log | grep -i "data_source\|MYPREFIX"
+```
+
+---
+
+## See Also
+
+- [Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md) - Output format specification
+- [Plugin Settings System](PLUGINS_DEV_SETTINGS.md) - How to define settings
+- [Quick Start Guide](PLUGINS_DEV_QUICK_START.md) - Create your first plugin
+- [Database Schema](DATABASE.md) - Available tables and columns
+- [Debugging Plugins](DEBUG_PLUGINS.md) - Troubleshooting data issues
diff --git a/docs/PLUGINS_DEV_DATA_CONTRACT.md b/docs/PLUGINS_DEV_DATA_CONTRACT.md
new file mode 100644
index 00000000..c843290f
--- /dev/null
+++ b/docs/PLUGINS_DEV_DATA_CONTRACT.md
@@ -0,0 +1,249 @@
+# Plugin Data Contract
+
+This document specifies the exact interface between plugins and the NetAlertX core.
+
+> [!IMPORTANT]
+> Every plugin must output data in this exact format to be recognized and processed correctly.
+
+## Overview
+
+Plugins communicate with NetAlertX by writing results to a **pipe-delimited log file**. The core reads this file, parses the data, and processes it for notifications, device discovery, and data integration.
+
+**File Location:** `/tmp/log/plugins/last_result.<PREFIX>.log`
+
+**Format:** Pipe-delimited (`|`), one record per line
+
+**Required Columns:** 9 (mandatory) + up to 4 optional helper columns = 13 total
+
+## Column Specification
+
+> [!NOTE]
+> The order of columns is **FIXED** and cannot be changed. All 9 mandatory columns must be provided. If you use any optional column (`HelpVal1`), you must supply all optional columns (`HelpVal1` through `HelpVal4`).
+
+### Mandatory Columns (0–8)
+
+| Order | Column Name | Type | Required | Description |
+|-------|-------------|------|----------|-------------|
+| 0 | `Object_PrimaryID` | string | **YES** | The primary identifier for grouping. Examples: device MAC, hostname, service name, or any unique ID |
+| 1 | `Object_SecondaryID` | string | no | Secondary identifier for relationships (e.g., IP address, port, sub-ID). Use `null` if not needed |
+| 2 | `DateTime` | string | **YES** | Timestamp when the event/data was collected. Format: `YYYY-MM-DD HH:MM:SS` |
+| 3 | `Watched_Value1` | string | **YES** | Primary watched value. Changes trigger notifications. Examples: IP address, status, version |
+| 4 | `Watched_Value2` | string | no | Secondary watched value. Use `null` if not needed |
+| 5 | `Watched_Value3` | string | no | Tertiary watched value. Use `null` if not needed |
+| 6 | `Watched_Value4` | string | no | Quaternary watched value. Use `null` if not needed |
+| 7 | `Extra` | string | no | Any additional metadata to display in UI and notifications. Use `null` if not needed |
+| 8 | `ForeignKey` | string | no | Foreign key linking to parent object (usually MAC address for device relationship). Use `null` if not needed |
+
+### Optional Columns (9–12)
+
+| Order | Column Name | Type | Required | Description |
+|-------|-------------|------|----------|-------------|
+| 9 | `HelpVal1` | string | *conditional* | Helper value 1. If used, all help values must be supplied |
+| 10 | `HelpVal2` | string | *conditional* | Helper value 2. If used, all help values must be supplied |
+| 11 | `HelpVal3` | string | *conditional* | Helper value 3. If used, all help values must be supplied |
+| 12 | `HelpVal4` | string | *conditional* | Helper value 4. If used, all help values must be supplied |
+
+## Usage Guide
+
+### Empty/Null Values
+
+- Represent empty values as the literal string `null` (not Python `None`, SQL `NULL`, or empty string)
+- Example: `device_id|null|2023-01-02 15:56:30|status|null|null|null|null|null`
+
+### Watched Values
+
+**What are Watched Values?**
+
+Watched values are fields that the NetAlertX core monitors for **changes between scans**. When a watched value differs from the previous scan, it can trigger notifications.
+
+**How to use them:**
+- `Watched_Value1`: Always required; primary indicator of status/state
+- `Watched_Value2–4`: Optional; use for secondary/tertiary state information
+- Leave unused ones as `null`
+
+**Example:**
+- Device scanner: `Watched_Value1 = "online"` or `"offline"`
+- Port scanner: `Watched_Value1 = "80"` (port number), `Watched_Value2 = "open"` (state)
+- Service monitor: `Watched_Value1 = "200"` (HTTP status), `Watched_Value2 = "0.45"` (response time)
+
+### Foreign Key
+
+Use the `ForeignKey` column to link objects to a parent device by MAC address:
+
+```
+device_name|192.168.1.100|2023-01-02 15:56:30|online|null|null|null|Found on network|aa:bb:cc:dd:ee:ff
+                                                                                              ↑
+                                                                                        ForeignKey (MAC)
+```
+
+This allows NetAlertX to:
+- Display the object on the device details page
+- Send notifications when the parent device is involved
+- Link events across plugins
+
+## Examples
+
+### Valid Data (9 columns, minimal)
+
+```csv
+https://example.com|null|2023-01-02 15:56:30|200|null|null|null|null|null
+printer-hp-1|192.168.1.50|2023-01-02 15:56:30|online|50%|null|null|Last seen in office|aa:11:22:33:44:55
+gateway.local|null|2023-01-02 15:56:30|active|v2.1.5|null|null|Firmware version|null
+```
+
+### Valid Data (13 columns, with helpers)
+
+```csv
+service-api|192.168.1.100:8080|2023-01-02 15:56:30|200|45ms|true|null|Responding normally|aa:bb:cc:dd:ee:ff|extra1|extra2|extra3|extra4
+host-web-1|10.0.0.20|2023-01-02 15:56:30|active|256GB|online|ok|Production server|null|cpu:80|mem:92|disk:45|alerts:0
+```
+
+### Invalid Data (Common Errors)
+
+❌ **Missing required column** (only 8 separators instead of 8):
+```csv
+https://google.com|null|2023-01-02 15:56:30|200|0.7898||null|null
+                                                      ↑
+                                                  Missing pipe
+```
+
+❌ **Missing mandatory Watched_Value1** (column 3):
+```csv
+https://duckduckgo.com|192.168.1.1|2023-01-02 15:56:30|null|0.9898|null|null|Best|null
+                                                         ↑
+                                          Must not be null
+```
+
+❌ **Incomplete optional columns** (has HelpVal1 but missing HelpVal2–4):
+```csv
+device|null|2023-01-02 15:56:30|status|null|null|null|null|null|helper1
+                                                                    ↑
+                                                    Has helper but incomplete
+```
+
+✅ **Complete with helpers** (all 4 helpers provided):
+```csv
+device|null|2023-01-02 15:56:30|status|null|null|null|null|null|h1|h2|h3|h4
+```
+
+✅ **Complete without helpers** (9 columns exactly):
+```csv
+device|null|2023-01-02 15:56:30|status|null|null|null|null|null
+```
+
+## Using `plugin_helper.py`
+
+The easiest way to ensure correct output is to use the [`plugin_helper.py`](../front/plugins/plugin_helper.py) library:
+
+```python
+from plugin_helper import Plugin_Objects
+
+# Initialize with your plugin's prefix
+plugin_objects = Plugin_Objects("YOURPREFIX")
+
+# Add objects
+plugin_objects.add_object(
+    Object_PrimaryID="device_id",
+    Object_SecondaryID="192.168.1.1",
+    DateTime="2023-01-02 15:56:30",
+    Watched_Value1="online",
+    Watched_Value2=None,
+    Watched_Value3=None,
+    Watched_Value4=None,
+    Extra="Additional data",
+    ForeignKey="aa:bb:cc:dd:ee:ff",
+    HelpVal1=None,
+    HelpVal2=None,
+    HelpVal3=None,
+    HelpVal4=None
+)
+
+# Write results (handles formatting, sanitization, and file creation)
+plugin_objects.write_result_file()
+```
+
+The library automatically:
+- Validates data types
+- Sanitizes string values
+- Normalizes MAC addresses
+- Writes to the correct file location
+- Creates the file in `/tmp/log/plugins/last_result.<PREFIX>.log`
+
+## De-duplication
+
+The core runs **de-duplication once per hour** on the `Plugins_Objects` table:
+
+- **Duplicate Detection Key:** Combination of `Object_PrimaryID`, `Object_SecondaryID`, `Plugin` (auto-filled from `unique_prefix`), and `UserData`
+- **Resolution:** Oldest duplicate entries are removed, newest are kept
+- **Use Case:** Prevents duplicate notifications when the same object is detected multiple times
+
+## DateTime Format
+
+**Required Format:** `YYYY-MM-DD HH:MM:SS`
+
+**Examples:**
+- `2023-01-02 15:56:30` ✅
+- `2023-1-2 15:56:30` ❌ (missing leading zeros)
+- `2023-01-02T15:56:30` ❌ (wrong separator)
+- `15:56:30 2023-01-02` ❌ (wrong order)
+
+**Python Helper:**
+```python
+from datetime import datetime
+
+# Current time in correct format
+now = datetime.now().strftime("%Y-%m-%d %H:%M:%S")
+# Output: "2023-01-02 15:56:30"
+```
+
+**Bash Helper:**
+```bash
+# Current time in correct format
+date '+%Y-%m-%d %H:%M:%S'
+# Output: 2023-01-02 15:56:30
+```
+
+## Validation Checklist
+
+Before writing your plugin's `script.py`, ensure:
+
+- [ ] **9 or 13 columns** in each output line (8 or 12 pipe separators)
+- [ ] **Mandatory columns filled:**
+  - Column 0: `Object_PrimaryID` (not null)
+  - Column 2: `DateTime` in `YYYY-MM-DD HH:MM:SS` format
+  - Column 3: `Watched_Value1` (not null)
+- [ ] **Null values as literal string** `null` (not empty string or special chars)
+- [ ] **No extra pipes or misaligned columns**
+- [ ] **If using optional helpers** (columns 9–12), all 4 must be present
+- [ ] **File written to** `/tmp/log/plugins/last_result.<PREFIX>.log`
+- [ ] **One record per line** (newline-delimited)
+- [ ] **No header row** (data only)
+
+## Debugging
+
+**View raw plugin output:**
+```bash
+cat /tmp/log/plugins/last_result.YOURPREFIX.log
+```
+
+**Check line count:**
+```bash
+wc -l /tmp/log/plugins/last_result.YOURPREFIX.log
+```
+
+**Validate column count (should be 8 or 12 pipes per line):**
+```bash
+cat /tmp/log/plugins/last_result.YOURPREFIX.log | awk -F'|' '{print NF}' | sort | uniq
+# Output: 9 (for minimal) or 13 (for with helpers)
+```
+
+**Check core processing in logs:**
+```bash
+tail -f /tmp/log/stdout.log | grep -i "YOURPREFIX\|Plugins_Objects"
+```
+
+## See Also
+
+- [Plugin Settings System](PLUGINS_DEV_SETTINGS.md) - How to accept user input
+- [Data Sources](PLUGINS_DEV_DATASOURCES.md) - Different data source types
+- [Debugging Plugins](DEBUG_PLUGINS.md) - Troubleshooting plugin issues
diff --git a/docs/PLUGINS_DEV_INDEX.md b/docs/PLUGINS_DEV_INDEX.md
new file mode 100644
index 00000000..da4077b9
--- /dev/null
+++ b/docs/PLUGINS_DEV_INDEX.md
@@ -0,0 +1,225 @@
+# Plugin Development Documentation Index
+
+Complete guide to building NetAlertX plugins, split into focused, easy-to-navigate documents.
+
+## Quick Navigation
+
+**Just getting started?** → [Quick Start Guide](PLUGINS_DEV_QUICK_START.md)
+**Need the basics?** → [Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md)
+**Configuring plugins?** → [Plugin Settings System](PLUGINS_DEV_SETTINGS.md)
+**Displaying results?** → [UI Components](PLUGINS_DEV_UI_COMPONENTS.md)
+**Getting data?** → [Data Sources](PLUGINS_DEV_DATASOURCES.md)
+
+---
+
+## Documentation Structure
+
+### Getting Started (Start Here!)
+
+| Document | Purpose | Read Time |
+|----------|---------|-----------|
+| **[Quick Start Guide](PLUGINS_DEV_QUICK_START.md)** | Create a working plugin in 5 minutes. Copy template, edit config, implement script, test. | 5 min |
+| **[Development Environment Setup](./DEV_ENV_SETUP.md)** | Set up your local development environment for plugin development. | 10 min |
+
+### Core Concepts
+
+| Document | Purpose | Read Time |
+|----------|---------|-----------|
+| **[Full Plugin Development Guide](PLUGINS_DEV.md)** | Comprehensive overview with references to all specialized guides. Architecture, file structure, manifest format. | 20 min |
+| **[Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md)** | **THE** authoritative reference for plugin output format. 9-13 pipe-delimited columns. Examples, validation, debugging. | 15 min |
+| **[Plugin Settings System](PLUGINS_DEV_SETTINGS.md)** | How to add user-configurable settings. Component types, reserved names, accessing in scripts. | 20 min |
+| **[Data Sources](PLUGINS_DEV_DATASOURCES.md)** | How plugins retrieve data: scripts, database queries, external SQLite, templates. Performance considerations. | 15 min |
+| **[UI Components](PLUGINS_DEV_UI_COMPONENTS.md)** | How to display plugin results: labels, links, color-coded badges, filters. Database mapping. | 25 min |
+
+### Advanced Topics
+
+| Document | Purpose | Read Time |
+|----------|---------|-----------|
+| **[Config Lifecycle](PLUGINS_DEV_CONFIG.md)** | Deep dive into how `config.json` is loaded, validated, and used throughout plugin lifecycle. | 15 min |
+| **[Debugging Plugins](DEBUG_PLUGINS.md)** | Troubleshooting plugin issues: logs, validation, common errors. | 10 min |
+
+---
+
+## Document Overview
+
+### [Quick Start Guide](PLUGINS_DEV_QUICK_START.md)
+**For:** First-time plugin developers
+**Contains:**
+- 5 prerequisites
+- Step-by-step: folder setup, config.json, script.py, execution settings
+- Testing locally & via UI
+- Common issues table
+
+**Read this first if you want a working plugin in 5 minutes.**
+
+---
+
+### [Full Plugin Development Guide](PLUGINS_DEV.md)
+**For:** Reference and architecture understanding
+**Contains:**
+- Quick links to all specialized guides
+- Use cases and limitations
+- Plugin workflow (4 steps)
+- File structure overview
+- Manifest format
+- References to detailed guides
+
+**Read this for the big picture and to navigate to specific topics.**
+
+---
+
+### [Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md)
+**For:** Understanding plugin output format
+**Contains:**
+- 9 mandatory + 4 optional column specification
+- Column purpose and examples
+- Empty/null value handling
+- Watched values explanation
+- Foreign key usage
+- Valid & invalid data examples
+- Using `plugin_helper.py`
+- De-duplication rules
+- DateTime formatting
+- Validation checklist
+- Debugging commands
+
+**Read this to understand exactly what format your plugin must output.**
+
+---
+
+### [Plugin Settings System](PLUGINS_DEV_SETTINGS.md)
+**For:** Adding user-configurable options
+**Contains:**
+- Setting definition structure
+- Required & optional properties
+- 10 reserved function names (RUN, CMD, RUN_TIMEOUT, WATCH, etc.)
+- Component types: text, password, select, multi-select, checkbox, textarea, label
+- Reading settings in scripts (3 methods)
+- Localized strings
+- Complete examples (website monitor, PiHole)
+- Validation & testing
+
+**Read this to let users configure your plugin via the UI.**
+
+---
+
+### [Data Sources](PLUGINS_DEV_DATASOURCES.md)
+**For:** Choosing how your plugin gets data
+**Contains:**
+- 5 data source types: `script`, `app-db-query`, `sqlite-db-query`, `template`, `plugin_type`
+- Configuration for each type
+- How it works section for each
+- Script source best practices
+- SQL query examples for app database
+- External SQLite database setup
+- Execution order/priority
+- Performance considerations
+- Debugging data sources
+
+**Read this to decide where your plugin data comes from.**
+
+---
+
+### [UI Components](PLUGINS_DEV_UI_COMPONENTS.md)
+**For:** Displaying plugin results in the web interface
+**Contains:**
+- Column definition structure
+- Property reference (10+ properties)
+- 15+ render types:
+  - Display-only: label, device_mac, device_ip, device_name_mac, url, url_http_https, textarea_readonly
+  - Interactive: textbox_save
+  - Styled: threshold, replace, regex, eval
+- Chaining types (e.g., regex.url_http_https)
+- Dynamic options (SQL-driven, setting-driven)
+- Database mapping to CurrentScan
+- Static value mapping
+- Filters with 5+ examples
+- CSS classes reference
+- Complete examples
+
+**Read this to make your plugin results look great and work intuitively.**
+
+---
+
+### [Config Lifecycle](PLUGINS_DEV_CONFIG.md)
+**For:** Understanding how plugins integrate
+**Contains:**
+- Plugin data flow diagram
+- 6-step lifecycle: loading, validation, preparation, execution, parsing, mapping
+- How `config.json` is processed
+- Plugin output contract
+- Plugin categories & execution
+- Data sources in detail
+
+**Read this to understand the deep architecture.**
+
+---
+
+### [Debugging Plugins](DEBUG_PLUGINS.md)
+**For:** Troubleshooting when things don't work
+**Contains:**
+- Common errors & solutions
+- Log file locations
+- Commands to check status
+- Validation tools
+- Database queries for inspection
+- Permission issues
+- Performance troubleshooting
+
+**Read this when your plugin isn't working.**
+
+
+---
+
+## Quick Reference: Key Concepts
+
+### Plugin Output Format
+```
+Object_PrimaryID|Object_SecondaryID|DateTime|Watched_Value1|Watched_Value2|Watched_Value3|Watched_Value4|Extra|ForeignKey
+```
+9 required columns, 4 optional helpers = 13 max
+
+See: [Data Contract](PLUGINS_DEV_DATA_CONTRACT.md)
+
+### Plugin Metadata (config.json)
+```json
+{
+  "code_name": "my_plugin",           // Folder name
+  "unique_prefix": "MYPLN",           // Settings prefix
+  "display_name": [...],              // UI label
+  "data_source": "script",            // Where data comes from
+  "settings": [...],                  // User configurable
+  "database_column_definitions": [...] // How to display
+}
+```
+
+See: [Full Guide](PLUGINS_DEV.md), [Settings](PLUGINS_DEV_SETTINGS.md)
+
+### Reserved Settings
+- `RUN` - When to execute (disabled, once, schedule, always_after_scan, etc.)
+- `RUN_SCHD` - Cron schedule
+- `CMD` - Command/script to execute
+- `RUN_TIMEOUT` - Max execution time
+- `WATCH` - Monitor for changes
+- `REPORT_ON` - Notification trigger
+
+See: [Settings System](PLUGINS_DEV_SETTINGS.md)
+
+### Display Types
+`label`, `device_mac`, `device_ip`, `url`, `threshold`, `replace`, `regex`, `textbox_save`, and more.
+
+See: [UI Components](PLUGINS_DEV_UI_COMPONENTS.md)
+
+---
+
+## Tools & References
+
+- **Template Plugin:** `/app/front/plugins/__template/` - Start here!
+- **Helper Library:** `/app/front/plugins/plugin_helper.py` - Use for output formatting
+- **Settings Helper:** `/app/server/helper.py` - Use `get_setting_value()` in scripts
+- **Example Plugins:** `/app/front/plugins/*/` - Study working implementations
+- **Logs:** `/tmp/log/plugins/` - Plugin output and execution logs
+- **Backend Logs:** `/tmp/log/stdout.log` - Core system logs
+
+---
+
diff --git a/docs/PLUGINS_DEV_QUICK_START.md b/docs/PLUGINS_DEV_QUICK_START.md
new file mode 100644
index 00000000..933b6886
--- /dev/null
+++ b/docs/PLUGINS_DEV_QUICK_START.md
@@ -0,0 +1,175 @@
+# Plugin Development Quick Start
+
+Get a working plugin up and running in 5 minutes.
+
+## Prerequisites
+
+- Read [Development Environment Setup Guide](./DEV_ENV_SETUP.md) to set up your local environment
+- Understand [Plugin Architecture Overview](PLUGINS_DEV.md)
+
+## Quick Start Steps
+
+### 1. Create Your Plugin Folder
+
+Start from the template to get the basic structure:
+
+```bash
+cd /workspaces/NetAlertX/front/plugins
+cp -r __template my_plugin
+cd my_plugin
+```
+
+### 2. Update `config.json` Identifiers
+
+Edit `my_plugin/config.json` and update these critical fields:
+
+```json
+{
+  "code_name": "my_plugin",
+  "unique_prefix": "MYPLN",
+  "display_name": [{"language_code": "en_us", "string": "My Plugin"}],
+  "description": [{"language_code": "en_us", "string": "My custom plugin"}]
+}
+```
+
+**Important:**
+- `code_name` must match the folder name
+- `unique_prefix` must be unique and uppercase (check existing plugins to avoid conflicts)
+- `unique_prefix` is used as a prefix for all generated settings (e.g., `MYPLN_RUN`, `MYPLN_CMD`)
+
+### 3. Implement Your Script
+
+Edit `my_plugin/script.py` and implement your data collection logic:
+
+```python
+#!/usr/bin/env python3
+
+import sys
+import os
+sys.path.insert(0, os.path.join(os.path.dirname(__file__), '../../server'))
+sys.path.insert(0, os.path.join(os.path.dirname(__file__), '../plugins'))
+
+from plugin_helper import Plugin_Objects, mylog
+from helper import get_setting_value
+from const import logPath
+
+pluginName = "MYPLN"
+
+LOG_PATH = logPath + "/plugins"
+LOG_FILE = os.path.join(LOG_PATH, f"script.{pluginName}.log")
+RESULT_FILE = os.path.join(LOG_PATH, f"last_result.{pluginName}.log")
+
+# Initialize
+plugin_objects = Plugin_Objects(RESULT_FILE)
+
+try:
+    # Your data collection logic here
+    # For example, scan something and collect results
+
+    # Add an object to results
+    plugin_objects.add_object(
+        Object_PrimaryID="example_id",
+        Object_SecondaryID=None,
+        DateTime="2023-01-02 15:56:30",
+        Watched_Value1="value1",
+        Watched_Value2=None,
+        Watched_Value3=None,
+        Watched_Value4=None,
+        Extra="additional_data",
+        ForeignKey=None
+    )
+
+    # Write results to the log file
+    plugin_objects.write_result_file()
+
+except Exception as e:
+    mylog("none", f"Error: {e}")
+    sys.exit(1)
+```
+
+### 4. Configure Execution
+
+Edit the `RUN` and `CMD` settings in `config.json`:
+
+```json
+{
+  "function": "RUN",
+  "type": {"dataType":"string", "elements": [{"elementType": "select", "elementOptions": [], "transformers": []}]},
+  "default_value": "disabled",
+  "options": ["disabled", "once", "schedule"],
+  "localized": ["name", "description"],
+  "name": [{"language_code":"en_us", "string": "When to run"}],
+  "description": [{"language_code":"en_us", "string": "Enable plugin execution"}]
+},
+{
+  "function": "CMD",
+  "type": {"dataType":"string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+  "default_value": "python3 /app/front/plugins/my_plugin/script.py",
+  "localized": ["name", "description"],
+  "name": [{"language_code":"en_us", "string": "Command"}],
+  "description": [{"language_code":"en_us", "string": "Command to execute"}]
+}
+```
+
+### 5. Test Your Plugin
+
+#### In Dev Container
+
+```bash
+# Test the script directly
+python3 /workspaces/NetAlertX/front/plugins/my_plugin/script.py
+
+# Check the results
+cat /tmp/log/plugins/last_result.MYPLN.log
+```
+
+#### Via UI
+
+1. Restart backend: Run task `[Dev Container] Start Backend (Python)`
+2. Open Settings → Plugin Settings → My Plugin
+3. Set `My Plugin - When to run` to `once`
+4. Click Save
+5. Check `/tmp/log/plugins/last_result.MYPLN.log` for output
+
+### 6. Check Results
+
+Verify your plugin is working:
+
+```bash
+# Check if result file was generated
+ls -la /tmp/log/plugins/last_result.MYPLN.log
+
+# View contents
+cat /tmp/log/plugins/last_result.MYPLN.log
+
+# Check backend logs for errors
+tail -f /tmp/log/stdout.log | grep "my_plugin\|MYPLN"
+```
+
+## Next Steps
+
+Now that you have a working basic plugin:
+
+1. **Add Settings**: Customize behavior via user-configurable settings (see [PLUGINS_DEV_SETTINGS.md](PLUGINS_DEV_SETTINGS.md))
+2. **Implement Data Contract**: Structure your output correctly (see [PLUGINS_DEV_DATA_CONTRACT.md](PLUGINS_DEV_DATA_CONTRACT.md))
+3. **Configure UI**: Display plugin results in the web interface (see [PLUGINS_DEV_UI_COMPONENTS.md](PLUGINS_DEV_UI_COMPONENTS.md))
+4. **Map to Database**: Import data into NetAlertX tables like `CurrentScan` or `Devices`
+5. **Set Schedules**: Run your plugin on a schedule (see [PLUGINS_DEV_CONFIG.md](PLUGINS_DEV_CONFIG.md))
+
+## Common Issues
+
+| Issue | Solution |
+|-------|----------|
+| "Module not found" errors | Ensure `sys.path` includes `/app/server` and `/app/front/plugins` |
+| Settings not appearing | Restart backend and clear browser cache |
+| Results not showing up | Check `/tmp/log/plugins/*.log` and `/tmp/log/stdout.log` for errors |
+| Permission denied | Plugin runs in container, use absolute paths like `/app/front/plugins/...` |
+
+## Resources
+
+- [Full Plugin Development Guide](PLUGINS_DEV.md)
+- [Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md)
+- [Plugin Settings System](PLUGINS_DEV_SETTINGS.md)
+- [Data Sources](PLUGINS_DEV_DATASOURCES.md)
+- [UI Components](PLUGINS_DEV_UI_COMPONENTS.md)
+- [Debugging Plugins](DEBUG_PLUGINS.md)
diff --git a/docs/PLUGINS_DEV_SETTINGS.md b/docs/PLUGINS_DEV_SETTINGS.md
new file mode 100644
index 00000000..4579cdac
--- /dev/null
+++ b/docs/PLUGINS_DEV_SETTINGS.md
@@ -0,0 +1,517 @@
+# Plugin Settings System
+
+Learn how to let users configure your plugin via the NetAlertX UI Settings page.
+
+> [!TIP]
+> For the higher-level settings flow and lifecycle, see [Settings System Documentation](./SETTINGS_SYSTEM.md).
+
+## Overview
+
+Plugin settings allow users to configure:
+- **Execution schedule** (when the plugin runs)
+- **Runtime parameters** (API keys, URLs, thresholds)
+- **Behavior options** (which features to enable/disable)
+- **Command overrides** (customize the executed script)
+
+All settings are defined in your plugin's `config.json` file under the `"settings"` array.
+
+## Setting Definition Structure
+
+Each setting is a JSON object with required and optional properties:
+
+```json
+{
+  "function": "UNIQUE_CODE",
+  "type": {
+    "dataType": "string",
+    "elements": [
+      {
+        "elementType": "input",
+        "elementOptions": [],
+        "transformers": []
+      }
+    ]
+  },
+  "default_value": "default_value_here",
+  "options": [],
+  "localized": ["name", "description"],
+  "name": [
+    {
+      "language_code": "en_us",
+      "string": "Display Name"
+    }
+  ],
+  "description": [
+    {
+      "language_code": "en_us",
+      "string": "Help text describing the setting"
+    }
+  ]
+}
+```
+
+## Required Properties
+
+| Property | Type | Description | Example |
+|----------|------|-------------|---------|
+| `function` | string | Unique identifier for the setting. Used in manifest and when reading values. See [Reserved Function Names](#reserved-function-names) for special values | `"MY_CUSTOM_SETTING"` |
+| `type` | object | Defines the UI component and data type | See [Component Types](#component-types) |
+| `default_value` | varies | Initial value shown in UI | `"https://example.com"` |
+| `localized` | array | Which properties have translations | `["name", "description"]` |
+| `name` | array | Display name in Settings UI (localized) | See [Localized Strings](#localized-strings) |
+
+## Optional Properties
+
+| Property | Type | Description | Example |
+|----------|------|-------------|---------|
+| `description` | array | Help text in Settings UI (localized) | See [Localized Strings](#localized-strings) |
+| `options` | array | Valid values for select/checkbox controls | `["option1", "option2"]` |
+| `events` | string | Trigger action button: `"test"` or `"run"` | `"test"` for notifications |
+| `maxLength` | number | Character limit for input fields | `100` |
+| `readonly` | boolean | Make field read-only | `true` |
+| `override_value` | object | Template-based value override (advanced) | See [Templates](#templates) |
+
+## Reserved Function Names
+
+These function names have special meaning and control core plugin behavior:
+
+### Core Execution Settings
+
+| Function | Purpose | Type | Required | Options |
+|----------|---------|------|----------|---------|
+| `RUN` | **When to execute the plugin** | select | **YES** | `"disabled"`, `"once"`, `"schedule"`, `"always_after_scan"`, `"before_name_updates"`, `"on_new_device"`, `"before_config_save"` |
+| `RUN_SCHD` | **Cron schedule** | input | If `RUN="schedule"` | Cron format: `"0 * * * *"` (hourly) |
+| `CMD` | **Command/script to execute** | input | **YES** | Linux command or path to script |
+| `RUN_TIMEOUT` | **Maximum execution time in seconds** | input | optional | Numeric: `"60"`, `"120"`, etc. |
+
+### Data & Filtering Settings
+
+| Function | Purpose | Type | Required | Options |
+|----------|---------|------|----------|---------|
+| `WATCH` | **Which columns to monitor for changes** | multi-select | optional | Column names from data contract |
+| `REPORT_ON` | **When to send notifications** | select | optional | `"new"`, `"watched-changed"`, `"watched-not-changed"`, `"missing-in-last-scan"` |
+| `DB_PATH` | **External database path** | input | If using SQLite plugin | File path: `"/etc/pihole/pihole-FTL.db"` |
+
+### API & Data Settings
+
+| Function | Purpose | Type | Required | Options |
+|----------|---------|------|----------|---------|
+| `API_SQL` | **Generate API JSON file** | (reserved) | Not implemented | — |
+
+## Component Types
+
+### Text Input
+
+Simple text field for API keys, URLs, thresholds, etc.
+
+```json
+{
+  "function": "URL",
+  "type": {
+    "dataType": "string",
+    "elements": [
+      {
+        "elementType": "input",
+        "elementOptions": [],
+        "transformers": []
+      }
+    ]
+  },
+  "default_value": "https://api.example.com",
+  "localized": ["name", "description"],
+  "name": [{"language_code": "en_us", "string": "API URL"}],
+  "description": [{"language_code": "en_us", "string": "The API endpoint to query"}]
+}
+```
+
+### Password Input
+
+Secure field with SHA256 hashing transformer.
+
+```json
+{
+  "function": "API_KEY",
+  "type": {
+    "dataType": "string",
+    "elements": [
+      {
+        "elementType": "input",
+        "elementOptions": [{"type": "password"}],
+        "transformers": ["sha256"]
+      }
+    ]
+  },
+  "default_value": "",
+  "localized": ["name", "description"],
+  "name": [{"language_code": "en_us", "string": "API Key"}],
+  "description": [{"language_code": "en_us", "string": "Stored securely with SHA256 hashing"}]
+}
+```
+
+### Dropdown/Select
+
+Choose from predefined options.
+
+```json
+{
+  "function": "RUN",
+  "type": {
+    "dataType": "string",
+    "elements": [
+      {
+        "elementType": "select",
+        "elementOptions": [],
+        "transformers": []
+      }
+    ]
+  },
+  "default_value": "disabled",
+  "options": ["disabled", "once", "schedule", "always_after_scan"],
+  "localized": ["name", "description"],
+  "name": [{"language_code": "en_us", "string": "When to run"}],
+  "description": [{"language_code": "en_us", "string": "Select execution trigger"}]
+}
+```
+
+### Multi-Select
+
+Select multiple values (returns array).
+
+```json
+{
+  "function": "WATCH",
+  "type": {
+    "dataType": "array",
+    "elements": [
+      {
+        "elementType": "select",
+        "elementOptions": [{"isMultiSelect": true}],
+        "transformers": []
+      }
+    ]
+  },
+  "default_value": [],
+  "options": ["Status", "IP_Address", "Response_Time"],
+  "localized": ["name", "description"],
+  "name": [{"language_code": "en_us", "string": "Watch columns"}],
+  "description": [{"language_code": "en_us", "string": "Which columns trigger notifications on change"}]
+}
+```
+
+### Checkbox
+
+Boolean toggle.
+
+```json
+{
+  "function": "ENABLED",
+  "type": {
+    "dataType": "boolean",
+    "elements": [
+      {
+        "elementType": "input",
+        "elementOptions": [{"type": "checkbox"}],
+        "transformers": []
+      }
+    ]
+  },
+  "default_value": false,
+  "localized": ["name", "description"],
+  "name": [{"language_code": "en_us", "string": "Enable feature"}],
+  "description": [{"language_code": "en_us", "string": "Toggle this feature on/off"}]
+}
+```
+
+### Textarea
+
+Multi-line text input.
+
+```json
+{
+  "function": "CUSTOM_CONFIG",
+  "type": {
+    "dataType": "string",
+    "elements": [
+      {
+        "elementType": "textarea",
+        "elementOptions": [],
+        "transformers": []
+      }
+    ]
+  },
+  "default_value": "",
+  "localized": ["name", "description"],
+  "name": [{"language_code": "en_us", "string": "Custom Configuration"}],
+  "description": [{"language_code": "en_us", "string": "Enter configuration (one per line)"}]
+}
+```
+
+### Read-Only Label
+
+Display information without user input.
+
+```json
+{
+  "function": "STATUS_DISPLAY",
+  "type": {
+    "dataType": "string",
+    "elements": [
+      {
+        "elementType": "input",
+        "elementOptions": [{"readonly": true}],
+        "transformers": []
+      }
+    ]
+  },
+  "default_value": "Ready",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Status"}]
+}
+```
+
+## Using Settings in Your Script
+
+### Method 1: Via `get_setting_value()` Helper
+
+**Recommended approach** — clean and simple:
+
+```python
+from helper import get_setting_value
+
+# Read the setting by function name with plugin prefix
+api_url = get_setting_value('MYPLN_API_URL')
+api_key = get_setting_value('MYPLN_API_KEY')
+watch_columns = get_setting_value('MYPLN_WATCH')  # Returns list if multi-select
+
+# Use in your script
+mylog("none", f"Connecting to {api_url} with key {api_key}")
+```
+
+### Method 2: Via Command Parameters
+
+For more complex scenarios where you need to **pass settings as command-line arguments**:
+
+Define `params` in your `config.json`:
+
+```json
+{
+  "params": [
+    {
+      "name": "api_url",
+      "type": "setting",
+      "value": "MYPLN_API_URL"
+    },
+    {
+      "name": "timeout",
+      "type": "setting",
+      "value": "MYPLN_RUN_TIMEOUT"
+    }
+  ]
+}
+```
+
+Update your `CMD` setting:
+
+```json
+{
+  "function": "CMD",
+  "default_value": "python3 /app/front/plugins/my_plugin/script.py --url={api_url} --timeout={timeout}"
+}
+```
+
+The framework will replace `{api_url}` and `{timeout}` with actual values before execution.
+
+### Method 3: Via Environment Variables (check with maintainer)
+
+Settings are also available as environment variables:
+
+```bash
+# Environment variable format: <PREFIX>_<FUNCTION>
+MY_PLUGIN_API_URL
+MY_PLUGIN_API_KEY
+MY_PLUGIN_RUN
+```
+
+In Python:
+```python
+import os
+
+api_url = os.environ.get('MYPLN_API_URL', 'default_value')
+```
+
+## Localized Strings
+
+Settings and UI text support multiple languages. Define translations in the `name` and `description` arrays:
+
+```json
+{
+  "localized": ["name", "description"],
+  "name": [
+    {
+      "language_code": "en_us",
+      "string": "API URL"
+    },
+    {
+      "language_code": "es_es",
+      "string": "URL de API"
+    },
+    {
+      "language_code": "de_de",
+      "string": "API-URL"
+    }
+  ],
+  "description": [
+    {
+      "language_code": "en_us",
+      "string": "Enter the API endpoint URL"
+    },
+    {
+      "language_code": "es_es",
+      "string": "Ingrese la URL del endpoint de API"
+    },
+    {
+      "language_code": "de_de",
+      "string": "Geben Sie die API-Endpunkt-URL ein"
+    }
+  ]
+}
+```
+
+- `en_us` - English (required)
+
+
+## Examples
+
+### Example 1: Website Monitor Plugin
+
+```json
+{
+  "settings": [
+    {
+      "function": "RUN",
+      "type": {"dataType": "string", "elements": [{"elementType": "select", "elementOptions": [], "transformers": []}]},
+      "default_value": "disabled",
+      "options": ["disabled", "once", "schedule"],
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "When to run"}],
+      "description": [{"language_code": "en_us", "string": "Enable website monitoring"}]
+    },
+    {
+      "function": "RUN_SCHD",
+      "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+      "default_value": "*/5 * * * *",
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "Schedule"}],
+      "description": [{"language_code": "en_us", "string": "Cron format (default: every 5 minutes)"}]
+    },
+    {
+      "function": "CMD",
+      "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+      "default_value": "python3 /app/front/plugins/website_monitor/script.py urls={urls}",
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "Command"}],
+      "description": [{"language_code": "en_us", "string": "Command to execute"}]
+    },
+    {
+      "function": "RUN_TIMEOUT",
+      "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+      "default_value": "60",
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "Timeout"}],
+      "description": [{"language_code": "en_us", "string": "Maximum execution time in seconds"}]
+    },
+    {
+      "function": "URLS",
+      "type": {"dataType": "array", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+      "default_value": ["https://example.com"],
+      "maxLength": 200,
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "URLs to monitor"}],
+      "description": [{"language_code": "en_us", "string": "One URL per line"}]
+    },
+    {
+      "function": "WATCH",
+      "type": {"dataType": "array", "elements": [{"elementType": "select", "elementOptions": [{"isMultiSelect": true}], "transformers": []}]},
+      "default_value": ["Status_Code"],
+      "options": ["Status_Code", "Response_Time", "Certificate_Expiry"],
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "Watch columns"}],
+      "description": [{"language_code": "en_us", "string": "Which changes trigger notifications"}]
+    }
+  ]
+}
+```
+
+### Example 2: PiHole Integration Plugin
+
+```json
+{
+  "settings": [
+    {
+      "function": "RUN",
+      "type": {"dataType": "string", "elements": [{"elementType": "select", "elementOptions": [], "transformers": []}]},
+      "default_value": "disabled",
+      "options": ["disabled", "schedule"],
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "When to run"}],
+      "description": [{"language_code": "en_us", "string": "Enable PiHole integration"}]
+    },
+    {
+      "function": "DB_PATH",
+      "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [], "transformers": []}]},
+      "default_value": "/etc/pihole/pihole-FTL.db",
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "Database path"}],
+      "description": [{"language_code": "en_us", "string": "Path to pihole-FTL.db inside container"}]
+    },
+    {
+      "function": "API_KEY",
+      "type": {"dataType": "string", "elements": [{"elementType": "input", "elementOptions": [{"type": "password"}], "transformers": ["sha256"]}]},
+      "default_value": "",
+      "localized": ["name", "description"],
+      "name": [{"language_code": "en_us", "string": "API Key"}],
+      "description": [{"language_code": "en_us", "string": "PiHole API key (optional, stored securely)"}]
+    }
+  ]
+}
+```
+
+## Validation & Testing
+
+### Check Settings Are Recognized
+
+After saving your `config.json`:
+
+1. Restart the backend: Run task `[Dev Container] Start Backend (Python)`
+2. Open Settings page in UI
+3. Navigate to Plugin Settings
+4. Look for your plugin's settings
+
+### Read Setting Values in Script
+
+Test that values are accessible:
+
+```python
+from helper import get_setting_value
+
+# Try to read a setting
+value = get_setting_value('MYPLN_API_URL')
+mylog('none', f"Setting value: {value}")
+
+# Should print the user-configured value or default
+```
+
+### Debug Settings
+
+Check backend logs:
+
+```bash
+tail -f /tmp/log/stdout.log | grep -i "setting\|MYPLN"
+```
+
+## See Also
+
+- [Settings System Documentation](./SETTINGS_SYSTEM.md) - Full settings flow and lifecycle
+- [Quick Start Guide](PLUGINS_DEV_QUICK_START.md) - Get a working plugin quickly
+- [Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md) - Output data format
+- [UI Components](PLUGINS_DEV_UI_COMPONENTS.md) - Display plugin results
diff --git a/docs/PLUGINS_DEV_UI_COMPONENTS.md b/docs/PLUGINS_DEV_UI_COMPONENTS.md
new file mode 100644
index 00000000..53d8fb71
--- /dev/null
+++ b/docs/PLUGINS_DEV_UI_COMPONENTS.md
@@ -0,0 +1,642 @@
+# Plugin UI Components
+
+Configure how your plugin's data is displayed in the NetAlertX web interface.
+
+## Overview
+
+Plugin results are displayed in the UI via the **Plugins page** and **Device details tabs**. You control the appearance and functionality of these displays by defining `database_column_definitions` in your plugin's `config.json`.
+
+Each column definition specifies:
+- Which data field to display
+- How to render it (label, link, color-coded badge, etc.)
+- What CSS classes to apply
+- What transformations to apply (regex, string replacement, etc.)
+
+## Column Definition Structure
+
+```json
+{
+  "column": "Object_PrimaryID",
+  "mapped_to_column": "devMac",
+  "mapped_to_column_data": null,
+  "css_classes": "col-sm-2",
+  "show": true,
+  "type": "device_mac",
+  "default_value": "",
+  "options": [],
+  "options_params": [],
+  "localized": ["name"],
+  "name": [
+    {
+      "language_code": "en_us",
+      "string": "MAC Address"
+    }
+  ]
+}
+```
+
+## Properties
+
+| Property | Type | Required | Description |
+|----------|------|----------|-------------|
+| `column` | string | **YES** | Source column name from data contract (e.g., `Object_PrimaryID`, `Watched_Value1`) |
+| `mapped_to_column` | string | no | Target database column if mapping to a table like `CurrentScan` |
+| `mapped_to_column_data` | object | no | Static value to map instead of using column data |
+| `css_classes` | string | no | Bootstrap CSS classes for width/spacing (e.g., `"col-sm-2"`, `"col-sm-6"`) |
+| `show` | boolean | **YES** | Whether to display in UI (must be `true` to appear) |
+| `type` | string | **YES** | How to render the value (see [Render Types](#render-types)) |
+| `default_value` | varies | **YES** | Default if column is empty |
+| `options` | array | no | Options for `select`/`threshold`/`replace`/`regex` types |
+| `options_params` | array | no | Dynamic options from SQL or settings |
+| `localized` | array | **YES** | Which properties need translations (e.g., `["name", "description"]`) |
+| `name` | array | **YES** | Display name in UI (localized strings) |
+| `description` | array | no | Help text in UI (localized strings) |
+| `maxLength` | number | no | Character limit for input fields |
+
+## Render Types
+
+### Display-Only Types
+
+These render as read-only display elements:
+
+#### `label`
+Plain text display (read-only).
+
+```json
+{
+  "column": "Watched_Value1",
+  "show": true,
+  "type": "label",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Status"}]
+}
+```
+
+**Output:** `online`
+
+---
+
+#### `device_mac`
+Renders as a clickable link to the device with the given MAC address.
+
+```json
+{
+  "column": "ForeignKey",
+  "show": true,
+  "type": "device_mac",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Device"}]
+}
+```
+
+**Input:** `aa:bb:cc:dd:ee:ff`
+**Output:** Clickable link to device details page
+
+---
+
+#### `device_ip`
+Resolves an IP address to a MAC address and creates a device link.
+
+```json
+{
+  "column": "Object_SecondaryID",
+  "show": true,
+  "type": "device_ip",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Host"}]
+}
+```
+
+**Input:** `192.168.1.100`
+**Output:** Link to device with that IP (if known)
+
+---
+
+#### `device_name_mac`
+Creates a device link with the target device's name as the link label.
+
+```json
+{
+  "column": "Object_PrimaryID",
+  "show": true,
+  "type": "device_name_mac",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Device Name"}]
+}
+```
+
+**Input:** `aa:bb:cc:dd:ee:ff`
+**Output:** Device name (clickable link to device)
+
+---
+
+#### `url`
+Renders as a clickable HTTP/HTTPS link.
+
+```json
+{
+  "column": "Watched_Value1",
+  "show": true,
+  "type": "url",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Endpoint"}]
+}
+```
+
+**Input:** `https://example.com/api`
+**Output:** Clickable link
+
+---
+
+#### `url_http_https`
+Creates two links (HTTP and HTTPS) as lock icons for the given IP/hostname.
+
+```json
+{
+  "column": "Object_SecondaryID",
+  "show": true,
+  "type": "url_http_https",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Web Links"}]
+}
+```
+
+**Input:** `192.168.1.50`
+**Output:** 🔓 HTTP link | 🔒 HTTPS link
+
+---
+
+#### `textarea_readonly`
+Multi-line read-only display with newlines preserved.
+
+```json
+{
+  "column": "Extra",
+  "show": true,
+  "type": "textarea_readonly",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Details"}]
+}
+```
+
+---
+
+### Interactive Types
+
+#### `textbox_save`
+User-editable text box that persists changes to the database (typically `UserData` column).
+
+```json
+{
+  "column": "UserData",
+  "show": true,
+  "type": "textbox_save",
+  "default_value": "",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Notes"}]
+}
+```
+
+---
+
+### Styled/Transformed Types
+
+#### `label` with `threshold`
+Color-codes values based on ranges. Useful for status codes, latency, capacity percentages.
+
+```json
+{
+  "column": "Watched_Value1",
+  "show": true,
+  "type": "threshold",
+  "options": [
+    {
+      "maximum": 199,
+      "hexColor": "#792D86"  // Purple for <199
+    },
+    {
+      "maximum": 299,
+      "hexColor": "#5B862D"  // Green for 200-299
+    },
+    {
+      "maximum": 399,
+      "hexColor": "#7D862D"  // Orange for 300-399
+    },
+    {
+      "maximum": 499,
+      "hexColor": "#BF6440"  // Red-orange for 400-499
+    },
+    {
+      "maximum": 999,
+      "hexColor": "#D33115"  // Dark red for 500+
+    }
+  ],
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "HTTP Status"}]
+}
+```
+
+**How it works:**
+- Value `150` → Purple (≤199)
+- Value `250` → Green (≤299)
+- Value `350` → Orange (≤399)
+- Value `450` → Red-orange (≤499)
+- Value `550` → Dark red (>500)
+
+---
+
+#### `replace`
+Replaces specific values with display strings or HTML.
+
+```json
+{
+  "column": "Watched_Value2",
+  "show": true,
+  "type": "replace",
+  "options": [
+    {
+      "equals": "online",
+      "replacement": "<i class='fa-solid fa-circle' style='color: green;'></i> Online"
+    },
+    {
+      "equals": "offline",
+      "replacement": "<i class='fa-solid fa-circle' style='color: red;'></i> Offline"
+    },
+    {
+      "equals": "idle",
+      "replacement": "<i class='fa-solid fa-circle' style='color: yellow;'></i> Idle"
+    }
+  ],
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Status"}]
+}
+```
+
+**Output Examples:**
+- `"online"` → 🟢 Online
+- `"offline"` → 🔴 Offline
+- `"idle"` → 🟡 Idle
+
+---
+
+#### `regex`
+Applies a regular expression to extract/transform values.
+
+```json
+{
+  "column": "Watched_Value1",
+  "show": true,
+  "type": "regex",
+  "options": [
+    {
+      "type": "regex",
+      "param": "([0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3})"
+    }
+  ],
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "IP Address"}]
+}
+```
+
+**Input:** `Host: 192.168.1.100 Port: 8080`
+**Output:** `192.168.1.100`
+
+---
+
+#### `eval`
+Evaluates JavaScript code with access to the column value (use `${value}` or `{value}`).
+
+```json
+{
+  "column": "Watched_Value1",
+  "show": true,
+  "type": "eval",
+  "default_value": "",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Formatted Value"}]
+}
+```
+
+**Example with custom formatting:**
+```json
+{
+  "column": "Watched_Value1",
+  "show": true,
+  "type": "eval",
+  "options": [
+    {
+      "type": "eval",
+      "param": "`<b>${value}</b> units`"
+    }
+  ],
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Value with Units"}]
+}
+```
+
+**Input:** `42`
+**Output:** **42** units
+
+---
+
+### Chaining Types
+
+You can chain multiple transformations with dot notation:
+
+```json
+{
+  "column": "Watched_Value3",
+  "show": true,
+  "type": "regex.url_http_https",
+  "options": [
+    {
+      "type": "regex",
+      "param": "([\\d.:]+)"  // Extract IP/host
+    }
+  ],
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "HTTP/S Links"}]
+}
+```
+
+**Flow:**
+1. Apply regex to extract `192.168.1.50` from input
+2. Create HTTP/HTTPS links for that host
+
+---
+
+## Dynamic Options
+
+### SQL-Driven Select
+
+Use SQL query results to populate dropdown options:
+
+```json
+{
+  "column": "Watched_Value2",
+  "show": true,
+  "type": "select",
+  "options": ["{value}"],
+  "options_params": [
+    {
+      "name": "value",
+      "type": "sql",
+      "value": "SELECT devType as id, devType as name FROM Devices UNION SELECT 'Unknown' as id, 'Unknown' as name ORDER BY id"
+    }
+  ],
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Device Type"}]
+}
+```
+
+The SQL query must return exactly **2 columns:**
+- **First column (id):** Option value
+- **Second column (name):** Display label
+
+---
+
+### Setting-Driven Select
+
+Use plugin settings to populate options:
+
+```json
+{
+  "column": "Watched_Value1",
+  "show": true,
+  "type": "select",
+  "options": ["{value}"],
+  "options_params": [
+    {
+      "name": "value",
+      "type": "setting",
+      "value": "MYPLN_AVAILABLE_STATUSES"
+    }
+  ],
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Status"}]
+}
+```
+
+---
+
+## Mapping to Database Tables
+
+### Mapping to `CurrentScan`
+
+To import plugin data into the device scan pipeline (for notifications, heuristics, etc.):
+
+1. Add `"mapped_to_table": "CurrentScan"` at the root level of `config.json`
+2. Add `"mapped_to_column"` property to each column definition
+
+```json
+{
+  "code_name": "my_device_scanner",
+  "unique_prefix": "MYSCAN",
+  "mapped_to_table": "CurrentScan",
+  "database_column_definitions": [
+    {
+      "column": "Object_PrimaryID",
+      "mapped_to_column": "cur_MAC",
+      "show": true,
+      "type": "device_mac",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "MAC Address"}]
+    },
+    {
+      "column": "Object_SecondaryID",
+      "mapped_to_column": "cur_IP",
+      "show": true,
+      "type": "device_ip",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "IP Address"}]
+    },
+    {
+      "column": "NameDoesntMatter",
+      "mapped_to_column": "cur_ScanMethod",
+      "mapped_to_column_data": {
+        "value": "MYSCAN"
+      },
+      "show": true,
+      "type": "label",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "Scan Method"}]
+    }
+  ]
+}
+```
+
+---
+
+### Using Static Values
+
+Use `mapped_to_column_data` to map a static value instead of reading from a column:
+
+```json
+{
+  "column": "NameDoesntMatter",
+  "mapped_to_column": "cur_ScanMethod",
+  "mapped_to_column_data": {
+    "value": "MYSCAN"
+  },
+  "show": true,
+  "type": "label",
+  "localized": ["name"],
+  "name": [{"language_code": "en_us", "string": "Discovery Method"}]
+}
+```
+
+This always sets `cur_ScanMethod` to `"MYSCAN"` regardless of column data.
+
+---
+
+## Filters
+
+Control which rows are displayed based on filter conditions. Filters are applied on the client-side in JavaScript.
+
+```json
+{
+  "data_filters": [
+    {
+      "compare_column": "Object_PrimaryID",
+      "compare_operator": "==",
+      "compare_field_id": "txtMacFilter",
+      "compare_js_template": "'{value}'.toString()",
+      "compare_use_quotes": true
+    }
+  ]
+}
+```
+
+| Property | Description |
+|----------|-------------|
+| `compare_column` | The column from plugin results to compare (left side) |
+| `compare_operator` | JavaScript operator: `==`, `!=`, `<`, `>`, `<=`, `>=`, `includes`, `startsWith` |
+| `compare_field_id` | HTML input field ID containing the filter value (right side) |
+| `compare_js_template` | JavaScript template to transform values. Use `{value}` placeholder |
+| `compare_use_quotes` | If `true`, wrap result in quotes for string comparison |
+
+**Example: Filter by MAC address**
+
+```json
+{
+  "data_filters": [
+    {
+      "compare_column": "ForeignKey",
+      "compare_operator": "==",
+      "compare_field_id": "txtMacFilter",
+      "compare_js_template": "'{value}'.toString()",
+      "compare_use_quotes": true
+    }
+  ]
+}
+```
+
+When viewing a device detail page, the `txtMacFilter` field is populated with that device's MAC, and only rows where `ForeignKey == MAC` are shown.
+
+---
+
+## Example: Complete Column Definitions
+
+```json
+{
+  "database_column_definitions": [
+    {
+      "column": "Object_PrimaryID",
+      "mapped_to_column": "cur_MAC",
+      "css_classes": "col-sm-2",
+      "show": true,
+      "type": "device_mac",
+      "default_value": "",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "MAC Address"}]
+    },
+    {
+      "column": "Object_SecondaryID",
+      "mapped_to_column": "cur_IP",
+      "css_classes": "col-sm-2",
+      "show": true,
+      "type": "device_ip",
+      "default_value": "unknown",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "IP Address"}]
+    },
+    {
+      "column": "DateTime",
+      "css_classes": "col-sm-2",
+      "show": true,
+      "type": "label",
+      "default_value": "",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "Last Seen"}]
+    },
+    {
+      "column": "Watched_Value1",
+      "css_classes": "col-sm-2",
+      "show": true,
+      "type": "threshold",
+      "options": [
+        {"maximum": 199, "hexColor": "#792D86"},
+        {"maximum": 299, "hexColor": "#5B862D"},
+        {"maximum": 399, "hexColor": "#7D862D"},
+        {"maximum": 499, "hexColor": "#BF6440"},
+        {"maximum": 999, "hexColor": "#D33115"}
+      ],
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "HTTP Status"}]
+    },
+    {
+      "column": "Watched_Value2",
+      "css_classes": "col-sm-1",
+      "show": true,
+      "type": "label",
+      "default_value": "",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "Response Time"}]
+    },
+    {
+      "column": "Extra",
+      "css_classes": "col-sm-3",
+      "show": true,
+      "type": "textarea_readonly",
+      "default_value": "",
+      "localized": ["name"],
+      "name": [{"language_code": "en_us", "string": "Additional Info"}]
+    }
+  ]
+}
+```
+
+---
+
+## CSS Classes
+
+Use Bootstrap grid classes to control column widths in tables:
+
+| Class | Width | Usage |
+|-------|-------|-------|
+| `col-sm-1` | ~8% | Very narrow (icons, status) |
+| `col-sm-2` | ~16% | Narrow (MACs, IPs) |
+| `col-sm-3` | ~25% | Medium (names, URLs) |
+| `col-sm-4` | ~33% | Medium-wide (descriptions) |
+| `col-sm-6` | ~50% | Wide (large content) |
+
+---
+
+## Validation Checklist
+
+- [ ] All columns have `"show": true` or `false`
+- [ ] Display columns with `"type"` specified from supported types
+- [ ] Localized strings include at least `en_us`
+- [ ] `mapped_to_column` matches target table schema (if using mapping)
+- [ ] Options/thresholds have correct structure
+- [ ] CSS classes are valid Bootstrap grid classes
+- [ ] Chaining types (e.g., `regex.url_http_https`) are supported combinations
+
+---
+
+## See Also
+
+- [Plugin Data Contract](PLUGINS_DEV_DATA_CONTRACT.md) - What data fields are available
+- [Plugin Settings System](PLUGINS_DEV_SETTINGS.md) - Configure user input
+- [Database Mapping](PLUGINS_DEV.md#-mapping-the-plugin-results-into-a-database-table) - Map data to core tables
+- [Debugging Plugins](DEBUG_PLUGINS.md) - Troubleshoot display issues
diff --git a/mkdocs.yml b/mkdocs.yml
index 38ce3e83..932dca0e 100755
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -89,8 +89,14 @@ nav:
         - Environment Setup: DEV_ENV_SETUP.md
         - Builds: BUILDS.md
         - Devcontainer: DEV_DEVCONTAINER.md
-        - Custom Plugins: PLUGINS_DEV.md
-        - Plugin Config: PLUGINS_DEV_CONFIG.md
+        - Custom Plugins:
+          - Overview: PLUGINS_DEV.md
+          - Quick Start: PLUGINS_DEV_QUICK_START.md
+          - Data Contract: PLUGINS_DEV_DATA_CONTRACT.md
+          - Settings System: PLUGINS_DEV_SETTINGS.md
+          - Data Sources: PLUGINS_DEV_DATASOURCES.md
+          - UI Components: PLUGINS_DEV_UI_COMPONENTS.md
+          - Config Lifecycle: PLUGINS_DEV_CONFIG.md
         - Frontend Development: FRONTEND_DEVELOPMENT.md
         - Database: DATABASE.md
         - Settings: SETTINGS_SYSTEM.md