Feedback
Your feedback helps us improve. Whether you've spotted an error, found something confusing, or have ideas for new content, we want to hear from you.
Ways to share feedback
Report an error
Found a mistake? Let us know:
- Typos and grammar: Small things that slipped through
- Factual errors: Incorrect information or outdated guidance
- Broken links: Links that no longer work
- Code errors: Bugs in examples or tool functionality
Email [email protected] with:
- The page URL
- What's wrong
- The correct information (if you know it)
Suggest improvements
Have ideas for making content better?
- Clarity: Explanations that could be clearer
- Completeness: Missing considerations or edge cases
- Examples: Better or additional examples that would help
- Organization: Content that would work better structured differently
We especially value feedback from people actively using the materials, as you see gaps we might miss.
Request new content
Looking for something we don't cover? Tell us:
- Topic: What you're looking for
- Context: Why you need it / what problem you're solving
- Priority: How important is this to your work?
We can't add everything, but understanding what practitioners need helps us prioritize.
We track all content suggestions and review them periodically. Addition to the site depends on whether a topic fits our scope, how broadly useful it would be, and our capacity to do it justice. We aim for quality over quantity.
Feedback on specific areas
Guides
For guides, we're particularly interested in:
- Steps that don't work as described
- Missing prerequisites or context
- Techniques that have better alternatives
- Accessibility considerations we've missed
Patterns
For patterns, helpful feedback includes:
- Implementations that cause usability problems
- Accessibility issues with documented approaches
- Platform-specific considerations we haven't covered
- Better examples than the ones we show
Tools
For tools, let us know about:
- Features that would make them more useful
- Bugs or unexpected behavior
- Usability issues with the tools themselves
- Accessibility barriers
Linear
For Linear specifically:
- Measurement accuracy issues
- Missing functionality for common tasks
- Platform compatibility problems
- Documentation gaps
What happens with feedback
- We read everything: Every piece of feedback is seen by someone who can act on it
- We triage: We categorize and prioritize based on impact and feasibility
- We act: High-priority issues get addressed quickly; others are queued for periodic updates
- We update: The changelog notes significant improvements
We don't always reply individually, but know that your feedback contributes to improvements even if you don't hear back.
Community input
We occasionally gather input on specific topics through:
- Email surveys to newsletter subscribers
- Focused questions in the newsletter
- Direct outreach on particular issues
If you'd like to be more involved in shaping content, mention that when you provide feedback.
For error reports that we fix, you might see the change before you hear from us. For suggestions and requests, we track them but may not reply individually. If you've asked a specific question, we'll try to respond.
It varies widely. Error corrections often happen within days. New content can take months depending on scope and priority. We don't provide timelines for suggestions.
We don't maintain a public roadmap. The changelog shows what's been added, but planned work isn't announced in advance.
Not necessarily. Some suggestions take time to address properly, and some don't fit our current priorities. If you're curious about a specific suggestion, feel free to follow up.
Contact
Send feedback to: [email protected]
For security issues, use [email protected].