chore: moved all operations

Jelledb · Jelledb · commit 5110384b0cd4 · 2025-08-26T17:30:28.000Z
diff --git a/amplify/main.tf b/amplify/main.tf
@@ -355,7 +355,7 @@ locals {
     # },
     # {
     #   source = "/security-faq"
-    #   target = "/security-faq"
+    #   target = "/operations/security-faq"
     # },
     # {
     #   source = "/copilot-preview"
diff --git a/docs/concepts/copilot.md b/docs/concepts/copilot.md
@@ -48,7 +48,7 @@ When using meshStack Copilot, please keep in mind:
 
 ### Which AI model providers do you use for Copilot?
 
-meshStack Copilot currently uses Google Gemini models hosted by Google Cloud in the EU. This means your questions are processed by Google Cloud, acting as a subprocessor of meshcloud. For more details, see our official subprocessor list in the [Security FAQ](security-faq.md).
+meshStack Copilot currently uses Google Gemini models hosted by Google Cloud in the EU. This means your questions are processed by Google Cloud, acting as a subprocessor of meshcloud. For more details, see our official subprocessor list in the [Security FAQ](operations/security-faq.md).
 
 We're curious to hear if you’d like to see “bring your own model” (or API key) support so you can use meshStack Copilot with models under your own contract.
 
@@ -96,7 +96,7 @@ All conversations with meshStack Copilot, including all data provided to the mod
 ### Concepts
 
 - [Copilot](concepts/copilot.md)
-- [Security FAQ](security-faq.md)
+- [Security FAQ](operations/security-faq.md)
 
 ### Guides
 
diff --git a/docs/concepts/identity-and-access-management.md b/docs/concepts/identity-and-access-management.md
@@ -126,7 +126,7 @@ meshStack supports the following identity provisioning strategies:
 | :-----------: | :------------------------------------------------------------: | :------------------------------------------------------------------------: |
 |   OpenStack   |                               -                                |   [supported](integrations/openstack/index.md#access-control-integration)   |
 | Cloud Foundry |                                                                | [supported](integrations/cloud-foundry/index.md#uaa-configuration)             |
-|  Kubernetes   |                               -                                |  [supported](meshstack.kubernetes.index.md#access-control-integration)   |
+|  Kubernetes   |                               -                                |  [supported](integrations/kubernetes/index.md#access-control-integration)   |
 |   OpenShift   |                               -                                |       [supported](integrations/openshift/index.md#idp-configuration)        |
 |      AWS      |   [deprecated](/integrations/aws/index.md#meshidb-deprecated)    |               [supported](/integrations/aws/index.md#aws-sso)                |
 |     Azure     |   [AAD B2B](integrations/azure/index#workload-aad-tenant)    | [supported](integrations/azure/index#azure-active-directory-integration) |
diff --git a/docs/guides/core/how-to-kickstart-your-IDP.md b/docs/guides/core/how-to-kickstart-your-IDP.md
@@ -46,5 +46,5 @@ importing a Building Block Definition from the meshStack Hub and making it avail
 
 ### Concepts
 
-- [Building Block](concepts/building-block.md)
+- [Building Block](../../concepts/building-block.md)
 - [meshStack Hub](https://hub.meshcloud.io)
diff --git a/docs/guides/core/how-to-manage-a-tenant.md b/docs/guides/core/how-to-manage-a-tenant.md
@@ -12,7 +12,7 @@ This guide helps you manage tenants in meshStack. You'll learn how to keep your
 ### Prerequisites
 
 - Have an admin user that can log into meshStack.
-- For AWS account import, refer to the [AWS Integration Guide Step 11](integrations/aws/how-to-integrate.md) for detailed instructions.
+- For AWS account import, refer to the [AWS Integration Guide Step 11](../../integrations/aws/how-to-integrate.md) for detailed instructions.
 
 ### Step by Step Guide
 
diff --git a/docs/integrations/openshift/index.md b/docs/integrations/openshift/index.md
@@ -3,7 +3,7 @@ id: index
 title: Integration
 ---
 
-meshStack supports management of RedHat OpenShift platforms. OpenShift has a [Kubernetes](meshstack.kubernetes.index.md) core and provides additional services. It is available in both Open Source flavors (OKD) as well as enterprise offerings by RedHat.
+meshStack supports management of RedHat OpenShift platforms. OpenShift has a [Kubernetes](integrations/kubernetes/index.md) core and provides additional services. It is available in both Open Source flavors (OKD) as well as enterprise offerings by RedHat.
 
 meshStack supports project creation, configuration, access control, quota management and billing for OpenShift.
 
diff --git a/docs/integrations/openstack/index.md b/docs/integrations/openstack/index.md
@@ -19,7 +19,7 @@ The latest OpenStack release officially validated with meshStack is [OpenStack 2
 However, any later OpenStack releases that continues to maintain API compatibility with the API versions specified below is supported.
 
 > As OpenStack is typically deployed "behind the firewall" in a private cloud settings, you may consider using an on-prem deployment of
-> [meshStack Enterprise](meshstack.managed-service.md). This enables meshStack to safely connect to your OpenStack APIs on your private network.
+> [meshStack Enterprise](operations/managed-service.md). This enables meshStack to safely connect to your OpenStack APIs on your private network.
 
 ### Supported OpenStack Versions
 
diff --git a/docs/operations/backup.md b/docs/operations/backup.md
@@ -1,5 +1,5 @@
 ---
-id: meshstack.backup
+id: backup
 title: Backup
 ---
 
diff --git a/docs/operations/dns.md b/docs/operations/dns.md
@@ -1,5 +1,5 @@
 ---
-id: administration.dns
+id: dns
 title: "DNS and SSL Certificates"
 ---
 
@@ -25,7 +25,7 @@ The DNS records needed for those domains are provided to you by meshcloud during
 
 ## SSL certificates
 
-> Providing SSL certificates is only required for [meshStack Enterprise](meshstack.managed-service.md#meshstack-saas-on-prem). For [meshStack SaaS](meshstack.managed-service.md#meshstack-saas) manages SSL certificates automatically.
+> Providing SSL certificates is only required for [meshStack Enterprise](operations/managed-service.md#meshstack-saas-on-prem). For [meshStack SaaS](operations/managed-service.md#meshstack-saas) manages SSL certificates automatically.
 
 meshStack supports wildcard certificates and certificates with Subject Alternative Name (SAN).
 SAN certificates need to contain FQDN for all hosts.
diff --git a/docs/operations/email.md b/docs/operations/email.md
@@ -1,5 +1,5 @@
 ---
-id: meshstack.email
+id: email
 title: Email
 ---
  
diff --git a/docs/operations/logging.md b/docs/operations/logging.md
@@ -1,5 +1,5 @@
 ---
-id: meshstack.logging
+id: logging
 title: Logging & Auditing
 ---
 
diff --git a/docs/operations/managed-service.md b/docs/operations/managed-service.md
@@ -1,5 +1,5 @@
 ---
-id: meshstack.managed-service
+id: managed-service
 title: Managed Service
 ---
 
@@ -69,8 +69,8 @@ frameworks such as ISO 27001 and ISO 27017.
 
 ### Monitoring and Support
 
-Every meshStack installation includes sophisticated [logging](meshstack.logging.md)
-and [monitoring](meshstack.monitoring.md) infrastructure. meshcloud uses these tools
+Every meshStack installation includes sophisticated [logging](operations/logging.md)
+and [monitoring](operations/monitoring.md) infrastructure. meshcloud uses these tools
 to monitor system availability and diagnose any possible issues.
 
 The monitoring infrastructure of your installations can be made available to your own operations teams on request.
diff --git a/docs/operations/monitoring.md b/docs/operations/monitoring.md
@@ -1,12 +1,12 @@
 ---
-id: meshstack.monitoring
+id: monitoring
 title: Monitoring & Telemetry
 ---
 
-Our [managed service](meshstack.managed-service.md) team
+Our [managed service](operations/managed-service.md) team
 relies on monitoring & telemetry to operate meshStack installations for our customers. The integration of these systems are a mandatory pre-requisite for using our managed services.
 
-This page documents what data we collect and for what purposes we process it. All customer data we collect and store is handled with confidentiality in accordance with our information security management system as described in our [Security FAQ](security-faq.md).
+This page documents what data we collect and for what purposes we process it. All customer data we collect and store is handled with confidentiality in accordance with our information security management system as described in our [Security FAQ](operations/security-faq.md).
 
 ## Customer data
 
@@ -24,7 +24,7 @@ Application-level metrics can contain labels that include customer data such as
 
 ## Logs
 
-meshStack collects various logs as described in [Logging & Auditing](meshstack.logging.md). Logs can contain customer data and also PII like user identifiers.
+meshStack collects various logs as described in [Logging & Auditing](operations/logging.md). Logs can contain customer data and also PII like user identifiers.
 
 Log data is therefore not part of telemetry data we collect.
 
@@ -34,7 +34,7 @@ meshcloud transmits and processes metrics data to a central monitoring system op
 
 Customers can find more details including a full list of metrics transmitted in meshStack's security documentation.
 
-When enabled, collected [product feedback and usage data](administration.product-feedback-collection.md) is relayed from meshPanel's web server to a central plausible server instance operated by meshcloud.
+When enabled, collected [product feedback and usage data](operations/product-feedback-collection.md) is relayed from meshPanel's web server to a central plausible server instance operated by meshcloud.
 
 ## Health endpoint
 
diff --git a/docs/operations/product-feedback-collection.md b/docs/operations/product-feedback-collection.md
@@ -1,5 +1,5 @@
 ---
-id: administration.product-feedback-collection
+id: product-feedback-collection
 title: Product Feedback Collection
 ---
 
diff --git a/docs/operations/security-faq.md b/docs/operations/security-faq.md
diff --git a/docs/settings/identity-lookup.md b/docs/settings/identity-lookup.md
@@ -3,7 +3,7 @@ id: identity-lookup
 title: Identity Lookup
 ---
 
-> The recommended way to set up [user provisioning via SCIM](settings/user-group-provisioning). The instructions below are not needed if users are provisioned via SCIM.
+> The recommended way to set up [user provisioning via SCIM](/settings/user-group-provisioning). The instructions below are not needed if users are provisioned via SCIM.
 
 meshStack allows Workspace Managers to [quickly onboard team members](/concepts/workspace#invite-users-to-a-meshworkspace-team) with an assisted onboarding workflow.
 This onboarding workflow features an autocomplete and search for user identities in an enterprise user directory. We call this search process identity lookup.
diff --git a/sidebars.ts b/sidebars.ts
@@ -225,14 +225,14 @@ const sidebars: SidebarsConfig = {
       collapsible: true,
       collapsed: true,
       items: [
-        'meshstack.managed-service',
-        'meshstack.email',
-        'meshstack.logging',
-        'meshstack.monitoring',
-        'meshstack.backup',
-        'security-faq',
-        'administration.dns',
-        'administration.product-feedback-collection'
+        'operations/managed-service',
+        'operations/email',
+        'operations/logging',
+        'operations/monitoring',
+        'operations/backup',
+        'operations/security-faq',
+        'operations/dns',
+        'operations/product-feedback-collection'
       ],
     },
     {
