Hi guys, sorry for late response. Lots of good proposals and observations here.
First, you are right that this is basically a side job. Don’t get me wrong here, when I say side job I don’t mean less important. We take everything we do seriusly, and sitecake is after all our first born :), but we can’t live out of Sitecake sale and that’s why some things are progessing slow. The lack of funds is also the reason why there’s almost no marketing except few promotion sales and campaigns on few different services (codecanyon among others).
Also, I agree that if we want to speed up development, we need to figure a way to raise more funds. Sitecake from it’s begining has changed several pricing models. We had journey from open source to now days pricing model. Also had experiment with different prices for both whitelabel and non-whitelabel versions. We even had freemium version of sitecake with limited functionality at some point, but current pricing model (with prices we have them now) turned out as best solution so far. But it’s obvisly not good enough.
As for identity crisis, I wouldn’t call it like that, but you are right when you say that we are tryint to walk two paths toward both developers/designers and end users. In last few months we are putting our thoughts on how to distinguish those two paths and which one should we take at the end. So we came up with idea to create SaaS (Sitecake as a Service :)). This path would satisfy designers and developers who would have easy solution for their clients with smaller websites where they woudn’t have to think about server requirements and settings, FTP, charging… They would just need to upload template (or buy it on SaaS platform) and instantiate new sitecake site. This also opens up possibility for designers and developers to sell their templates (and plugins after Sitecake v3) on SaaS platform and it would take some burden of Sitecake core team in regards of support because support tickects would mostly be real issues opened by develeopers and designer with technical knowledge and usage support from end users would be handeled by designers/developers them self. That means less time on support for sitecake core team and more time to focus on main product which is Sitecake CMS. So, Sitecake CMS would remain focus of our development, which is important for all developers and designers who wouldn’t use SaaS.
All that being said, it’s clear that we have an idea of how should we continue from here. Only thing that left to figure out is funding.
For SaaS solution we will try to ensure funds through some kind of sturtup accelerator as SaaS platform would be a new service.
Further development and maintenace of Sitecake CMS would need to fund it self. So what would you say if we would start charging Sitecake CMS per site (domain)? There were mentions of donations, but that wouldn’t be neceserry in that case. I think that @MichaelC is right when say that many designers/developers charge $50 to $100/hr so that would be at least $1000+ per site. Sitecake price in compare to that is preatty small. Designers / developers wouldn’t even need to take that of from what they charge to their client. They would simply offer their clients Sitecake as solution for content editing, and if on our site official price is per site, it would be legitimet to ask your client to pay for that if he want Sitecake integration. We don’t even need to implement any kind of restrictions or checks, but go with our users honesty. As there are more sites with sitecake installed that would mean more funds and more stability and new features and improvements. Most of sitecake users use sitecake on more than one website, so that’s means at least double funding.
So, what do you think?