Update

2026-07-24 20:29:23 +02:00
commit 66060348da
107 changed files with 14771 additions and 0 deletions
@@ -0,0 +1,99 @@
+# Stitch review and design corrections
+
+## What worked well
+
+The Stitch export established a strong visual starting point:
+
+- A restrained graphite theme suitable for long sessions.
+- Compact desktop density.
+- Clear technical typography.
+- Useful deployment progress and failure concepts.
+- A credible developer-tool tone without excessive decoration.
+- Good use of green, amber and red for operational state.
+
+## What was changed
+
+### 1. From IDE shell to release cockpit
+
+The export contained navigation for Editor, Monitoring and Extensions. Those features would blur the product into an incomplete IDE. ForgeFlow instead complements the user's existing editor and terminal.
+
+The product boundary is now:
+
+```text
+Understand repository state -> perform safe Git action -> release exact version
+```
+
+### 2. One navigation model
+
+The mock-ups mixed a top product navigation with a broad left application navigation. The implementation uses:
+
+- A compact top bar for global search, identity, refresh and theme.
+- A left rail for Overview, Deployments, Settings and repositories.
+- Repository tabs only inside the selected project.
+
+### 3. Operational cards instead of generic statistics
+
+CPU, queue or server graphs are not useful unless ForgeFlow becomes a monitoring suite. The overview now answers:
+
+- Which projects have local changes?
+- Which commits are not pushed?
+- Which repositories are behind or conflicted?
+- Which exact commits are ready to deploy?
+
+### 4. Persistent Local -> Gitea -> Server rail
+
+The most important state was made visible at the top of every repository workspace. The user no longer needs to infer synchronization from several unrelated badges.
+
+### 5. Contextual action panel
+
+The right panel now changes with state:
+
+- Link or clone.
+- Resolve conflict.
+- Commit and push.
+- Fast-forward synchronize.
+- Push commits.
+- Configure deployment.
+- Deploy exact SHA.
+- Explain the blocking error.
+
+Only one action is visually dominant.
+
+### 6. Diff viewer, not editor
+
+ForgeFlow displays changed files and diffs, but deliberately opens the real project folder for editing. This avoids duplicating editor features and keeps the application technically realistic.
+
+### 7. Safer deployment language
+
+A generic **Deploy** button can hide too much. ForgeFlow displays the exact action:
+
+```text
+Deploy b82f91a -> Production
+```
+
+The confirmation state shows the repository, branch, full SHA and workflow file.
+
+### 8. Desktop behavior
+
+The implementation adds details that static screens could not provide:
+
+- Native directory selection.
+- External-link restrictions.
+- Keyboard shortcut for global search.
+- Ctrl/Cmd+Enter for commit and push.
+- Resizable desktop layout.
+- Offline and error handling foundations.
+- Secure process boundary between UI and system operations.
+
+## Visual direction retained
+
+The implementation intentionally keeps:
+
+- Deep neutral background and panels.
+- Blue primary actions.
+- Green synchronization and health.
+- Amber pending work.
+- Red actual failures and conflicts.
+- Compact status badges.
+- Monospace only for branches, commits, paths and logs.
+- Minimal decorative effects.