Community & Support
Welcome to the Saint CMS community! Whether you are stuck on a complex deployment, found a bug in the Go engine, or want to show off your new Next.js Studio dashboard, we are here to help.
Because Saint CMS is an open-source project, support is primarily asynchronous and driven by the community on GitHub.
Where to get help
1. Questions & Best Practices
If your code isn’t crashing, but you aren’t sure how to do something, GitHub Discussions is the right place.
Use Discussions for:
- “How do I connect the Studio to a different database?”
- “What is the best way to structure my content models for my specific use case?”
- “How do I run the backend as a background service via systemd?”
- Showcasing projects you have built using the CMS.
2. Bug Reports
If something is genuinely broken, the auto-migration fails, or you are getting unexpected database panics, please open a GitHub Issue.
To help us track down the problem faster, please include:
- Your OS and environment details.
- The exact
npx create-saintcommand or deployment method you used. - The error logs from your terminal.
- Clear steps to reproduce the issue.
3. Feature Requests
Have an idea to make the headless engine even faster or the content management experience more intuitive? We love feature requests.
Search the existing GitHub Issues to see if someone has already suggested it. If not, open a new issue with the enhancement label and describe the problem your feature would solve.
Want to contribute?
If you have fixed a bug or added a feature yourself, we welcome Pull Requests! Check out the README.md guide in the root of the repository for instructions on setting up your local development environment for both the backend engine and the frontend Studio.