docs: move code blocks outside list items for MkDocs compatibility

Author: edmondas

docs/configuration/ui/custom-css.md

@@ -15,23 +15,16 @@ Each theme includes support for custom CSS extension files that are automaticall
 
 ## Quick Start
 
-1. Navigate to your theme's style directory:
-
-    ```
-    templates/default/style/
-    ```
-
-2. Copy the example files:
-
-    ```bash
-    cp custom_light.css.example custom_light.css
-    cp custom_dark.css.example custom_dark.css
-    ```
-
+1. Navigate to your theme's style directory: `templates/default/style/`
+2. Copy the example files (see below)
 3. Edit the CSS files to match your preferences
-
 4. Refresh your browser - custom styles are automatically loaded
 
+```bash
+cp custom_light.css.example custom_light.css
+cp custom_dark.css.example custom_dark.css
+```
+
 ## How It Works
 
 | File | Description |

docs/configuration/ui/layout.md

@@ -25,17 +25,16 @@ return [
 
 ### Creating Custom Templates
 
-1. Create a directory structure for your custom theme:
+1. Create a directory structure for your custom theme (see below)
+2. Create the following files (see sections below)
 
-    ```
-    templates/
-    └── custom/
-        ├── header.html
-        ├── footer.html
-        └── other template files...
-    ```
-
-2. Create the following files:
+```
+templates/
+└── custom/
+    ├── header.html
+    ├── footer.html
+    └── other template files...
+```
 
 #### Custom Header (templates/custom/header.html)
 

docs/configuration/ui/themes.md

@@ -47,18 +47,17 @@ Each theme includes consistent styling for:
 Poweradmin supports custom themes through the theme templates system. To create a custom theme:
 
 1. Set the theme to `custom` in your settings
-2. Create a directory structure in your theme base path:
-
-    ```
-    templates/
-    └── custom/
-        ├── header.html
-        ├── footer.html
-        └── other template files...
-    ```
-
+2. Create a directory structure in your theme base path (see below)
 3. Customize the template files to match your organization's branding
 
+```
+templates/
+└── custom/
+    ├── header.html
+    ├── footer.html
+    └── other template files...
+```
+
 ## Theme Customization
 
 For more information on customizing themes, see:

docs/contributing/development.md

@@ -10,23 +10,25 @@
 - PowerDNS server (for testing)
 
 ### Installation for Development
-1. Clone the repository
 
-    ```
-    git clone https://github.com/poweradmin/poweradmin.git
-    cd poweradmin
-    ```
+**1. Clone the repository:**
 
-2. Install dependencies
+```
+git clone https://github.com/poweradmin/poweradmin.git
+cd poweradmin
+```
+
+**2. Install dependencies:**
 
-    ```
-    composer install
-    npm install
-    ```
+```
+composer install
+npm install
+```
 
-3. Configure the application
-   - Copy `config/settings.defaults.php` to a new file in the same directory
-   - Modify the settings according to your environment
+**3. Configure the application:**
+
+- Copy `config/settings.defaults.php` to a new file in the same directory
+- Modify the settings according to your environment
 
 ## Project Structure
 
@@ -74,13 +76,14 @@ Poweradmin has comprehensive testing support including unit tests, integration t
 Poweradmin follows PSR-12 with project-specific modifications. For detailed information on coding standards, tools for code quality, and how to enforce them, see the [Coding Standards Guide](coding-standards.md).
 
 ## Database Migrations
+
 - Database migrations are managed with Phinx
 - See `db/migrations/` for existing migrations
 - Create new migrations with:
 
-    ```
-    ./vendor/bin/phinx create MyNewMigration
-    ```
+```
+./vendor/bin/phinx create MyNewMigration
+```
 
 ## Contributing
 1. Fork the repository

docs/installation/centos.md

@@ -29,71 +29,71 @@ dnf install -y php-sqlite3
 
 ### Apache
 
-1. Install Apache if not already installed:
+**1. Install Apache if not already installed:**
 
-    ```bash
-    dnf install -y httpd
-    ```
+```bash
+dnf install -y httpd
+```
 
-2. Enable and start the Apache service:
+**2. Enable and start the Apache service:**
 
-    ```bash
-    systemctl enable httpd
-    systemctl start httpd
-    ```
+```bash
+systemctl enable httpd
+systemctl start httpd
+```
 
-3. Configure SELinux if it's enabled:
+**3. Configure SELinux if it's enabled:**
 
-    ```bash
-    # Allow Apache to connect to the database
-    setsebool -P httpd_can_network_connect_db 1
+```bash
+# Allow Apache to connect to the database
+setsebool -P httpd_can_network_connect_db 1
 
-    # If using a non-standard directory, set the correct context
-    semanage fcontext -a -t httpd_sys_content_t "/path/to/poweradmin(/.*)?"
-    restorecon -Rv /path/to/poweradmin
-    ```
+# If using a non-standard directory, set the correct context
+semanage fcontext -a -t httpd_sys_content_t "/path/to/poweradmin(/.*)?"
+restorecon -Rv /path/to/poweradmin
+```
 
-4. Configure your firewall:
+**4. Configure your firewall:**
 
-    ```bash
-    firewall-cmd --permanent --add-service=http
-    firewall-cmd --permanent --add-service=https  # If using HTTPS
-    firewall-cmd --reload
-    ```
+```bash
+firewall-cmd --permanent --add-service=http
+firewall-cmd --permanent --add-service=https  # If using HTTPS
+firewall-cmd --reload
+```
 
-5. Ensure `AllowOverride All` is set in your Apache configuration to allow the `.htaccess` file to function properly. The `.htaccess` file handles URL routing, API support, and security rules automatically.
+**5.** Ensure `AllowOverride All` is set in your Apache configuration to allow the `.htaccess` file to function properly. The `.htaccess` file handles URL routing, API support, and security rules automatically.
 
 ### Nginx Configuration
 
 If you prefer Nginx, use the configuration example provided in the Poweradmin repository. The configuration includes API routing, CORS support, security rules, and clean URL handling.
 
-1. Install Nginx:
+**1. Install Nginx:**
 
-    ```bash
-    dnf install -y nginx
-    ```
+```bash
+dnf install -y nginx
+```
 
-2. Download the appropriate configuration file:
+**2.** Download the appropriate configuration file:
 
 **Version-specific configuration files:**
 
 - **Poweradmin 4.0.x**: Use [nginx.conf.example from release/4.x](https://github.com/poweradmin/poweradmin/blob/release/4.x/nginx.conf.example)
 - **Poweradmin 4.1.x+**: Use [nginx.conf.example from master](https://github.com/poweradmin/poweradmin/blob/master/nginx.conf.example) (includes subfolder deployment support)
 
-3. Save the configuration to `/etc/nginx/conf.d/poweradmin.conf` and adjust:
+**3.** Save the configuration to `/etc/nginx/conf.d/poweradmin.conf` and adjust:
 
 - `server_name` - Set to your domain name
 - `root` - Set to your Poweradmin installation path
 - `fastcgi_pass` - Use `unix:/var/run/php-fpm/www.sock` for RHEL/CentOS
 
-4. Enable and start Nginx and PHP-FPM:
+**4. Enable and start Nginx and PHP-FPM:**
 
-    ```bash
-    systemctl enable nginx php-fpm
-    systemctl start nginx php-fpm
-    ```
+```bash
+systemctl enable nginx php-fpm
+systemctl start nginx php-fpm
+```
 
-5. Configure SELinux and firewall as with Apache.
+**5.** Configure SELinux and firewall as with Apache.
 
 ### Caddy Configuration
 

docs/installation/docker-secrets.md

@@ -174,26 +174,26 @@ EOF
 
 ## Security Best Practices
 
-1. **File permissions**: Set restrictive permissions on secret files
+**1. File permissions:** Set restrictive permissions on secret files:
 
 ```bash
 chmod 600 ./secrets/*
 ```
 
-2. **Read-only mounts**: Mount secrets as read-only
+**2. Read-only mounts:** Mount secrets as read-only:
 
-    ```yaml
-    volumes:
-      - ./secrets/db_password.txt:/run/secrets/db_password:ro
-    ```
+```yaml
+volumes:
+  - ./secrets/db_password.txt:/run/secrets/db_password:ro
+```
 
-3. **Exclude from version control**: Add secrets to `.gitignore`
+**3. Exclude from version control:** Add secrets to `.gitignore`:
 
-    ```
-    secrets/
-    *.key
-    *.pem
-    ```
+```
+secrets/
+*.key
+*.pem
+```
 
 4. **Use external secrets in production**: For Swarm deployments, use external secrets managed outside of compose files
 

docs/installation/remote-setup-guide.md

@@ -92,16 +92,16 @@ PRIVILEGES;
 
 For DNSSEC management and certain operations, Poweradmin requires access to the PowerDNS API:
 
-1. Enable the API on your PowerDNS server by editing `/etc/powerdns/pdns.conf`:
-
-    ```
-    api=yes
-    api-key=your_secure_api_key
-    webserver=yes
-    webserver-address=0.0.0.0  # Or restrict to admin_server_ip
-    webserver-port=8081
-    webserver-allow-from=admin_server_ip/32
-    ```
+**1.** Enable the API on your PowerDNS server by editing `/etc/powerdns/pdns.conf`:
+
+```
+api=yes
+api-key=your_secure_api_key
+webserver=yes
+webserver-address=0.0.0.0  # Or restrict to admin_server_ip
+webserver-port=8081
+webserver-allow-from=admin_server_ip/32
+```
 
 2. Configure Poweradmin to use the API by editing your `settings.php`:
 

docs/upgrading/v4.0.0.md

@@ -47,14 +47,14 @@ After successfully running the migration script and verifying your new configura
    - Keep this backup temporarily while testing
    - Delete it once you're confident everything works: `rm inc/config.inc.php.bak`
 
-2. **If you kept the original file (answered "n"):**
-
-    ```bash
-    # Backup and remove the old config
-    mv inc/config.inc.php inc/config.inc.php.backup
-    # Store it safely outside the web root
-    mv inc/config.inc.php.backup ~/poweradmin-backups/config.inc.php.$(date +%Y%m%d)
-    ```
+**If you kept the original file (answered "n"):**
+
+```bash
+# Backup and remove the old config
+mv inc/config.inc.php inc/config.inc.php.backup
+# Store it safely outside the web root
+mv inc/config.inc.php.backup ~/poweradmin-backups/config.inc.php.$(date +%Y%m%d)
+```
 
 3. **Clean up other legacy files:**
    - You can safely remove `.old`, `.bak`, or other backup files from the `inc/` directory

docs/upgrading/v4.1.0.md

@@ -109,17 +109,15 @@ Four new pre-configured permission templates are included:
 
 Customize the Poweradmin interface with CSS files that persist across upgrades:
 
-1. Copy example files in `templates/default/style/`:
-
-    ```bash
-    cp custom_light.css.example custom_light.css
-    cp custom_dark.css.example custom_dark.css
-    ```
-
+1. Copy example files in `templates/default/style/`
 2. Edit the CSS files with your customizations
-
 3. Changes are automatically loaded for the corresponding theme
 
+```bash
+cp custom_light.css.example custom_light.css
+cp custom_dark.css.example custom_dark.css
+```
+
 See [Custom CSS](../configuration/ui/custom-css.md) for details.
 
 ### Username Recovery