Add linter (#376)

* chore: add prettier

* format

# Conflicts:
#	docs/dev/web/embed-mode.md
#	docs/dev/web/extension-system/extension-types/action-extensions.md
#	docs/dev/web/extension-system/extension-types/app-menu-item-extensions.md
#	docs/dev/web/extension-system/extension-types/custom-component-extensions.md
#	docs/dev/web/extension-system/extension-types/folder-view-extensions.md
#	docs/dev/web/extension-system/extension-types/right-sidebar-panel-extensions.md
#	docs/dev/web/extension-system/extension-types/search-extensions.md
#	docs/dev/web/extension-system/viewer-editor-apps.md
#	docs/dev/web/testing/e2e-testing-standards.md
#	prettier.config.js

* use ;

* use single quotes as its as well docusaurus default

* chore: add linter

# Conflicts:
#	package.json
#	pnpm-lock.yaml

* ignore some rules

* add to ci

* ignore md003

* ignore .git

* use ordere lists

* run linter

* fix links

* update lockfile

* run formatter

* remove from woodpecker

Author: AlexAndBear

.markdownlint-cli2.jsonc

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://raw.githubusercontent.com/DavidAnson/markdownlint-cli2/main/schema/markdownlint-cli2-config-schema.json",
+  "config": ".markdownlint.json",
+  "ignores": [
+    ".git",
+    "node_modules",
+    "static",
+    "assets",
+    "CHANGELOG.md",
+    "CONTRIBUTING.md",
+    "README.md"
+  ]
+}

.markdownlint.json

@@ -0,0 +1,7 @@
+{
+  "default": true,
+  "MD003": false, // Disable MD003 to allow different heading styles
+  "MD013": false, // Disable MD013 to allow long lines
+  "MD033": false, // Disable MD033 to allow inline HTML
+  "MD029": { "style": "ordered" } // Ensure ordered lists are used
+}

docs/admin/configuration/logging.md

@@ -18,7 +18,7 @@ Logging helps monitor OpenCloud’s health and diagnose issues. Log output varie
 
 Set the global log level using the `OPEN_CLOUD_LOG_LEVEL` environment variable. You can also override it per service using service-specific variables. Default is `error`.
 
-## The log levels are:
+## The log levels are
 
 ### FATAL
 

docs/admin/configuration/mail-notifications.md

@@ -7,7 +7,7 @@ description: 'How to activate mail notifications in OpenCloud.'
 
 # Mail notifications in OpenCloud
 
-## This guide shows how to configure your OpenCloud instance to send notification E-Mails by modifying the `.env` file in your OpenCloud setup.
+## This guide shows how to configure your OpenCloud instance to send notification E-Mails by modifying the `.env` file in your OpenCloud setup
 
 ---
 

docs/admin/getting-started/container/docker-compose-local.md

@@ -29,21 +29,21 @@ git clone https://github.com/opencloud-eu/opencloud-compose.git
 
 ## 2. Start
 
-### cd into the Docker Compose configuration folder:
+### cd into the Docker Compose configuration folder
 
 ```Shell
 cd opencloud-compose
 ```
 
-### Create environment file:
+### Create environment file
 
 ```Shell
 cp .env.example .env
 ```
 
 > **Note:** The repository includes .env.example as a template with default settings and documentation. Your actual .env file is excluded from version control (via .gitignore) to prevent accidentally committing sensitive information like passwords and domain-specific settings.
 
-### Configure deployment options:
+### Configure deployment options
 
 You can deploy using explicit -f flags:
 

docs/admin/getting-started/container/docker-compose/docker-compose.md

@@ -193,7 +193,7 @@ Example with Chrome browser:
 
 Once the staging certificate works, switch to a production certificate.
 
-### Steps:
+### Steps
 
 #### 1️⃣ Stop Docker Compose
 
@@ -257,7 +257,7 @@ If you encounter any issues, check the [Common Issues & Help](./../../../resourc
 
 <br/>
 
-#### To enable Keycloak for identity and access management, **uncomment** the following lines in your `.env` file:
+#### To enable Keycloak for identity and access management, **uncomment** the following lines in your `.env` file
 
 ```env
 LDAP=:ldap.yml
@@ -271,15 +271,15 @@ KEYCLOAK_ADMIN_PASSWORD="your.save.password"
 
 This will include the LDAP and Keycloak service definitions in the Docker Compose setup.
 
-#### After starting OpenCloud, Keycloak will be available at:
+#### After starting OpenCloud, Keycloak will be available at
 
 ```bash
 https://keycloak.your.domain
 ```
 
 ## 👤 Initial User Setup in Keycloak
 
-### Once Keycloak is running:
+### Once Keycloak is running
 
 **1. Open your browser and go to**
 

docs/admin/getting-started/container/docker.md

@@ -7,7 +7,7 @@ description: 'Classic docker setup.'
 
 # Docker
 
-## Spin up a temporary local instance of OpenCloud using **Docker**.
+## Spin up a temporary local instance of OpenCloud using **Docker**
 
 ---
 

docs/admin/getting-started/other/bare-metal.md

@@ -21,9 +21,11 @@ Bare-metal deployments are not officially supported by OpenCloud. They are great
 - Open a terminal.
 
 - Update your package list:
+
   ```bash
   sudo apt update && apt upgrade
   ```
+
 - Install Git using the following command:
 
   ```bash
@@ -33,9 +35,11 @@ Bare-metal deployments are not officially supported by OpenCloud. They are great
   <img src={require("./../img/bare-metal/install-git.png").default} alt="install git" width="1920"/>
 
 - Clone the OpenCloud repository:
+
   ```bash
   git clone https://github.com/opencloud-eu/opencloud.git
   ```
+
   <img src={require("./../img/bare-metal/git-clone.png").default} alt="git clone" width="1920"/>
 
 ---
@@ -61,20 +65,25 @@ Bare-metal deployments are not officially supported by OpenCloud. They are great
   <img src={require("./../img/bare-metal/install-corepack.png").default} alt="install corepack" width="1920"/>
 
 - Enable `pnpm` using corepack:
+
   ```bash
   corepack enable pnpm
   ```
+
   <img src={require("./../img/bare-metal/corepack-enable.png").default} alt="corepack enable" width="1920"/>
 
 ---
 
 ### 3. Build process and OpenCloud initialization
 
 - Navigate to the OpenCloud directory:
+
   ```bash
   cd opencloud
   ```
+
   <img src={require("./../img/bare-metal/cd-opencloud.png").default} alt="cd opencloud" width="1920"/>
+
 - Run the build generate process:
 
   ```bash
@@ -91,9 +100,11 @@ Bare-metal deployments are not officially supported by OpenCloud. They are great
   <img src={require("./../img/bare-metal/opencloud-init.png").default} alt="opencloud init" width="1920"/>
 
 - Start the OpenCloud server:
+
   ```bash
   ./bin/opencloud server
   ```
+
   <img src={require("./../img/bare-metal/opencloud-server.png").default} alt="opencloud server" width="1920"/>
 
 ---
@@ -116,6 +127,6 @@ Your OpenCloud server is now running and ready to use 🚀
 
 ---
 
-### If you encounter any issues or errors, try finding a solution here:
+### If you encounter any issues or errors, try finding a solution here
 
 - [Common Issues & Help](./../../resources/common-issues.md)

docs/admin/getting-started/other/raspberry-pi.md

@@ -34,7 +34,7 @@ The IP for this can be viewed in your router.
 
 <img src={require("./../img/raspberrypi/ip-router.png").default} alt="find ip from raspberry-pi in router" width="500"/>
 
-#### Establish connection via SSH:
+#### Establish connection via SSH
 
 ```sh
 ssh pi@YOUR-IP

docs/admin/maintenance/backup.md

@@ -4,13 +4,13 @@ id: backup
 title: 'Backup'
 ---
 
-## Regular backups are essential to ensure that your OpenCloud instance can be restored in case of issues.
+## Regular backups are essential to ensure that your OpenCloud instance can be restored in case of issues
 
 ---
 
 ### General considerations
 
-#### OpenCloud supports two different storage setups:
+#### OpenCloud supports two different storage setups
 
 - Pure POSIX Setup: All data (configuration, blobs, and metadata) is stored on a POSIX-compliant filesystem.
 
@@ -22,7 +22,7 @@ To determine which filesystems are supported, see: Filesystems and Shared Storag
 
 ### Backup strategies
 
-#### To create a consistent backup, the OpenCloud instance must be stopped before starting the backup process. After the backup is complete, the instance can be restarted.
+#### To create a consistent backup, the OpenCloud instance must be stopped before starting the backup process. After the backup is complete, the instance can be restarted
 
 **There are two recommended approaches:**
 
@@ -41,7 +41,7 @@ To determine which filesystems are supported, see: Filesystems and Shared Storag
 
 ### Required backup components
 
-#### A complete backup must include:
+#### A complete backup must include
 
 - Configuration data
 
@@ -65,7 +65,7 @@ To determine which filesystems are supported, see: Filesystems and Shared Storag
 
 ### Pure POSIX setup
 
-#### If all data (configuration, blobs, and metadata) is stored on a POSIX-compliant filesystem:
+#### If all data (configuration, blobs, and metadata) is stored on a POSIX-compliant filesystem
 
 - Stop the OpenCloud instance
 
@@ -81,7 +81,7 @@ To determine which filesystems are supported, see: Filesystems and Shared Storag
 
 ### Distributed setup
 
-#### If blobs are stored on S3, while configuration and metadata remain on a POSIX-compliant filesystem:
+#### If blobs are stored on S3, while configuration and metadata remain on a POSIX-compliant filesystem
 
 - Stop the OpenCloud instance
 
@@ -93,4 +93,4 @@ To determine which filesystems are supported, see: Filesystems and Shared Storag
 
 ---
 
-#### With these backup strategies, you can ensure that your OpenCloud instance remains secure and restorable in case of issues!
+#### With these backup strategies, you can ensure that your OpenCloud instance remains secure and restorable in case of issues