I'm at work now, and VS2003 is pissing me off by locking project output files and then declaring that it cannot write to those files because "someone" is using them. Dimwit.
So I figured, why not take a break and do something at least semi-useful.
I was browsing around the web and looking at different kinds of content management systems, and compare that to what I'm trying to do with NeutrinoCMS. I must say, the competition in the domain of "regular" CM systems is really tough. If you want to run a site, you pretty much can get all you need. For free. Becoming famous in that domain is virtually impossible (or so it seems to me).
In that view, I'm glad I made the decision to create a CMS for developers. Most of the CM systems I've run into are dumb-end-user oriented. Often though, they have with very complex back-end interfaces and complex administration.
The way I see it, these CMSes are trying to be "the jack of all trades" of a sort, and are bound to fail. The reason why Linux is such a great platform is not because it tries to do everything. Linux makes it possible for you do whatever you want, but it fact, Linux itself does nothing. The real power behind it lies in the huge collection of small tools, each fine tuned to do one thing, and one thing only. Specialization is the key.
I feel the same way about CakePHP. CakePHP just makes it possible for you to code any damn thing you want. The latest RC1 release is unbelievably good. Now it's up to us to create specialized tools.
In the upcoming release of NeutrinoCMS, among other things, I'm planning to optimize pretty much everything (hint: Containable), there will be some bug fixes (comments pagination), Google integration (webmaster tools & analytics), and the star rating.
This is not much, one might say, but bear in mind the single most important concept: simplicity. For those of you who don't read physics books as a hobby, Neutrino is an elementary particle (see Wikipedia entry: Neutrino). NeutrinoCMS, just like neutrino the particle, will not get in your way (yes, even if you use it).
Knowing all this, I'm very interested in developers' opinions. What do you expect from a CMS from developers, for developers? What are the features you miss now? Do you think that smashing things like tickets and software roadmaps into a developers CMS is a good idea? Looking forward to your input..