Need help with Arillso projects? Here's how to get support.
Start with our comprehensive documentation:
guide.arillso.io - Complete guides, examples, and API references
Before asking for help, try these resources:
- Project README - Check the specific project's README file
- CHANGELOG - See if your issue is addressed in recent releases
- Closed Issues - Search closed issues for similar problems
- Discussions - Browse GitHub Discussions
For questions, ideas, and community support:
- 💡 Ideas - Share feature requests
- 🙋 Q&A - Ask questions
- 📣 Show and Tell - Share your implementations
- 💬 General - Everything else
For bug reports and specific technical issues:
- Search existing issues first
- Use issue templates when creating new issues
- Provide reproduction steps
- Include version information
For private or sensitive matters:
- General inquiries: [email protected]
- Security issues: [email protected] (see SECURITY.md)
- Business inquiries: [email protected]
When reporting bugs, include:
- Version of the tool/collection
- Operating System and version
- Steps to reproduce the issue
- Expected behavior vs actual behavior
- Error messages or logs
- Minimal reproduction (if possible)
When requesting features:
- Check if it already exists in newer versions
- Search for existing feature requests
- Describe the problem you're trying to solve
- Explain why this would be useful to others
- Consider contributing the feature yourself!
We're a small team, so please be patient:
- Critical Security Issues: 24-48 hours
- Bug Reports: 3-5 business days
- Feature Requests: Reviewed monthly
- Questions: Best effort, usually within a week
Want to help improve Arillso? See CONTRIBUTING.md
- Standards: STANDARDS.md - Development standards and best practices
- Code of Conduct: CODE_OF_CONDUCT.md - Community guidelines
- License: LICENSE - MIT License
Documentation and support are primarily in English.
Thank you for using Arillso! We appreciate your patience and understanding. 🙏