docs: add page-by-page user guide

Author: b45632

README.md

@@ -47,6 +47,22 @@ The current interface is in German. This README uses the exact German button nam
 | Multi-project setup | **Workspaces** in the top bar | Starts several project actions together |
 | App configuration | **Einstellungen** in the top bar | IDE commands, templates, theme, folders and import/export |
 
+## Documentation
+
+For a detailed explanation of every page and feature, see the full user guide:
+
+[Open the Code Deck documentation](docs/README.md)
+
+
+### Guides
+
+- [Dashboard](docs/pages/dashboard.md)
+- [New Project](docs/pages/new-project.md)
+- [Project Details](docs/pages/project-details.md)
+- [Processes](docs/pages/processes.md)
+- [Workspaces](docs/pages/workspaces.md)
+- [Settings](docs/pages/settings.md)
+
 ## Adding projects
 
 Click **Neues Projekt** on the dashboard. There are two modes.

docs/README.md

@@ -0,0 +1,25 @@
+# Code Deck user guide
+
+This guide explains the app page by page. The names in bold match the current German interface so the controls are easy to find.
+
+## Pages
+
+| Page | Use it for |
+|---|---|
+| [Dashboard](pages/dashboard.md) | Finding projects and using the most common shortcuts |
+| [New Project](pages/new-project.md) | Creating a starter project, copying a template or importing an existing folder |
+| [Project Details](pages/project-details.md) | Editing one project and using its IDE, terminal, commands and Git information |
+| [Processes](pages/processes.md) | Viewing live output and stopping commands |
+| [Workspaces](pages/workspaces.md) | Starting several projects and actions as one setup |
+| [Settings](pages/settings.md) | Configuring editors, terminal behavior, templates, theme and backups |
+| [Onboarding](pages/onboarding.md) | Completing the first setup or running it again |
+
+## A useful way to think about Code Deck
+
+- A **project** represents one local project folder.
+- A **command** represents something that can run inside that folder.
+- A **process** is one active or completed command run.
+- A **workspace** is a saved routine made from several project actions.
+- A **template** is a folder used as the starting point for a new project.
+
+Code Deck keeps its own configuration locally. Adding a project does not move the project folder, and opening a project does not change its source files.

docs/architecture.md

@@ -0,0 +1,39 @@
+# Dashboard
+
+![Code Deck dashboard](../screenshots/dashboard.png)
+
+The dashboard is the main page. It is meant for finding a project quickly and starting the action you use most often.
+
+## Where to find it
+
+The dashboard opens when Code Deck starts. Return to it by closing the current dialog or detail view.
+
+## Main controls
+
+| Control | What it does |
+|---|---|
+| Search field | Searches project names, paths, tags, frameworks and known Git branches |
+| **Favoriten** | Shows only projects marked with a star |
+| Framework or tag filters | Narrows the list without changing project data |
+| Sort control | Changes the order, for example by name or last use |
+| **Neues Projekt** | Opens the project creation and import dialog |
+| **Ordner scannen** | Searches below a selected folder for likely projects |
+| Star on a project card | Adds or removes the project from favorites |
+| **Details** | Opens the complete project page |
+| IDE quick action | Opens the project with its preferred editor |
+| Command quick action | Runs a saved command without opening the detail page |
+
+## Typical flow
+
+1. Type part of a project name into the search field.
+2. Open the project directly in its preferred IDE, or select **Details** for more options.
+3. Use the star for projects you open often.
+4. Use **Neues Projekt** when the project is not in Code Deck yet.
+
+## Empty dashboard
+
+When no projects have been added, start with **Neues Projekt**. Choose an existing folder when the project already exists, or choose a starter when Code Deck should create the initial files.
+
+## What the dashboard does not do
+
+Removing a card from Code Deck does not delete the project directory. Likewise, archiving a project only hides it from the normal list.

docs/config.md

@@ -0,0 +1,70 @@
+# New Project
+
+![New project dialog](../screenshots/new-project.png)
+
+Open **Neues Projekt** from the dashboard. The dialog supports three different jobs: create a starter project, create from your own template, or add an existing folder.
+
+## Create a starter project
+
+Choose **Neues Projekt erstellen**, then select a starter such as Node.js, React, Spring Boot, Python or Rust.
+
+You provide:
+
+| Field | Meaning |
+|---|---|
+| Project name | The folder name and default display name |
+| Parent folder | The directory in which the new folder is created |
+| Starter | The base files Code Deck should generate |
+| Initialize Git | Runs `git init` after the files are created |
+| Preferred IDE | The editor used by the main open button |
+
+Code Deck shows the final path before creating anything.
+
+Dependencies are not installed automatically. This avoids running package-manager commands without a clear user action. For a generated React project, for example, open its terminal afterwards and run `pnpm install` or `npm install`.
+
+## Use a custom template
+
+Custom templates are ordinary local folders registered under **Einstellungen → Eigene Projektvorlagen**.
+
+When you select one during project creation, Code Deck copies the template contents into the new project folder. These generated or repository-specific directories are skipped:
+
+```text
+.git
+node_modules
+target
+dist
+build
+```
+
+A template is useful when your projects usually begin with the same configuration, folder structure, scripts or internal defaults.
+
+## Add an existing project
+
+Choose **Vorhandenen Ordner hinzufügen** when the project is already on disk.
+
+Code Deck reads common files such as:
+
+```text
+package.json
+Cargo.toml
+pom.xml
+build.gradle
+pyproject.toml
+go.mod
+Dockerfile
+.git
+```
+
+This information is used to suggest frameworks, tags and package scripts. The project files are not rewritten.
+
+## Scan a base folder
+
+Use **Ordner scannen** on the dashboard when many repositories are stored below one parent folder. The scan proposes likely projects; you still decide which ones are added.
+
+## Common problems
+
+**The folder already exists:** choose a different project name or parent folder, or add the existing folder instead.
+
+**A starter command is unavailable:** generated files do not require the related runtime immediately, but running the project later still requires Node.js, Java, Python, Rust or the relevant toolchain.
+
+**The preferred IDE is missing:** configure it first under **Einstellungen → IDEs**.

docs/pages/dashboard.md

@@ -0,0 +1,25 @@
+# Onboarding
+
+The onboarding guide appears on the first launch and can be opened again from **Einstellungen**.
+
+## What it helps with
+
+The guide covers the three things needed before Code Deck becomes useful:
+
+1. choose or scan a folder containing projects
+2. configure at least one IDE
+3. add or create the first project
+
+## Recommended first setup
+
+1. Add VS Code, Cursor, IntelliJ IDEA or the editor you actually use.
+2. Set the default project folder.
+3. Add one existing project.
+4. Open its detail page and save the command you normally use to start it.
+5. Run the command and check its output under **Prozesse**.
+
+Workspaces can be configured later. They are optional and mainly useful once several related projects have been added.
+
+## Running onboarding again
+
+Open **Einstellungen** and select the option to restart onboarding. This does not delete projects or reset settings.

docs/pages/new-project.md

@@ -0,0 +1,43 @@
+# Processes
+
+![Processes and live logs](../screenshots/processes.png)
+
+The process page shows commands that were started from projects or workspaces.
+
+## Process states
+
+| State | Meaning |
+|---|---|
+| Running | The command is still active |
+| Successful | The command exited with code `0` |
+| Failed | The command exited with a non-zero code or could not be started |
+| Stopped | The command was stopped from Code Deck |
+
+## What each entry shows
+
+A process entry can contain:
+
+- project name
+- command label and command text
+- start time
+- process ID when available
+- stdout and stderr output
+- exit code
+- stop button for active commands
+
+## Stopping a command
+
+Use **Stop** on the active process. Code Deck asks the operating system to terminate the process and updates the state afterwards.
+
+Some commands start child processes of their own. If a development server remains active after stopping, check the terminal output and the operating system's process list.
+
+## History
+
+Finished entries remain available so recent output can be checked. Removing an entry from the history does not remove the saved project command and does not change project files.
+
+## Common uses
+
+- checking why a development server failed
+- following test output
+- stopping a long-running command
+- seeing which workspace services are still active

docs/pages/onboarding.md

@@ -0,0 +1,69 @@
+# Project Details
+
+![Project details](../screenshots/project-details.png)
+
+Open **Details** on a project card. This page contains everything that belongs to one project.
+
+## Project information
+
+You can edit:
+
+- display name
+- description
+- tags
+- favorite state
+- preferred IDE
+- archive state
+
+The path identifies the local directory and is used as the default working directory for commands.
+
+## Quick actions
+
+| Action | What it does |
+|---|---|
+| **Open in …** | Opens the project with its preferred IDE |
+| **Terminal öffnen** | Opens a terminal in the project folder |
+| **Ordner öffnen** | Opens Explorer, Finder or the Linux file manager |
+| **Status aktualisieren** | Re-reads frameworks, scripts, Docker files and Git information |
+| Archive | Hides the project from the normal dashboard without deleting its folder |
+| Remove | Removes the project from Code Deck after confirmation; source files remain untouched |
+
+## Commands
+
+Commands are reusable actions such as:
+
+```text
+pnpm dev
+pnpm test
+mvn spring-boot:run
+cargo run
+docker compose up
+```
+
+Each command can have:
+
+- a label shown in the interface
+- the actual shell command
+- an optional working directory relative to the project
+- optional environment variables
+- a display order
+
+Starting a command opens a process entry where the output can be followed. A command is never run merely because it was imported or detected.
+
+## Detected package scripts
+
+For projects with `package.json`, Code Deck can show scripts from the `scripts` section. A suggestion is not yet a saved command. Save it when you want it to appear as a regular project action.
+
+## Git information
+
+For Git repositories, the page can show:
+
+- current branch
+- number of changed files
+- latest commit hash, message and date
+
+Use **Status aktualisieren** after changing branches or making commits outside Code Deck.
+
+## When to use this page
+
+Use the detail page when a project needs more than the single quick action shown on its dashboard card. It is also the correct place to fix a wrong IDE assignment, edit tags or add a new command.