Ways to contribute
- Submit or improve shortcut packs — the most common contribution.
- Publish typed marketplace bundles (prompts, snippets, commands, workflows, and related families) through the moderated website flow — see Community Marketplace (creators).
- Report incorrect or missing shortcuts — include app version and reproducible steps.
- Suggest features — especially overlay UX, search quality, or localization gaps.
If you want to ship non-shortcut overlay content for specific apps (process-targeted JSON per family), use the Community Marketplace creator dashboard after sign-in. Bundles are reviewed before they appear in the public catalog; FluentOverlay Pro is required for end users to install. This path does not replace GitHub contributions for shortcut packs — see the guide above for scope and rules.
Contributing a pack
- Fork the FluentOverlay repository or export JSON from the Pack Editor (Pro).
- Follow the schema documented in Creating custom packs (
/schemas/pack.schema.json).
- Test against the real application on Windows — shortcuts must be verified, not guessed.
- Open a GitHub pull request with a clear description, or reach out via the contact form if you cannot use GitHub.
Guidelines
- Accuracy — verify every chord in the target build; note the app version in the PR description when possible.
- Completeness — prefer covering whole primary menus over a handful of random keys.
- Localization — English is required for upstream review; additional locales are welcome.
- Naming — match existing pack naming conventions (
processNames, file names, category labels) to keep the index predictable.
Code & docs
Bug fixes and documentation improvements follow the same hygiene: small focused PRs, screenshots when UI changes, and respect for WinUI 3 + MVVM patterns described in the FluentOverlay contributor docs on GitHub.
Thank you for helping make Windows feel a little more fluent.
← Back to FluentOverlay