# Community Growth Loop (Post-Launch)

Last verified: **March 24, 2026**

This keeps the free app healthy while growing trust and channel reach.

## Weekly Loop
1. Triage Issues and Discussions daily.
2. Tag top 3 bugs and top 3 feature requests for next patch.
3. Publish a short changelog post every week.
4. Share one workflow template and one integration tip per week.
5. Ask users for before/after results and quote feedback (with permission).

## Monthly Loop
1. Ship at least one stability patch release.
2. Ship one connector or node UX improvement.
3. Refresh screenshots/GIFs on GitHub Pages.
4. Review analytics:
   - Downloads
   - GitHub stars/forks/issues
   - Docker stack pulls/runs
   - Tutorial completion signals

## Contribution Guardrails
- Keep contributions open with templates and quality checks.
- Require issue discussion for major architecture changes.
- Preserve maintainer ownership of roadmap direction.

## Content Cadence
- `How-to` tutorial post (weekly)
- `Release highlights` post (biweekly/monthly)
- `Roadmap update` (monthly)
- `Call for testers` (before major releases)

## Feedback Sources
- GitHub Issues
- GitHub Discussions
- Reddit/self-hosted communities
- Linux maker communities
- Direct support email

## Success Signals
- Faster time-to-first-run for new users
- Reduced setup and canvas friction reports
- Higher integration adoption per user
- More repeat contributors and community PRs