Hey gang, we’ve been getting a lot of interest from customers wanting to migrate away from slow/costly WordPress sites and onto CC + a static site.
I know many of our now 160+ partners (
) are constantly working out how to best explain the benefits of making the move.
We’ve made a first draft of a small slide deck that tries to make the case. I’d love to hear if there’s anything you’d add to the deck. What are the reasons you choose CC + static? How do you explain it to clients?
From my personal perspective, it seems like these are the top reasons:
- It’s easier to build a fast website, which improves SEO
- The stack is easier to maintain (set and forget)
- Simple visual editing is key (this is achievable with something like Elementor, but that often hurts performance)
- Security. No plugins. No database. No updates.
If you find the deck helpful, feel free to use it! I’ll incorporate any feedback I get and keep improving it. Thanks!
Chris
4 Likes
@Timmy_Brown would be keen to hear your take!
1 Like
I’d suggest fixing this grammatical puzzle. 
With CloudCannon’s editing interface is
fully customizable and flexible, which
means an editing experience to what works
for your team
2 Likes
Also, the ‘s’ in ‘URLs’ shouldn’t be capitalized:
Visual editing and preview URLS
2 Likes
Great catch, @Kevin_Yank. Thanks! A bit of a word salad there 
Anything you’d add to the content?
Hi Chris,
I think you could also add items such as:
- Continuous development: adding features and improvements
- Standards based
- Building CloudCannon for accessibility
That’s my understanding of what you are about in addition to the items already included in the deck. I think these points are also worth highlighting. 
2 Likes
Hey Rosemary, it’s been a while. It’s great to hear from you. I hope you are doing well!
Great suggestions. Accessibility is definitely top of mind for many of our new customers, both when it comes to the CMS interface and the website itself.
1 Like
The option to switch CMS systems is a great plus, if you ask me. Happy with your CMS, but not with your website? No problem. Happy with your website, but not with your CMS? No problem either. A CMS that is also responsible for your website logic (like WordPress) is a tangled mess and should be a red flag. I miss that in the deck.
PS. The percentage of hacked WordPress websites is also a great number to include.
2 Likes
Yeah, good call, the lack of vendor lock-in/site portability is a huge selling point.
We’re working on a deck aimed at more technical stakeholders as well, which goes a bit deeper into that and actually also has a WP hack stat (mind the typos–we have a couple of different people collabing on these slides):
3 Likes
Perhaps more for the tech deck, but could be good to make more of a pitch for git and branching workflows.
For example, content editors can collaborate on their own branch all without affecting the live site until ready to publish. While developers can work on new features on their own dev branch without disrupting editors.
Also with version history every change is tracked, so if something breaks or you change your mind, you can easily roll back to previous versions.
I guess that last part isn’t quite so easy right now without the help of a developer.
3 Likes
Another very good suggestion @harrycresswell. And yeah, you’re right, being able to rollback/revert from the CloudCannon UI is definitely something we’re thinking about!
2 Likes
