Need help with Semantica? You've come to the right place!
Start with our comprehensive documentation:
- Getting Started - Quick start guide
- Concepts - Core concepts
- API Reference - Complete API docs
- Cookbook - Interactive tutorials
- FAQ - Frequently asked questions
Best for: General questions, feature discussions, and getting help
Best for: Real-time chat and quick questions
Best for: Bug reports and feature requests
- Check the documentation - Your question might already be answered
- Search existing issues - Someone might have asked the same question
- Review the cookbook - Examples might help
- Check the FAQ - Common questions are answered there
Use our bug report template to report bugs.
Include:
- Clear description of the bug
- Steps to reproduce
- Expected vs actual behavior
- Environment details
- Error messages or logs
Use our feature request template to suggest features.
Include:
- Problem statement
- Proposed solution
- Use cases
- Impact assessment
Do NOT create a public issue for security vulnerabilities.
Instead:
- Email: semantica-dev@users.noreply.github.com
- Subject: [SECURITY] Brief description
- See Security Policy for details
For enterprise support, custom development, or consulting:
- Email: semantica-dev@users.noreply.github.com
- Subject: [ENTERPRISE] Your request
- Community Support: Best effort (volunteer-based)
- Bug Reports: Initial response within 48 hours
- Security Issues: Response within 24 hours
- Enterprise: Contact for SLA details
See our FAQ for answers to common questions.
If you've tried the above and still need help:
- Ask in GitHub Discussions - Community members are happy to help
- Join Discord - Real-time support
- Open an issue - For bugs or feature requests
- Email - For private matters or enterprise support
We're here to help! Don't hesitate to reach out. 🚀