Community and Support

VeloCMS is a small platform at an early stage. That means the people who build plugins and themes have direct access to the people who built VeloCMS — there's no support queue or corporate intermediary. If you're stuck, you get a real answer, not a link to a doc you already read.

Discord

The VeloCMS developer Discord has channels for plugin questions, theme development, SDK feature requests, and general discussion. The founder and core contributors are active in the #developer-support channel. Response times in business hours are usually under 2 hours.

Join at: discord.gg/velocms

GitHub Discussions

For feature requests, SDK design questions, and longer-form technical proposals, use GitHub Discussions at github.com/muharremyurtsever/velocms/discussions. If you're proposing a change to the plugin SDK API surface, start with a discussion thread before writing a formal RFC — it saves time if the direction isn't viable.

Monthly office hours

The first Thursday of every month at 17:00 UTC, the founder runs a 45-minute open office hours session on Discord voice. Topics: plugin feedback, SDK roadmap, marketplace policy questions, anything you want to discuss. Sessions are recorded and posted to the Discord #office-hours-recordings channel.

RFC process

Significant changes to the plugin SDK — new hook types, capability additions, manifest schema changes, breaking changes to the CLI — go through a lightweight RFC process. The template is at docs/rfcs/0001-template.md in the repository. Fork the repo, copy the template, fill it in, and open a pull request. The RFC stays open for at least 14 days of community comment before a decision is made.

Minor additions (adding a new optional manifest field, a new hook that doesn't affect existing plugins) do not need a formal RFC — a GitHub Discussion thread with a concrete proposal is enough.

Reporting issues

Bug reports for the VeloCMS platform go to GitHub Issues. For security vulnerabilities, email [email protected] instead of opening a public issue. See the Security Guidelines for responsible disclosure details.