GitHub Issues Are Now the Main Feedback Channel for Evolution CMS

This post matters because it changed how project communication was expected to work. Instead of scattering bug reports, feature ideas, and workflow suggestions across Telegram chats, the team explicitly asked people to create GitHub Issues as the main record of technical feedback.

That is a healthy shift for any project that wants to scale its maintenance process. Chat is great for quick discussion, but it is a poor long-term backlog. Issues make requests searchable, linkable, triageable, and easier to prioritize publicly.

Why this matters for the community

• Feature requests become easier to track and revisit.
• Bug reports are less likely to get lost in fast-moving chats.
• The roadmap becomes more transparent for contributors and users.

The original post also shared lightweight templates for feature requests and bug reports, which is exactly the kind of process signal that deserves a permanent place in the blog archive.

Source: Telegram post and GitHub Issues.