- Saved Dashboards page with favorites, tags, search, and actions
+
+ + Saved Dashboards page with favorites, tags, search, and actions +
- Saved Dashboards page with favorites, tags, search, and actions
+
+ + Saved Dashboards page with favorites, tags, search, and actions +
-
-Simply fill in your email, full name, and password to create the initial admin account. This user will have full administrative privileges to configure providers, manage services, and access all OpsiMate features.
-
-## Next Steps
-
-After deployment:
-
-1. **Access OpsiMate** at `http://localhost:8080`
-2. **Configure your settings** - [See configuration guide](configuration)
-3. **Check system requirements** - [System requirements](system-requirements)
-
-## Support
-
-If you encounter issues during deployment:
-
-- Check the [configuration guide](configuration)
-- Join our [community discussions](https://github.com/opsimate/opsimate/discussions)
-- Report bugs on [GitHub Issues](https://github.com/opsimate/opsimate/issues)
diff --git a/opsimate-docs/docs/getting-started/introduction.mdx b/opsimate-docs/docs/getting-started/introduction.mdx
new file mode 100644
index 0000000..be175b9
--- /dev/null
+++ b/opsimate-docs/docs/getting-started/introduction.mdx
@@ -0,0 +1,91 @@
+---
+id: introduction
+slug: /getting-started/introduction
+sidebar_position: 1
+---
+
+# Introduction
+
+One platform to monitor, manage, and optimize your entire infrastructure
+
+
+Simply fill in your email, full name, and password to create the initial admin account. This user will have full administrative privileges to configure providers, manage services, and access all OpsiMate features.
+
+## Next Steps
+
+After deployment:
+
+1. **Access OpsiMate** at `http://localhost:8080`
+2. **Configure your settings** - [See configuration guide](configuration)
+3. **Check system requirements** - [System requirements](system-requirements)
+
+## Support
+
+If you encounter issues during deployment:
+
+- Check the [configuration guide](configuration)
+- Join our [community discussions](https://github.com/opsimate/opsimate/discussions)
+- Report bugs on [GitHub Issues](https://github.com/opsimate/opsimate/issues)
diff --git a/opsimate-docs/docs/getting-started/system-requirements.md b/opsimate-docs/docs/getting-started/system-requirements.md
deleted file mode 100644
index 0ede511..0000000
--- a/opsimate-docs/docs/getting-started/system-requirements.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-id: system-requirements
-title: System Requirements
-sidebar_position: 3
----
-
-# System Requirements
-
-OpsiMate is lightweight and runs efficiently on minimal hardware.
-
-## 💻 Hardware Requirements
-
-| Component | Minimum | Recommended |
-|-----------|---------|-------------|
-| **CPU** | 1 vCPU | 2+ vCPUs |
-| **RAM** | 512 MB | 2 GB+ |
-| **Storage** | 1 GB | 10 GB+ |
-## 🐳 Software Requirements
-
-- **Docker** 20.10+ or Docker Desktop
-- **Operating System**: Linux, macOS 10.15+, Windows 10+ (WSL2)
-
-## 🌐 Network Requirements
-
-- **Port 8080**: Web interface
-- **Port 3001**: API server
-- **Port 22**: SSH access to monitored servers
-- Internet access for Docker images
-
-:::tip Ready to Deploy?
-Once your system meets these requirements, head to the [deployment guide](deploy) to get started!
-:::
-
-
diff --git a/opsimate-docs/docs/glossary/index.md b/opsimate-docs/docs/glossary/index.md
new file mode 100644
index 0000000..74bd966
--- /dev/null
+++ b/opsimate-docs/docs/glossary/index.md
@@ -0,0 +1,194 @@
+---
+title: Glossary
+sidebar_position: 1
+---
+
+# Glossary
+Welcome to the OpsiMate glossary! This page explains the key terms and concepts you'll encounter while using OpsiMate. Think of this as your quick reference guide whenever you run into unfamiliar terminology.
+
+:::tip How to Use This Glossary
+- **New to OpsiMate?** Browse through to get familiar with core concepts.
+- **Reading documentation?** Use this page as a quick reference when a term is unclear.
+- **Setting up monitoring?** Return here to clarify concepts before proceeding.
+:::
+
+### A-C
+
+#### Active Alert
+An alert in **Active** state is currently firing and requires your attention.
+- See also [TV Mode](/docs/alerts/tv-mode-view) for full-screen monitoring.
+
+#### Alerts
+Notifications generated when service health or metrics cross predefined thresholds.
+- Can come from OpsiMate or integrated tools like [Grafana](../integrations/grafana), [Zabbix](../integrations/zabbix), or [Uptime Kuma](../integrations/uptime-kuma).
+> Think of alerts as your system’s “check engine” light.
+
+#### API Token
+A secret key used to securely authenticate requests between OpsiMate and external integrations.
+- Example usage: configuring [Uptime Kuma webhooks](../integrations/uptime-kuma).
+
+#### Auto-discovery
+OpsiMate automatically detects available services (like Docker containers or Kubernetes pods) under a configured provider.
+- This saves time and ensures you don’t miss any critical services.
+
+#### Alerts Dismissed
+A status indicating that an alert has been acknowledged or resolved.
+
+### D-F
+
+#### Dashboard
+A visual interface displaying alerts, service status, and metrics.
+- Can be saved, tagged, and filtered for quick access.
+- Related guide: [Saved Dashboards](/docs/dashboards/saved-dashboards).
+
+#### Docker Commands
+SSH-based commands used to control Docker containers monitored by OpsiMate:
+
+```bash
+docker start container-name
+docker stop container-name
+docker restart container-name
+```
+### E–F
+
+#### External System / Integration
+External tools connected to **OpsiMate** to provide alerts, metrics, logs, or dashboards.
+
+Common examples include:
+- [Grafana](https://grafana.com/)
+- [Datadog](https://www.datadoghq.com/)
+- [Kibana](https://www.elastic.co/kibana/)
+- [Zabbix](https://www.zabbix.com/)
+
+**Analogy:** Think of integrations as OpsiMate’s *helpers*—they do the monitoring work and send the important information back to OpsiMate to organize and display.
+
+### G–L
+
+#### Integration
+An **integration** is the actual connection between OpsiMate and an external system. Once connected, OpsiMate can pull in alerts, metrics, or logs and manage them from a single place.
+
+If *External Systems* are the helpers, **integrations** are the handshakes that allow them to talk to OpsiMate.
+
+#### Kubernetes Pods
+Pods are the **smallest deployable units in Kubernetes**, each containing one or more containers that run together.
+
+OpsiMate can automatically discover and monitor pods when connected to a Kubernetes provider.
+
+Learn more:
+- [Kubernetes Pods Documentation](https://kubernetes.io/docs/concepts/workloads/pods/)
+
+#### Kubectl Commands
+`kubectl` is the command-line tool used to manage Kubernetes clusters, pods, and resources.
+
+Common examples include:
+```bash
+kubectl get pods -n namespace
+kubectl delete pod pod-name -n namespace
+```
+These commands allow you to inspect and control Kubernetes workloads that OpsiMate is monitoring.
+
+### Providers
+Providers represent the infrastructure where your services live—such as servers, Kubernetes clusters, or cloud platforms.
+
+Providers are the **starting point** when connecting your infrastructure to OpsiMate.
+
+Learn more:
+- [Adding Providers](/docs/providers-services/providers/add-provider)
+
+### M–O
+
+#### Saved Dashboard
+A **saved dashboard** is a stored monitoring view that includes selected filters, visible columns, and tags.
+
+This allows you to quickly return to your preferred monitoring setup without rebuilding it each time.
+
+:::tip Pro Tip
+Save dashboards for frequently checked environments like production, staging, or critical services.
+:::
+
+#### Service
+A **service** is any running application, process, container, or pod that delivers value within your system.
+
+Services are the core units monitored and controlled in OpsiMate.
+
+**Analogy:**
+Services are the *engines*, and OpsiMate is the *dashboard* showing how they’re performing.
+
+#### Service Tags
+Service tags are labels applied to services to help organize, filter, and associate them with alerts.
+
+Common examples include:
+- `environment` (production, staging)
+- `team`
+- `criticality`
+
+Tags play a key role in alert correlation and filtering across dashboards.
+
+### P–R
+
+#### SSH (Secure Shell)
+SSH is a secure protocol used to remotely access and manage servers.
+
+OpsiMate relies on SSH to monitor and control **server-based providers**.
+
+Learn more:
+- [What is SSH?](https://www.ssh.com/academy/ssh)
+
+#### Systemd Service
+A **systemd service** is a Linux system service managed by `systemd`.
+
+OpsiMate allows you to monitor and control systemd services using SSH-based commands:
+```bash
+sudo systemctl start service-name
+sudo systemctl stop service-name
+sudo systemctl restart service-name
+```
+This makes it easy to manage core server services directly from OpsiMate.
+
+### S–Z
+
+#### TV Mode
+TV Mode is a **full-screen alert display** designed for shared screens or monitoring rooms.
+
+It shows:
+- Active alerts
+- Dismissed alerts
+- Real-time service health at a glance
+
+Learn more:
+- [TV Mode View](/docs/alerts/tv-mode-view)
+
+#### Webhook
+A **webhook** is an HTTP callback that allows external systems to push alerts to OpsiMate in real time.
+
+Tools like [Uptime Kuma](https://uptime.kuma.pet/) and [Zabbix](https://www.zabbix.com/) use webhooks to notify OpsiMate when issues occur.
+
+**Analogy:**
+A webhook is like a *mailman*—it automatically delivers messages the moment something happens.
+
+#### Zabbix
+Zabbix is an enterprise monitoring platform used for tracking networks, servers, and applications.
+
+When integrated with OpsiMate, Zabbix sends alerts via webhooks for centralized alert management.
+
+Learn more:
+- [Zabbix Documentation](https://www.zabbix.com/documentation)
+
+### How These Terms Fit Together
+Understanding how these concepts connect helps you get the most out of OpsiMate:
+
+- **Providers** host your infrastructure
+- **Services** run on providers
+- **Service tags** help group and correlate services with alerts
+- **Integrations** pull alerts and metrics from external systems
+- **Webhooks** push alerts into OpsiMate in real time
+- **Dashboards** and **TV Mode** visualize system health
+- **SSH** and **Kubectl commands** allow service-level control
+
+:::success Learning Path
+Start by adding Providers and Services, set up Dashboards, then connect integrations for alerting. Once comfortable, explore advanced monitoring with auto-discovery and webhooks.
+:::
+
+
+
+
diff --git a/opsimate-docs/docs/integrations/gcp.md b/opsimate-docs/docs/integrations/gcp.mdx
similarity index 51%
rename from opsimate-docs/docs/integrations/gcp.md
rename to opsimate-docs/docs/integrations/gcp.mdx
index df1dcca..42d8fdb 100644
--- a/opsimate-docs/docs/integrations/gcp.md
+++ b/opsimate-docs/docs/integrations/gcp.mdx
@@ -1,34 +1,38 @@
---
-sidebar_position: 4
+id: gcp
+title: GCP Integration
+slug: /integrations/gcp
+sidebar_label: GCP Integration
+sidebar_position: 3
tags: [Alerts]
---
# GCP Integration
-The **GCP integration** lets you send alerts from Google Cloud Platform into OpsiMate using **webhook-based push notifications**.
+The **GCP integration** lets you send alerts from **Google Cloud Platform** into OpsiMate using webhook-based push notifications.
-Instead of OpsiMate pulling alerts from GCP, your GCP alerting policies **push alerts** directly to OpsiMate.
+Instead of OpsiMate pulling alerts from GCP, your GCP alerting policies push alerts directly to OpsiMate.
## Webhook URL
Configure your GCP notification channel to send alerts to your OpsiMate server:
```text
-http://localhost:3001/api/v1/alerts/custom/gcp?api_token={your_api_token}
+/api/v1/alerts/custom/gcp?api_token={your_api_token}
```
-Replace `{your_api_token}` with the API token configured in your OpsiMate server.
+> Replace `{your_api_token}` with the API token configured in your OpsiMate server.
## API Token Configuration
The API token used in the webhook URL is managed by OpsiMate through an environment variable:
-- **Env var**: `API_TOKEN`
-- **Default value**: `opsimate`
+- **Env var:** `API_TOKEN`
+- **Default value:** `opsimate`
This value is also used as the default for the `api_token` query parameter in the webhook URL.
-If you are using the **simple deployment** (via the provided `docker-compose.yml`), the `API_TOKEN` environment variable is already defined there for you.
+If you are using the simple deployment (via the provided `docker-compose.yml`), the `API_TOKEN` environment variable is already defined there for you.
Make sure your OpsiMate server is started with `API_TOKEN` set (or rely on the default), and use the same value in the GCP webhook URL.
@@ -38,17 +42,26 @@ To send alerts from GCP to OpsiMate via webhook:
1. In the **Google Cloud Console**, go to **Monitoring → Alerting**.
2. Open **Notification channels**.
-3. Create or edit a **Webhook** notification channel.
+3. Create or edit a **Webhook notification channel**.
4. Set the **Webhook URL** to your OpsiMate endpoint, for example:
- - `http://your-opsimate-host/api/v1/alerts/custom/gcp?api_token={your_api_token}`
+
+```text
+http://your-opsimate-host/api/v1/alerts/custom/gcp?api_token={your_api_token}
+```
+
5. Save the notification channel.
6. Attach this webhook notification channel to the alerting policies you want to forward to OpsiMate.
## Important Disclaimer
-GCP sends alerts via webhook only to **publicly reachable HTTP endpoints**.
+GCP sends alerts via webhook **only to publicly reachable HTTP endpoints**.
-- If you are running OpsiMate locally (for example at `http://localhost:3001`), GCP **cannot** call this URL directly from the internet.
-- For production use, deploy OpsiMate behind a **publicly accessible URL** (or expose it securely via tunneling / reverse proxy) so that GCP can reach the webhook endpoint.
+- If you are running OpsiMate locally (for example at ``), GCP cannot call this URL directly from the internet.
+- For production use, deploy OpsiMate behind a publicly accessible URL (or expose it securely via tunneling / reverse proxy) so that GCP can reach the webhook endpoint.
Once configured, alerts pushed from GCP will appear in the **alerts table** in OpsiMate with the **GCP integration icon**, so you can easily identify their source.
+
+
+
+
+
diff --git a/opsimate-docs/docs/integrations/uptime-kuma.md b/opsimate-docs/docs/integrations/uptime-kuma.md
deleted file mode 100644
index 193dbf0..0000000
--- a/opsimate-docs/docs/integrations/uptime-kuma.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-sidebar_position: 5
-tags: [Alerts]
----
-
-# Uptime Kuma Integration
-
-The **Uptime Kuma integration** lets you send alerts from Uptime Kuma into OpsiMate using **webhook-based push notifications**.
-
-Instead of OpsiMate pulling status from Uptime Kuma, your Uptime Kuma notifications **push alerts** directly to OpsiMate.
-
-## Webhook URL
-
-Configure your Uptime Kuma notification to send alerts to your OpsiMate server.
-
-Use your OpsiMate alerts webhook endpoint, for example:
-
-```text
-http://localhost:3001/api/v1/alerts/custom/uptime-kuma?api_token={your_api_token}
-```
-
-Replace `{your_api_token}` with the API token configured in your OpsiMate server.
-
-> The exact path segment (for example `uptime-kuma`) should match how the Uptime Kuma integration is configured in your OpsiMate backend.
-
-## API Token Configuration
-
-The API token used in the webhook URL is managed by OpsiMate through an environment variable:
-
-- **Env var**: `API_TOKEN`
-- **Default value**: `opsimate`
-
-This value is also used as the default for the `api_token` query parameter in the webhook URL.
-
-If you are using the **simple deployment** (via the provided `docker-compose.yml`), the `API_TOKEN` environment variable is already defined there for you.
-
-Make sure your OpsiMate server is started with `API_TOKEN` set (or rely on the default), and use the same value in the Uptime Kuma webhook URL.
-
-## Setting Up the Webhook in Uptime Kuma
-
-To send alerts from Uptime Kuma to OpsiMate via webhook:
-
-1. In **Uptime Kuma**, go to **Settings → Notifications**.
-2. Click **Add New Notification**.
-3. Choose **Webhook** as the notification type.
-4. Set the **URL** to your OpsiMate endpoint, for example:
- - `http://your-opsimate-host/api/v1/alerts/custom/uptime-kuma?api_token={your_api_token}`
-5. Keep the **HTTP method** as `POST`.
-6. (Optional) Adjust the **payload/template** only if you have customized parsing on the OpsiMate side; otherwise, use the default JSON payload from Uptime Kuma.
-7. Save the notification.
-8. Attach this notification to the monitors you want to forward to OpsiMate.
-
-## Important Disclaimer
-
-Uptime Kuma sends webhooks to **publicly reachable HTTP endpoints**.
-
-- If you are running OpsiMate locally (for example at `http://localhost:3001`), Uptime Kuma running on a different machine or in the cloud may **not** be able to call this URL directly.
-- For production use, deploy OpsiMate behind a **reachable URL** (or expose it securely via tunneling / reverse proxy) so that Uptime Kuma can reach the webhook endpoint.
-
-Once configured, alerts pushed from Uptime Kuma will appear in the **alerts table** in OpsiMate with the **Uptime Kuma integration icon**, so you can easily identify their source.
diff --git a/opsimate-docs/docs/integrations/uptime-kuma.mdx b/opsimate-docs/docs/integrations/uptime-kuma.mdx
new file mode 100644
index 0000000..0c5047b
--- /dev/null
+++ b/opsimate-docs/docs/integrations/uptime-kuma.mdx
@@ -0,0 +1,73 @@
+---
+id: uptime-kuma
+title: Uptime Kuma Integration
+slug: /integrations/uptime-kuma
+sidebar_label: Uptime Kuma Integration
+sidebar_position: 4
+tags: [Alerts]
+---
+
+# Uptime Kuma Integration
+
+The **Uptime Kuma integration** lets you send alerts from **Uptime Kuma** into OpsiMate using webhook-based push notifications.
+
+Instead of OpsiMate pulling status from Uptime Kuma, your Uptime Kuma notifications push alerts directly to OpsiMate.
+
+## Webhook URL
+
+Configure your Uptime Kuma notification to send alerts to your OpsiMate server.
+
+Use your OpsiMate alerts webhook endpoint, for example:
+
+```text
+/api/v1/alerts/custom/uptime-kuma?api_token={your_api_token}
+```
+
+> Replace `{your_api_token}` with the API token configured in your OpsiMate server.
+
+The exact path segment (for example `uptime-kuma`) should match how the Uptime Kuma integration is configured in your OpsiMate backend.
+
+## API Token Configuration
+
+The API token used in the webhook URL is managed by OpsiMate through an environment variable:
+
+- **Env var:** `API_TOKEN`
+- **Default value:** `opsimate`
+
+This value is also used as the default for the `api_token` query parameter in the webhook URL.
+
+If you are using the simple deployment (via the provided `docker-compose.yml`), the `API_TOKEN` environment variable is already defined there for you.
+
+Make sure your OpsiMate server is started with `API_TOKEN` set (or rely on the default), and use the same value in the Uptime Kuma webhook URL.
+
+## Setting Up the Webhook in Uptime Kuma
+
+To send alerts from Uptime Kuma to OpsiMate via webhook:
+
+1. In **Uptime Kuma**, go to **Settings → Notifications**.
+2. Click **Add New Notification**.
+3. Choose **Webhook** as the notification type.
+4. Set the URL to your OpsiMate endpoint, for example:
+
+```text
+http://your-opsimate-host/api/v1/alerts/custom/uptime-kuma?api_token={your_api_token}
+```
+
+5. Keep the HTTP method as **POST**.
+6. *(Optional)* Adjust the payload/template only if you have customized parsing on the OpsiMate side; otherwise, use the default JSON payload from Uptime Kuma.
+7. Save the notification.
+8. Attach this notification to the monitors you want to forward to OpsiMate.
+
+## Important Disclaimer
+
+Uptime Kuma sends webhooks **only to publicly reachable HTTP endpoints**.
+
+- If you are running OpsiMate locally (for example at ``), Uptime Kuma running on a different machine or in the cloud may not be able to call this URL directly.
+- For production use, deploy OpsiMate behind a publicly reachable URL (or expose it securely via tunneling / reverse proxy) so that Uptime Kuma can reach the webhook endpoint.
+
+Once configured, alerts pushed from Uptime Kuma will appear in the **alerts table** in OpsiMate with the **Uptime Kuma integration icon**, so you can easily identify their source.
+
+
+
+
+
diff --git a/opsimate-docs/docs/integrations/zabbix.md b/opsimate-docs/docs/integrations/zabbix.mdx
similarity index 97%
rename from opsimate-docs/docs/integrations/zabbix.md
rename to opsimate-docs/docs/integrations/zabbix.mdx
index 7f063f8..ee0b048 100644
--- a/opsimate-docs/docs/integrations/zabbix.md
+++ b/opsimate-docs/docs/integrations/zabbix.mdx
@@ -1,8 +1,13 @@
---
+id: zabbix
+title: Zabbix Integration
+slug: /integrations/zabbix
+sidebar_label: Zabbix Integration
sidebar_position: 6
tags: [Alerts]
---
+
# Zabbix Integration
The **Zabbix integration** lets you send alerts from Zabbix into OpsiMate using **webhook-based push notifications**.
@@ -113,7 +118,7 @@ Add the following parameters in the **Parameters** section of the media type:
| `zabbix_url` | `https://your-zabbix-server.com` |
| `trigger_url` | `{TRIGGER.URL}` |
-:::important
+:::caution
Set `zabbix_url` to your actual Zabbix server URL so alerts in OpsiMate can link back to Zabbix.
:::
diff --git a/opsimate-docs/sidebars.js b/opsimate-docs/sidebars.js
index f0abd3c..48ba719 100644
--- a/opsimate-docs/sidebars.js
+++ b/opsimate-docs/sidebars.js
@@ -1,32 +1,52 @@
-/**
- * Creating a sidebar enables you to:
- - create an ordered group of docs
- - render a sidebar for each doc of that group
- - provide next/previous navigation
-
- The sidebars can be generated from the filesystem, or explicitly defined here.
-
- Create as many sidebars as you want.
- */
-
+// sidebars.js
// @ts-check
/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
const sidebars = {
tutorialSidebar: [
- 'intro',
- 'core-features',
+ // Getting Started
{
type: 'category',
label: 'Getting Started',
+ collapsed: false,
+ items: [
+ 'getting-started/introduction',
+ 'getting-started/quick-start',
+ ],
+ },
+
+ // Providers & Services
+ {
+ type: 'category',
+ label: 'Providers & Services',
collapsed: true,
items: [
- 'getting-started/deploy',
- 'getting-started/configuration',
- 'getting-started/system-requirements',
+ 'providers-services/overview',
+ {
+ type: 'category',
+ label: 'Providers',
+ collapsed: true,
+ items: [
+ 'providers-services/providers/add-provider',
+ 'providers-services/providers/server-provider',
+ 'providers-services/providers/kubernetes-provider',
+ ],
+ },
+ {
+ type: 'category',
+ label: 'Services',
+ collapsed: true,
+ items: [
+ 'providers-services/services/add-services',
+ 'providers-services/services/container-services',
+ 'providers-services/services/systemd-services',
+ 'providers-services/services/kubernetes-pods',
+ ],
+ },
],
},
+ // Integrations
{
type: 'category',
label: 'Integrations',
@@ -34,34 +54,55 @@ const sidebars = {
items: [
'integrations/overview',
'integrations/grafana',
+ 'integrations/datadog',
'integrations/gcp',
'integrations/uptime-kuma',
- 'integrations/datadog',
'integrations/zabbix',
],
},
+
+ // Dashboards
{
type: 'category',
- label: 'Dashboard',
+ label: 'Dashboards',
collapsed: true,
items: [
'dashboards/saved-dashboards',
],
},
+
+ // Alerts
{
type: 'category',
label: 'Alerts',
collapsed: true,
- items: ['alerts/adding-alerts', 'alerts/alert-management', 'alerts/archived-alerts', 'alerts/tv-mode'],
+ items: [
+ 'alerts/adding-alerts',
+ 'alerts/alert-management',
+ 'alerts/archived-alerts',
+ 'alerts/tv-mode-view',
+ ],
},
+
+ // User Management
{
type: 'category',
- label: 'User Management & Security',
+ label: 'User Management',
collapsed: true,
- items: ['user-management/register-login', 'user-management/admin-panel', 'user-management/audit-logs'],
+ items: [
+ 'user-management/register-login',
+ 'user-management/admin-panel',
+ 'user-management/audit-logs',
+ ],
},
+
+ // Single-page sections (not collapsible)
'development',
+ 'contributing/index',
+ 'glossary/index',
+ 'faq/index',
+ 'legal/privacy',
],
};
-module.exports = sidebars;
+module.exports = sidebars;
\ No newline at end of file
diff --git a/opsimate-docs/src/css/custom.css b/opsimate-docs/src/css/custom.css
index 6daa98e..7017221 100644
--- a/opsimate-docs/src/css/custom.css
+++ b/opsimate-docs/src/css/custom.css
@@ -879,3 +879,6 @@ button[class*="toggle"] {
}
+
+
+