diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 1f6d0e4..203ea6b 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -30,6 +30,16 @@ body:
placeholder: "1.0.0"
validations:
required: true
+ - type: dropdown
+ id: workflow
+ attributes:
+ label: Which workflow was affected most?
+ options:
+ - Attaching files from multiple folders
+ - Collecting screenshots for bug reports/support
+ - Moving or copying files between folders/apps
+ - Organizing links/notes/images across shelves
+ - Other
- type: input
id: windows
attributes:
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 6531af5..7f43612 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,14 @@
-blank_issues_enabled: true
+blank_issues_enabled: false
contact_links:
+ - name: Start with a good first issue
+ url: https://github.com/editorrylix/Pouchy/labels/good%20first%20issue
+ about: Looking to contribute? Pick a small scoped issue to get started.
+ - name: Launch and feedback playbook
+ url: https://github.com/editorrylix/Pouchy/blob/main/docs/LAUNCH_PLAYBOOK.md
+ about: Reusable release messaging, channels and monthly growth-review checklist.
+ - name: Actions and themes guides
+ url: https://github.com/editorrylix/Pouchy/blob/main/docs/GUIDE.md
+ about: Learn how to extend Pouchy and where to find user-facing docs.
- name: Download the latest version
url: https://github.com/editorrylix/Pouchy/releases/latest
about: Grab the newest Pouchy before reporting โ your bug may already be fixed.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
index b7c46d7..3eebc3f 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -14,6 +14,16 @@ body:
attributes:
label: What would help?
description: How would you like Pouchy to handle it?
+ - type: dropdown
+ id: impact
+ attributes:
+ label: Which workflow would this improve most?
+ options:
+ - Attaching files from multiple folders
+ - Collecting screenshots for bug reports/support
+ - Moving or copying files between folders/apps
+ - Organizing links/notes/images across shelves
+ - Other
- type: textarea
id: extra
attributes:
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6b73c55..8ba3365 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,11 +13,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
### Added
- **Microsoft Store package** (MSIX for x64 and ARM64). The Store version is updated by the Store, starts with Windows through its startup task, and otherwise works exactly like the other downloads. See [packaging/store/README.md](packaging/store/README.md).
+- **Launch playbook** for repeatable release pages, social posts, channel targeting and monthly growth reviews. See [docs/LAUNCH_PLAYBOOK.md](docs/LAUNCH_PLAYBOOK.md).
### Changed
- Added a [privacy policy](PRIVACY.md), linked from Settings โ About.
- The full user guide now lives in [docs/GUIDE.md](docs/GUIDE.md). The welcome window and tray menu โ Help link there.
+- Refreshed the README to lead with a clear one-line positioning, first-30-seconds workflows, and a concise "which download should I pick?" section.
+- Added a trust-focused "known limitations and workarounds" section in the README, plus clearer contribution entry points.
## [1.1.0] - 2026-10-07
diff --git a/README.md b/README.md
index dcec3ec..eb914b2 100644
--- a/README.md
+++ b/README.md
@@ -4,11 +4,13 @@
# Pouchy
-**A drag-and-drop shelf for Windows 10 and 11.**
+**A Windows drag-and-drop shelf for files, links, text and screenshots.**
Park files, images, links and text in a floating pouch, then drop them wherever they need to go.
A free Windows alternative to Dropover and Yoink.
+
+Get fewer window switches, faster attachments and smoother bug reports.
@@ -47,6 +49,13 @@ Pouchy is a small shelf that appears where your mouse is while you drag. Drop th
- **Put anything in it:** files, folders, groups of files, images, text, links and colour codes.
- **Drag it out to any app:** Explorer, a browser, chat apps, design tools, email. Files are copied by default, so the originals stay where they were.
+### Why Pouchy vs the usual Windows workflow?
+
+- **Fewer window switches:** park files once, then drop them where needed.
+- **Faster attachments:** collect from different folders, attach in one drag.
+- **Smoother bug reports:** keep screenshots together while you reproduce issues.
+- **No account or telemetry:** your pouch stays local on your PC.
+
@@ -57,6 +66,12 @@ Pouchy is a small shelf that appears where your mouse is while you drag. Drop th
2. **Drag any file and give the mouse a little shake.** The pouch pops up next to it. Drop the file in.
3. **Drag it out wherever you need it.** Press Alt+Shift+Z or click the tray icon to show the pouch, then drag the file into an email, a chat or a folder.
+### In your first 30 seconds
+
+- **๐ง Faster attachments:** drag files from multiple folders into the pouch, then drop them into one email.
+- **๐ Smoother bug reports:** press Alt+Shift+S a few times, then drag all screenshots into the report.
+- **๐ Cross-folder file moves:** collect files once, switch folders, then drop them where they belong.
+
### What people use it for
- **๐ง Attachments from everywhere.** Collect files from three different folders, then drag them into an email in one go.
@@ -149,6 +164,12 @@ Press Ctrl+K and type. The palette finds:
Download from the **[latest release](https://github.com/editorrylix/Pouchy/releases/latest)**:
+### Which file should I download?
+
+- **Most Windows PCs (Intel/AMD):** `setup-x64.exe` (recommended)
+- **Windows on ARM (Snapdragon):** `setup-arm64.exe`
+- **Prefer no install:** use the matching portable `.zip`
+
| | Intel and AMD PCs | Windows on ARM |
| --- | --- | --- |
| **Installer** (recommended) | `Pouchy-x.y.z-setup-x64.exe` | `Pouchy-x.y.z-setup-arm64.exe` |
@@ -165,6 +186,12 @@ Download from the **[latest release](https://github.com/editorrylix/Pouchy/relea
> [!NOTE]
> Pouchy isn't code-signed yet, so Windows SmartScreen may say *"Windows protected your PC"* for a new download. Click **More info โ Run anyway**. Each release lists SHA-256 checksums so you can check your download.
+### Known limitations (and workarounds)
+
+- **Windows SmartScreen warning:** Pouchy is not code-signed yet. Use **More info โ Run anyway** and verify the release SHA-256 if needed.
+- **Windows 11 right-click menus:** Explorer integration is under **Show more options** due to Windows shell limits.
+- **If your default hotkey is already taken:** Pouchy auto-picks a free fallback and shows it in Settings/tray.
+
## Keyboard shortcuts
@@ -271,6 +298,14 @@ Pushing a version tag (`vX.Y.Z`) makes [GitHub Actions](.github/workflows/releas
To report a bug or suggest a feature, [open an issue](https://github.com/editorrylix/Pouchy/issues/new/choose). A screenshot and the last lines of `%AppData%\Pouchy\debug.log` help.
+## Contributing
+
+- **Start here:** [good first issues](https://github.com/editorrylix/Pouchy/labels/good%20first%20issue)
+- **Report reproducible bugs:** [Bug report template](https://github.com/editorrylix/Pouchy/issues/new?template=bug_report.yml)
+- **Suggest improvements:** [Feature idea template](https://github.com/editorrylix/Pouchy/issues/new?template=feature_request.yml)
+- **Extend Pouchy:** [Actions guide](docs/ACTIONS.md) and [Themes guide](docs/THEMES.md)
+- **Release, launch and growth process:** [Launch playbook](docs/LAUNCH_PLAYBOOK.md)
+
If Pouchy is useful to you, a star helps other Windows users find it. You can also support development:
diff --git a/docs/LAUNCH_PLAYBOOK.md b/docs/LAUNCH_PLAYBOOK.md
new file mode 100644
index 0000000..71f9b6d
--- /dev/null
+++ b/docs/LAUNCH_PLAYBOOK.md
@@ -0,0 +1,92 @@
+# Pouchy launch playbook
+
+Repeatable checklist for each release so messaging, distribution and feedback loops stay consistent.
+
+[โ Back to the README](../README.md)
+
+## 1) Core message (use everywhere)
+
+**Pouchy is a Windows drag-and-drop shelf for files, links, text and screenshots.**
+
+Lead with outcomes:
+- fewer window switches
+- faster attachments
+- smoother bug-report workflows
+
+Use this line in README, release pages and social posts.
+
+## 2) Release page checklist
+
+1. Put a short demo near the top (`demo.gif` + optional clip link).
+2. Include 3 quick workflows:
+ - attachments from multiple folders
+ - screenshot collection for bug reports
+ - cross-folder file moves/copies
+3. Keep download guidance explicit:
+ - installer first
+ - x64 vs ARM64 clearly labeled
+ - portable zip option
+4. Keep trust signals visible:
+ - privacy/no telemetry
+ - known limitations + workaround
+5. End with a clear feedback prompt:
+ - "What file workflow is most annoying for you right now?"
+
+## 3) Social post loop per release
+
+Publish at least 3 short posts:
+
+1. **Feature post**
+ - one feature
+ - one GIF/video
+ - one concrete user outcome
+2. **Workflow post**
+ - one real scenario (email, screenshots, file sorting, etc.)
+ - short before/after friction statement
+3. **Community post**
+ - request feedback with a specific question
+ - link to issues/discussions
+
+Reuse the same core assets and wording across Reddit/X/Discord/dev communities.
+
+## 4) Channel targeting
+
+Prioritise communities where workflow tools are discussed:
+- Windows productivity
+- file management
+- creators/design workflows
+- developer productivity
+
+Avoid generic promotion-only posting. Start from a workflow pain point and ask for feedback.
+
+## 5) Feedback triage and loop-closing
+
+For incoming requests, label and route as:
+- **Quick wins**
+- **High-value roadmap**
+- **Won't do for now**
+
+When shipping community-requested changes, say so in release notes:
+- "Requested by users, now added."
+
+## 6) Contribution funnel
+
+Keep these links visible and up to date:
+- Good first issues
+- Bug report template
+- Feature request template
+- Docs for extending Pouchy (actions/themes)
+
+## 7) Monthly growth review
+
+Track and review monthly:
+- GitHub profile/repo visits
+- README โ Releases click-through
+- release download counts
+- star growth
+- issue quality (clear repro steps, useful logs, actionable requests)
+
+Decide next month by evidence:
+- repeat channels/messages that convert
+- drop low-signal channels
+- keep testing small messaging iterations
diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md
index 1982639..474f56b 100644
--- a/docs/ROADMAP.md
+++ b/docs/ROADMAP.md
@@ -6,6 +6,26 @@ Legend: ๐ด must-have ยท ๐ก should-have ยท ๐ข nice-to-have
---
+## Execution focus (living priorities)
+
+### Now (ship + learn)
+- Keep positioning consistent everywhere: "Windows drag-and-drop shelf for files, links, text and screenshots."
+- Prioritise improvements that reduce workflow friction: fewer window switches, faster attachments, smoother bug reporting.
+- Keep release messaging practical: one feature, one workflow, one short demo asset per release.
+
+### Feedback triage buckets
+- **Quick wins:** small fixes with high day-to-day impact and low risk.
+- **High-value roadmap:** larger changes with clear, repeated user demand.
+- **Won't do for now:** ideas that don't fit current product direction or would add complexity without clear value.
+
+### How roadmap items are prioritised
+- Frequency of user pain (how often it comes up)
+- Workflow impact (time/friction saved)
+- Delivery cost and maintenance burden
+- Fit with Pouchy's core promise (fast drag-and-drop workflow on Windows)
+
+---
+
## 1. Theming & customisation (core identity)
### Theme engine