Hi As a free-time coder I'd love the idea to contribute to a cakephp cms project. I'd love to this project aggregate the work of a lot of peoples. Presently I see cakephp as having a great core team, some very good coders around in the community, but much less cohesion in the 3rd line where the peoples seems not to be efficient at producing code together.
As a professional web developer I need more than just cake to justify using cake. We kinda have 3 big steps in doing web development. When it is decided that a static site (step 1) has to become dynamic (step 2), we just plug a cms on it. Then some more features are being sold, then we use the cms as a framework, with all its limitations such as a stupid templating system with no php allowed and an un-documented exotic syntax to use, a mandatory web-based coding interface, to name a few. I believe that this situation is very common among web agencies. It actually pisses me off to work this way, but I cant justify the use of cake, because it make really sense at the 3rd step of development. So as a professional web developer I see clearly the benefit of having a little cms on top of cake that would allow me to be a little faster at step 1, with for instance an handy way to generate the navigation menu, to be fast at step 2 with some built-in rich text editing solution, and to have cake under the hand at step 3 when serious coding starts. digital spaghetti wrote: > Hi folks, > > Forgive me for being rather forward with my email here, I'll try to > put my case over as level headed and as thoughtfully as possible, and > please feel free to give back any constructive critisism. Also, > forgive any spelling and grammar - I'm typing this on the way home on > my blackberry, it's the only time I get to write an email this long. > > Through being on the IRC channel, and on here - many a time, someone > new has come along and they are looking for a ready-to-roll > application that they can plonk onto their server and have running. > At the moment, there are a few small apps out there currently being > written by small teams (and even just one coder) such as cheesecake, > bakesale to name a couple, and there are plenty of dead projects in > the trove. > > I want cake to succeed, it's a great framework - but I have to admit, > it took me three tries of coming back to it over the course of a few > month to get the hang of it. I could see it's power, but it took me a > while to get the hand of it. And I'm not the only one. > > What I believe CakePHP needs is a killer app, a CMS that can rival the > others out there, and that gives people the chance to actually see > cakephp in action. Think of it as a pre-packed Cake you get in the > supermarket. RoR has one, Radient CMS - why can't we? I think by NOT > having one, that scares a lot of people off. > > So my proposal is this - along with the primary cake team who are > developing the framework - we create a secondry team to work on an > application that will be this killer app. > > With the creation of this team, we can set about making something that > while it might not suit everyone's needs, it's something that most > people can start off with and build upon (which is something I think > is imporant to note now, think Drupal!). It would have standard > "modules" such as a user system (registration, authorisation, access > levels, etc), a post & comments system, pages (from the db), a menu > system, file upload - and many more. I'm thinking around a level akin > to a default install of Wordpress. > > As well as creating a base level of these modules for people to work > from, I think it would a) drive more people to download and learn > CakePHP as they can see it in action and also so they can expand upon > this base app and b) drive cakephp itself by defining requirments of > the base application, and also provide more components, plugins and > documentaion that can be included into CakePHP itself. And of course > it would help in bug fixing by providing code back to the main > project. > > Now, please don't me wrong - I think everyone should download the > framework and experiment with their own apps, and this "killer app" is > not going to suit all cases, but I think if some of the more senior > members of the community who already have apps out there were to come > together on this and pool their talents, something great could happen. > > If not, then I suppose it's the communitys loss. Personally, I'm > happy to work on my own app, and although progress is admitidly slow, > I certainly wouldn't loose any sleep over it. > > One last thing I would like to say is: convergance, not divergance - I > think that needs to be the motto here > > So folks, now is your time to pipe up with your opinion. If anyone is > interested, then discuss it here and we can start moving forward on > it. If not, then that's fine too. > > Tane > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
