docs(readme): seven screenshots and a name without a space in it
The screenshots were captured on 2026-08-14 against the installed build and staged without ever being committed or referenced. The README had no image beyond its five badges — a GUI whose readme shows no GUI. `setting (2).png` -> `settings.png`. A space and a `(2)` in an asset path has to be percent-encoded in Markdown and is a filename nobody meant to publish. Installed and Code Health lead, because they are the two screens that show what the tool is for; the other five are behind a `<details>` so the README stays scannable. Alt text says what each shot demonstrates rather than repeating the tab name. Caveat worth knowing: these predate the About tab, so the sidebar in them has eight entries and 1.0 has nine. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
57c365e36a
commit
401c917f20
2 files changed
+21
No files matched your search
@@ -23,6 +23,27 @@
|
||||
- **Skip-and-continue execution** — one failed package never aborts the batch; you get a final report: *"13 successful, 2 failed"* with per-package reasons.
|
||||
- **Never touches itself** — PipDock is a standalone binary that lives outside every environment it manages, so it can never break itself mid-update.
|
||||
|
||||
## Screenshots
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
<details>
|
||||
<summary>Environments, Updates, Search, Pins, Settings</summary>
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
</details>
|
||||
|
||||
## Features (v1)
|
||||
|
||||
| Area | What you get |
|
||||
|
||||
File renamed without changes.
|
Before Width: | Height: | Size: 60 KiB After Width: | Height: | Size: 60 KiB |
Reference in new issue
Block a user