Feedback & Analytics
User feedback system and documentation analytics for PEACHY bot
Documentation Feedback
Your feedback helps us understand what's working well and what needs improvement. Every response is reviewed by our team to make the documentation better for everyone.
Was this page helpful?
Need immediate help? Join our Discord community for real-time support.
Community Feedback Summary
Here's how the community has been rating and responding to our documentation:
Total Responses
Average Rating
Found Helpful
Common Issues
Recent Feedback
Love the detailed explanations!
Could use more examples
Very helpful guide
How We Use Your Feedback
📊 Continuous Improvement
- Weekly Reviews: All feedback is reviewed weekly by our documentation team
- Priority Updates: Most commonly reported issues are addressed first
- Content Updates: Feedback directly influences new content creation
🎯 What We Track
- Page Helpfulness: Which pages are most/least helpful
- User Ratings: Overall satisfaction with documentation quality
- Common Issues: Recurring problems that need attention
- Feature Requests: Suggestions for new documentation features
📈 Recent Improvements Based on Feedback
- Added More Examples: 67% increase in code examples after user requests
- Improved Mobile Experience: Complete mobile redesign based on feedback
- Better Search: Enhanced search functionality due to navigation complaints
- Clearer Commands: Rewritten command descriptions for better clarity
Types of Feedback We Value
✅ Most Helpful Feedback
- Specific Issues: "The example for /daily command is outdated"
- Missing Information: "Could you add info about permission requirements?"
- Improvement Suggestions: "A video tutorial would be helpful here"
- User Experience: "This page loads slowly on mobile"
📝 How to Give Great Feedback
- Be Specific: Point out exactly what's confusing or helpful
- Include Context: Mention your experience level or use case
- Suggest Solutions: If you see a problem, suggest how to fix it
- Be Constructive: Focus on how to make things better
Feedback Categories
🎯 Clarity
Issues with understanding or confusing explanations
- Unclear instructions
- Confusing terminology
- Missing context
📚 Examples
Requests for more or better examples
- Missing code examples
- Real-world use cases
- Step-by-step tutorials
✅ Accuracy
Information that's outdated or incorrect
- Wrong command syntax
- Outdated screenshots
- Incorrect information
🧭 Navigation
Issues finding information or moving around the docs
- Hard to find pages
- Poor search results
- Broken links
📱 Mobile Experience
Problems using the docs on mobile devices
- Layout issues
- Hard to tap buttons
- Slow loading
🔧 General
Other feedback that doesn't fit specific categories
- Feature requests
- Overall impressions
- Suggestions
Response Commitment
⚡ Quick Issues (Fixed within 1-3 days)
- Broken links
- Spelling/grammar errors
- Obvious mistakes
🔧 Standard Updates (Fixed within 1-2 weeks)
- Missing examples
- Unclear explanations
- Content organization
🏗️ Major Changes (Planned for future releases)
- New page sections
- Feature additions
- Complete rewrites
Privacy & Data
🔒 What We Collect
- Page ratings and helpfulness votes
- Anonymous feedback comments
- General usage analytics
- No personal information
🛡️ Data Protection
- All feedback is anonymous
- No tracking across other websites
- Data used only for documentation improvement
- Compliant with privacy regulations
Get Involved
💬 Join the Discussion
- Discord Community - Real-time feedback and discussion
- GitHub Issues - Technical suggestions
🤝 Contribute Directly
- Submit documentation pull requests
- Suggest new content topics
- Help with translations
- Share your PEACHY server setups
Your feedback makes PEACHY's documentation better for everyone. Thank you for taking the time to help us improve!