NYCPHP Meetup

[Peter Becker]

OK, so this last conversation begins to touch on the one I've had with 
my development team.  I know how easy it is for programmers (I'm more 
like a lowly PM / IT director) to claim that there's not too much to 
just writing your own, and then watch as revs get burned debugging and 
getting to the point of real usability by anyone but someone that knows 
all the quirks (undocumented functions in some lingo, hehe).  And that's 
about when I have to ask whether the time spent writing a CMS tool 
actually moves our business forward (part of our core competency) or 
not.  And here the answer is usually no.

In summary I've got the following list below to check out (thank you 
again), and Mitch, thank you for your candor as I know how "religious" 
some folks can get over their technology of choice, particularly if it's 
theirs.
 
And one last question to Kristina, why CakePHP and not Zend?  Is it that 
your team already knows Cake or is their some technical preference?

http://www.silverstripe.com/

http://modxcms.com/ 

http://www.Vork.us

http://www.steercms-project.org/



Kristina Anderson wrote:
>   
>> ummm, from my experience, in the end it is REALLY easy to just write 
>>     
> your
>   
>> own CMS. You can trash 98% of what the bloated CMS packages out there 
>>     
> give
>   
>> your. You just don't need it. It's so overkill.
>>
>>
>>
>>     
>
> The ease of doing it from scratch varies depending on the complexity of 
> both the site's front end, and the internal editorial/content approval 
> processes that need to be provided, and of course as usual you have IT 
> managers who are convinced that "doing it with frameworks" will save 
> tons of time and money.
>
> I've also had the experience of debugging and stabilizing some 
> extremely poorly designed written-from-scratch PHP CMSes which lacked 
> basic stuff like proper edit-mode handling and whose UIs were almost 
> impossible for the end-users to understand...
>
> So while rolling your own CMS is certainly a viable option, these 
> frameworks offer a lot of advantages even if they are somewhat bloated 
> with idiotic features.  I'm also in a position where this architecture 
> was "decided upon" by persons with no actual experience doing things 
> this way...which is where the proof-of-concept comes in.  We may do a 
> 180 if required.
>
> Kristina
> _______________________________________________
> New York PHP Users Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/Show-Participation
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20091025/aa72586d/attachment.html>