Good feedback is short, specific, and grounded in something you actually tried to do. Here's a quick guide for getting your idea or bug into the roadmap.

Pick the right board

• Feature requests — anything you wish Hollahoop did that it doesn't yet.
• Bugs — something that should work but doesn't, or works in a way that surprised you.
• General — questions, discussions, "is this just me?" posts.

Search before you post

Type a few words into the title field on submit feedback. If something close already exists, upvote it instead of creating a duplicate. One post with 30 upvotes beats five posts with 6 each.

What makes a great post

A title that reads like a feature, not a sentence:

• ✅ "Pin a post to the top of a board"
• ❌ "Why can't I keep the important post visible?"

A body that answers three questions:

1. What were you trying to do?
2. What happened instead? (or: what's missing?)
3. Why does it matter? — the use-case is what helps prioritisation.

A bug example:

Trying to sign in via the magic link form on /login with a brand-new email returns "Signups not allowed for OTP". Expected the form to either let me sign up or tell me which sign-in method to use instead. I'm trying to evaluate Hollahoop and don't want to create a GitHub/Google account just to test.

That post got accepted onto the roadmap within hours — because it's reproducible, it tells us why it's blocking the user, and it suggests what should happen.

After you post

• The team triages new posts daily.
• If we accept it, the post moves from Open to Planned on the roadmap. If we ship it, it moves to Shipped and shows up on the changelog.
• You'll get an email if you opted into status notifications when you signed up.