CakePHP CMS Wildflower
Ich habe schon lange nichts mehr mit CakePHP gemacht, oder über CakePHP gepostet, aber Wildflower sieht ganz spannend aus:
There are hundreds of PHP Content Management Systems. Why would a decently earning freelancer, hacking WordPress to fit any clients need decide to write one from scratch? The reason is CakePHP. When I picked up CakePHP it was a little revolution. The quality of my apps got better, I growed a lot as a coder thanks to it and I did stuff faster. But when the time to build a relative simple client site came, I always resorted to WordPress. You know the classic requirements: content managed pages, some news section. Every client also throws something specific into the mix, like a booking form, availability calendar a page pulling RSS from somewhere… I always had a hard time coming back from happy baking to plugin fixing and hacking together procedural PHP. Don’t get me wrong, WordPress is great and it has and will have it’s huge user base. But we Cakers know better, don’t we?
So what does a programmer do when he’s not comfortable with the tool he uses? He programs a new one. It’s slightly more than a year that I started a project called Wildflower. The tag line is A CakePHP CMS.
via debuggable

