We read these. Best format: one idea per topic, so we can track and prioritize each one on its own.
Before posting:
- Search to see if someone already asked if you find it, upvote/reply there instead of starting a new one. Duplicate requests split the signal we need to prioritize.
- Check if it’s intentional behavior in the docs sometimes what feels like a missing feature is a deliberate design choice, and the docs might explain why.
When you post, include:
What’s painful right now?
Describe the actual problem you’re hitting not just the feature you’re picturing. The problem is often more useful to us than the proposed solution.
Who does it affect?
Just you? All learners? Assess orgs?
What should happen instead?
Your proposed fix or improvement.
Any workaround today?
Even a hacky one helps us prioritize. If there’s a good workaround, it usually means this is annoying but not urgent; if there isn’t, that tells us something too.
How much does it matter to you?
Nice-to-have vs. blocking your workflow.
That’s it. We read every one of these, tag and track them internally, and reply when we’ve made a call even if the call is “not right now.” We can’t promise a timeline or that everything gets built, but nothing here goes unread.