WIP

Author: Frooodle

.claude/settings.local.json

@@ -2,9 +2,13 @@
   "permissions": {
     "allow": [
       "Bash(npm run docusaurus:*)",
-      "Bash(cat:*)"
+      "Bash(cat:*)",
+      "Bash(tree:*)"
     ],
     "deny": [],
-    "ask": []
+    "ask": [],
+    "additionalDirectories": [
+      "/mnt/c/Users/systo/git/Stirling-PDFNew/"
+    ]
   }
 }

docs/Advanced Configuration/How to add configurations.md

@@ -11,20 +11,54 @@ Stirling PDF allows easy customization of the app.
 Includes things like
 
 - Custom application name
-- Custom slogans, icons, HTML, images CSS etc (via file overrides)
+- Security settings
+- Feature toggles
+- System behavior
+- And much more
 
-There are two options for this, either using the generated settings file ``settings.yml``
-This file is located in the ``/configs`` directory and follows standard YAML formatting
+## V2.0 - In-App Settings (Recommended)
 
-Environment variables are also supported and would override the settings file
-For example in the settings.yml you have
+:::tip New in V2.0
+**Admin users can now configure all settings directly in the application!**
 
-```
+If you have login enabled (`SECURITY_ENABLELOGIN=true`) and are logged in as an admin, navigate to the **Settings** menu in the application to configure everything through the UI. Changes apply immediately without restarting.
+
+This is the easiest and recommended way to manage Stirling-PDF V2.0.
+:::
+
+## Configuration Methods
+
+There are three ways to configure Stirling-PDF (in order of precedence):
+
+1. **In-App Settings** (V2.0+, requires admin login) - Configure via the Settings menu
+2. **Environment Variables** - Set via Docker, docker-compose, or system environment
+3. **settings.yml file** - Located in the `/configs` directory
+
+**Precedence**: Environment variables override settings.yml. In-app settings update the settings.yml file.
+
+### Using settings.yml
+
+The settings file is located in the `/configs` directory and follows standard YAML formatting.
+
+Example:
+```yaml
 security:
-  enableLogin: 'true'
+  enableLogin: true
+```
+
+### Using Environment Variables
+
+Environment variables override the settings file.
+
+For example, to override the setting above:
+```bash
+SECURITY_ENABLELOGIN=true
 ```
 
-To have this via an environment variable you would have ``SECURITY_ENABLELOGIN``
+**Format rule**: Convert YAML paths to environment variables by:
+- Replacing `.` with `_`
+- Making everything UPPERCASE
+- Example: `security.enableLogin` → `SECURITY_ENABLELOGIN`
 
 The Current list of settings is
 

docs/Advanced Configuration/Pipeline.md

@@ -7,6 +7,20 @@ title: Pipeline Automation
 
 # Pipeline Configuration and Usage Tutorial
 
+:::info V2.0 Update - New "Automate" Feature
+In V2.0, the pipeline frontend interface has been replaced with the new **"Automate"** feature, which offers an improved user experience for creating and managing automation workflows. The backend pipeline system (JSON configuration and folder scanning) continues to work the same way.
+
+**What changed:**
+- ✅ Backend pipeline processing - **No changes**
+- ✅ JSON pipeline configurations - **Still work exactly the same**
+- ✅ Folder scanning with pipelines - **Still works the same**
+- 🆕 Frontend interface - **Now called "Automate" with better UX**
+
+If you have existing pipeline JSON files, they continue to work in V2.0's Automate feature.
+:::
+
+## About Pipeline Automation
+
 - Configure the pipeline config file and input files to run files against it.
 - For reuse, download the config file and re-upload it when needed, or place it in `/pipeline/defaultWebUIConfigs/` to auto-load in the web UI for all users.
 

docs/Advanced Configuration/UI Customisation.md

@@ -22,7 +22,22 @@ These settings (in Settings.yml) control system behavior and customization capab
 
 ## V2.0 UI Customization Notes
 
-**Important**: Stirling-PDF V2.0 uses a React-based frontend. The V1.5 `customFiles/` folder system for overriding templates **no longer works** in V2.0.
+### In-App Settings Management (V2.0+)
+
+**New in V2.0**: If you have login enabled and are logged in as an admin, you can now configure all settings directly in the application through the **Settings** menu. No need to edit `settings.yml` manually!
+
+**How to access:**
+1. Enable login: `SECURITY_ENABLELOGIN=true`
+2. Log in as an admin user
+3. Navigate to **Settings** in the application
+4. Configure all options through the UI
+5. Changes apply immediately
+
+This is the recommended way to manage settings in V2.0 for production deployments.
+
+### Template Customization Changes
+
+**Important**: The V1 `customFiles/` folder system for overriding templates has been replaced with a new customization approach due to the UI framework change in V2.0.
 
 For advanced UI customization in V2.0:
 1. Clone or download the repository
@@ -34,7 +49,7 @@ Example docker-compose with custom frontend:
 ```yaml
 services:
   stirling-pdf:
-    image: docker.stirlingpdf.com/stirlingtools/stirling-pdf:latest
+    image: stirlingtools/stirling-pdf:latest
     ports:
       - '8080:8080'
     volumes:
@@ -43,11 +58,11 @@ services:
       - MODE=BOTH
 ```
 
-The following environment-based customizations are still supported without rebuilding:
-- Application name and branding
-- Update notification settings
-- Language settings
-- Theme preferences (via application settings)
+The following customizations work without rebuilding:
+- Application name and branding (via environment variables or in-app settings)
+- Update notification settings (via in-app settings if admin)
+- Language settings (via in-app settings)
+- Theme preferences (via in-app settings)
 
 ## Configuration Examples