V2

Author: Frooodle

.claude/settings.local.json

@@ -0,0 +1,10 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(npm run docusaurus:*)",
+      "Bash(cat:*)"
+    ],
+    "deny": [],
+    "ask": []
+  }
+}

docs/Advanced Configuration/UI Customisation.md

@@ -20,62 +20,34 @@ These settings (in Settings.yml) control system behavior and customization capab
 - `showUpdate` - Controls whether update notifications are displayed
 - `showUpdateOnlyAdmin` - When true, restricts update notifications to admin users only (requires `showUpdate: true`)
 
-
-## System Configuration
-``customHTMLFiles`` In Settings.yml Enables custom HTML file overrides (called fragments) when set to true
-
-## Custom Files
-When `customHTMLFiles` is enabled, you can override the default templatesby placing your custom files in specific directories. The system uses a resource override mechanism where files in these custom directories take precedence over the default files.
-
-### Directory Structure
-```
-customFiles/
-├── static/          # Static assets (CSS, JS, images, etc.)
-└── templates/       # HTML template files
+## 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.
+
+For advanced UI customization in V2.0:
+1. Clone or download the repository
+2. Modify the React components in the `frontend/src` directory
+3. Build the frontend: `cd frontend && npm install && npm run build`
+4. Volume mount the `frontend/dist` folder into your Docker container to replace the built-in frontend files
+
+Example docker-compose with custom frontend:
+```yaml
+services:
+  stirling-pdf:
+    image: docker.stirlingpdf.com/stirlingtools/stirling-pdf:latest
+    ports:
+      - '8080:8080'
+    volumes:
+      - ./frontend/dist:/app/frontend/dist  # Mount your custom frontend
+    environment:
+      - MODE=BOTH
 ```
 
-### File Locations
-The root path for custom files varies by installation type:
-- **Default/Docker Installation**: `./customFiles/`
-- **Windows Desktop**: `%APPDATA%\Stirling-PDF\customFiles\`
-- **MacOS Desktop**: `~/Library/Application Support/Stirling-PDF/customFiles/`
-- **Linux Desktop**: `~/.config/Stirling-PDF/customFiles/`
-
-### Override Examples
-To override existing files, maintain the same directory structure as the original. Here are some examples with links to the original files you would be overriding:
-
-To override a file:
-1. Navigate to the original file in the GitHub repository
-2. Copy its contents
-3. Create the same file path under your `customFiles` directory following the same directory structure
-4. Paste and modify the contents as needed
-
-Note: When overriding templates, first copy the existing template from the [source repository](https://github.com/Stirling-Tools/Stirling-PDF/tree/main/app/core/src/main/resources/templates) to maintain the base structure.
-
-1. To replace the favicon:
-   ```
-   customFiles/static/favicon.svg
-   ```
-   Original file: [Stirling-PDF/app/core/src/main/resources/static/favicon.svg](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/app/core/src/main/resources/static/favicon.svg)
-
-2. To override a Bootstrap icon font:
-   ```
-   customFiles/static/css/fonts/bootstrap-icons.woff
-   ```
-   Original file: [Stirling-PDF/app/core/src/main/resources/static/css/fonts/bootstrap-icons.woff](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/app/core/src/main/resources/static/css/fonts/bootstrap-icons.woff)
-
-3. To modify a template:
-   ```
-   customFiles/templates/fragments/common.html
-   ```
-   Original file: [Stirling-PDF/app/core/src/main/resources/templates/fragments/common.html](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/app/core/src/main/resources/templates/fragments/common.html)
-
-The original files can be found in the GitHub repository under:
-- Static files: [Stirling-PDF/app/core/src/main/resources/static/](https://github.com/Stirling-Tools/Stirling-PDF/tree/main/app/core/src/main/resources/static)
-- Templates (HTML files): [Stirling-PDF/app/core/src/main/resources/templates/](https://github.com/Stirling-Tools/Stirling-PDF/tree/main/app/core/src/main/resources/templates)
-
-
-
+The following environment-based customizations are still supported without rebuilding:
+- Application name and branding
+- Update notification settings
+- Language settings
+- Theme preferences (via application settings)
 
 ## Configuration Examples
 
@@ -90,7 +62,6 @@ The original files can be found in the GitHub repository under:
     system:
       showUpdate: false # Control update notification visibility
       showUpdateOnlyAdmin: false # Restrict update notifications to admins
-      customHTMLFiles: false # Enable custom HTML/CSS overrides
     ```
   </TabItem>
   <TabItem value="local" label="Local Environment">
@@ -101,8 +72,7 @@ The original files can be found in the GitHub repository under:
     java -jar Stirling-PDF.jar \
       -DAPP_HOME_NAME="New Application Name" \
       -DSHOW_UPDATE=false \
-      -DSHOW_UPDATE_ONLY_ADMIN=false \
-      -DCUSTOM_HTML_FILES=true
+      -DSHOW_UPDATE_ONLY_ADMIN=false
     ```
 
     **Option 2: Using Environment Variables**
@@ -112,7 +82,6 @@ The original files can be found in the GitHub repository under:
     export UI_APPNAVBARNAME="Stirling PDF"
     export SYSTEM_SHOWUPDATE=false
     export SYSTEM_SHOWUPDATEONLYADMIN=false
-    export SYSTEM_CUSTOMHTMLFILES=true
     ```
   </TabItem>
   <TabItem value="docker-run" label="Docker Run">
@@ -121,8 +90,7 @@ The original files can be found in the GitHub repository under:
     -e UI_HOMEDESCRIPTION=Your locally hosted one-stop-shop for all your PDF needs. \
     -e UI_APPNAVBARNAME=Stirling PDF \
     -e SYSTEM_SHOWUPDATE=false \
-    -e SYSTEM_SHOWUPDATEONLYADMIN=false \
-    -e SYSTEM_CUSTOMHTMLFILES=true
+    -e SYSTEM_SHOWUPDATEONLYADMIN=false
     ```
   </TabItem>
   <TabItem value="docker-compose" label="Docker Compose">
@@ -133,9 +101,6 @@ The original files can be found in the GitHub repository under:
       UI_APPNAVBARNAME: Stirling PDF
       SYSTEM_SHOWUPDATE: "false"
       SYSTEM_SHOWUPDATEONLYADMIN: "false"
-      SYSTEM_CUSTOMHTMLFILES: "true"
-    volumes:
-      - ./customFiles:/app/customFiles # Mount custom files directory
     ```
   </TabItem>
 </Tabs>

docs/Contribute.md

@@ -4,12 +4,71 @@ id: Contribute
 ---
 
 # Contribution guidelines
-Thanks for taking a look at how to contribute to Stirling PDFs open-source codebase
-Please checkout our GitHub documentation
+Thanks for taking a look at how to contribute to Stirling PDFs open-source codebase!
 
-## Adding/Update translations
-See [How To Add New Language guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md)
+## Development Setup
 
-## Wanting to contribute to our codebase
+### Prerequisites
+- Java 17 or 21 (21 recommended)
+- Node.js 18+
+- Docker (for testing)
+- Gradle (included in repository)
 
-See our [CONTRIBUTING guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md)
+### Getting Started
+
+1. **Clone the repository**
+   ```bash
+   git clone https://github.com/Stirling-Tools/Stirling-PDF.git
+   cd Stirling-PDF
+   ```
+
+2. **Backend Development**
+   ```bash
+   # Build and run the Spring Boot backend
+   ./gradlew bootRun
+   # Backend runs on localhost:8080
+   ```
+
+3. **Frontend Development (V2.0+)**
+   ```bash
+   # Navigate to frontend directory
+   cd frontend
+
+   # Install dependencies
+   npm install
+
+   # Run development server
+   npm run dev
+   # Frontend runs on localhost:5173, proxies API calls to backend (localhost:8080)
+   ```
+
+## Contributing to Code
+
+### Backend Contributions
+- See our [CONTRIBUTING guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md)
+- Backend uses Spring Boot + Java
+- Code formatting: Run `./gradlew spotlessApply` before committing
+
+### Frontend Contributions (V2.0+)
+- Frontend is a React + TypeScript application
+- Uses Vite for build tooling
+- UI components: Mantine UI + TailwindCSS
+- Adding new tools: See [ADDING_TOOLS.md](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/ADDING_TOOLS.md)
+- Tool architecture: Uses `useToolOperation` hook pattern
+
+## Translation Contributions
+
+### V2.0 Translations (JSON)
+Translation files are located in `frontend/public/locales/`
+- **CRITICAL**: Always update translations in `en-GB` only, never `en-US`
+- Files are organized by feature (e.g., `common.json`, `tools.json`)
+- Use standard JSON format
+
+### Legacy Translations (Properties)
+For V1.5 and backend translations:
+- See [How To Add New Language guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md)
+
+## Development Resources
+- **API Documentation**: Access at `/swagger-ui/index.html` on your local instance
+- **Developer Guide**: See `DeveloperGuide.md` in the repository
+- **Claude Code Guide**: See `CLAUDE.md` for detailed architecture and patterns

docs/FAQ.md

@@ -34,4 +34,41 @@ If you experience connection issues, use these alternative endpoints:
 - Docker Hub: `docker pull stirlingtools/stirling-pdf:latest`
 - GitHub: `docker pull ghcr.io/stirling-tools/stirling-pdf:latest`
 
-All endpoints provide the same functionality.
+All endpoints provide the same functionality.
+
+### Q8: What's different in V2.0?
+
+V2.0 is a major frontend rewrite with significant improvements:
+- **Modern React Frontend**: Complete rewrite using React + TypeScript replacing the old Thymeleaf templates
+- **Better Performance**: Handles large PDFs (up to 100GB+) with improved memory management
+- **Stateful Processing**: Upload PDFs once and chain multiple tools without reloading files
+- **Client-Side Storage**: Uses IndexedDB for file persistence and thumbnail caching
+- **Native Desktop Apps**: Powered by Tauri for improved native experience
+- **Flexible Deployment**: Can deploy frontend and backend separately for better scalability
+
+The backend and API remain largely unchanged, so existing integrations continue to work.
+
+### Q9: Can I customize the UI in V2.0 like I did in V1.5?
+
+No, the V1.5 `customFiles/` folder override system no longer works in V2.0 due to the React-based frontend.
+
+You can still customize:
+- Application name and branding via environment variables
+- Theme preferences via application settings
+- Language settings
+
+For extensive UI customization:
+1. Clone the repository and modify React components in `frontend/src/`
+2. Build the frontend: `npm install && npm run build`
+3. Volume mount `frontend/dist` into your Docker container to replace the built-in frontend
+
+See [UI Customisation](/Advanced%20Configuration/UI%20Customisation) for detailed instructions.
+
+### Q10: How do I develop for the V2.0 React frontend?
+
+See our updated [Contribute](/Contribute) guide for detailed instructions. Quick start:
+1. Clone the repository
+2. Run backend: `./gradlew bootRun` (localhost:8080)
+3. Run frontend: `cd frontend && npm install && npm run dev` (localhost:5173)
+
+The frontend dev server automatically proxies API calls to the backend.

docs/Functionality/The Technologies.md

@@ -5,25 +5,29 @@ description: List of all technologies Stirling-PDF uses!
 # The Technologies Behind Stirling PDF
 Stirling PDF harnesses several technologies throughout its implementation.
 
-# Java
-As part of the JAVA framework to host the WebUI itself we use Spring Boot and Thymeleaf.
-Apache PDFBox is the core of the PDF functionality within Stirling-PDF.
-They offer a variety of methods to edit PDFs which we have then built Stirling-PDF on.
-We also show all licenses used within our Java application [here](https://stirlingpdf.io/licenses).
-
-# JavaScript
-- [PDF.js](https://github.com/mozilla/pdf.js)
-- [PDF-LIB.js](https://github.com/Hopding/pdf-lib)
-
-# Core Components
-- [Spring Boot + Thymeleaf](https://spring.io/projects/spring-boot) for the web framework
+# Backend (Java)
+- [Spring Boot](https://spring.io/projects/spring-boot) for the REST API framework
 - [PDFBox](https://pdfbox.apache.org/) for majority of PDF manipulation
 - [qpdf](https://qpdf.sourceforge.io/) for some PDF operations
 - [LibreOffice](https://www.libreoffice.org/discover/libreoffice/) for advanced file conversions
 
-# Additional Technologies
-- HTML, CSS, JavaScript for the frontend
+We also show all licenses used within our Java application [here](https://stirlingpdf.io/licenses).
+
+# Frontend (React SPA)
+- [React](https://react.dev/) + [TypeScript](https://www.typescriptlang.org/) for the web application
+- [Vite](https://vitejs.dev/) for build tooling and development server
+- [Mantine UI](https://mantine.dev/) component library for UI components
+- [TailwindCSS](https://tailwindcss.com/) for styling
+- [PDF.js](https://github.com/mozilla/pdf.js) for client-side PDF rendering
+- [PDF-LIB.js](https://github.com/Hopding/pdf-lib) for client-side PDF manipulation
+- [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API) for client-side file storage and caching
+- [i18next](https://www.i18next.com/) for internationalization
+
+# Desktop Application
+- [Tauri](https://tauri.app/) for native desktop application framework (Windows, Mac, Linux)
+
+# Infrastructure
 - Docker for containerization
-- jcefmaven (specifically for portable non-server version)
+- Gradle for build management
 
 For a comprehensive list of all technologies within the java application and their licenses, please visit our [licenses page](https://stirlingpdf.io/licenses).

docs/Getting Started.md

@@ -13,10 +13,18 @@ slug: /
 - **Open-Source:** Community-driven with frequent updates and GitHub support.
 - **Multi-Language Support:** Available in 38+ languages with active translations.
 
+### What's New in V2.0
+- **Modern React Frontend:** Complete rewrite with React + TypeScript for improved performance and user experience
+- **Stateful Document Processing:** Upload PDFs once and chain multiple tools without reloading
+- **Enhanced Performance:** Handles large PDFs (up to 100GB+) with improved memory management
+- **Client-Side File Storage:** IndexedDB for persistent file storage and thumbnail caching
+- **Improved Desktop Experience:** Native desktop apps powered by Tauri
+- **Flexible Deployment:** Separate frontend/backend deployment options for scalability
+
 Please feel free to request new features or report bugs through our [GitHub](https://github.com/Stirling-Tools/Stirling-PDF/issues) or [Discord](https://discord.gg/Cn8pWhQRxZ).
 
 
-## Introduction 
+## Introduction
 
 This guide will help you choose the right installation method based on your needs.
 We prioritise and focus on our Server deployment options however we also offer a [Ultra-Lite model](/Installation/Versions) for desktop users