Rounding up the 2020 Community Survey

Our annual Community Survey highlights how the community are using Silverstripe CMS and offers important insight for our product development team. In this post, we round up the key findings from this year’s survey.

We recently carried out our annual Community Survey to gain insight into how the community is using Silverstripe Framework & Silverstripe CMS to see if we're heading in the right direction. This is an important feedback cycle for our product development team as it can influence how we prioritise features.

We’d like to thank everyone who took part in this year’s survey. We heard back from nearly 50 of you and have shared your feedback with the relevant teams here at Silverstripe. We’d also like to congratulate the winners of the Community Survey prize pack—one GitHub shop voucher and two Silverstripe t-shirts.

Summary of findings from the 2019 survey

Silverstripe CMS 4.x upgrades

We’ve asked about upgrades to Silverstripe CMS 4.x, and a higher proportion of responses said they’ve planned or completed “most or all” upgrades (40%). That still leaves a decent portion of CMS 3.x sites out in the wild, which we’re still supporting until mid 2021 (see our roadmap).

What we could do better

Documentation is still a common thread in the responses about what we could do better. This is an open source project and we do encourage in particular the long-standing community members to share their knowledge by improving our docs.

How Silverstripe CMS compares

It’s great to hear that many of you are still on board with the technical direction of Silverstripe CMS and love doing projects with its flexible approach. That being said, the number of responses who would recommend the CMS to a friend or colleague went down slightly (from an NPS of 44 to 25).

A focus on stability and security

Much of the effort of the product developers here in New Zealand over the last while has been spent on ensuring the stability and security of our ~100 commercially supported modules. Maintenance and release management is a big time commitment on this scale. We occasionally spend more than a full-time developer month in fixing, testing, and releasing a single security vulnerability. So we are really grateful to anyone chipping in with their contributions on bug fixes and enhancements.

You can view the results from the survey here.

Make a comment