NYCPHP Meetup

[Joey Derrico]

Contrary to popular belief of many there is no perfect solutions. Other 
then my blog (wordpress) I have never used a non custom CMS. However, 
despite the potential annoyances/problems of CMS (and frameworks) there 
is one big advantage normally that I can see...the communities that form 
around them which have people who are (normally) willing to help in some 
fashion.



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/bae912ff/attachment.html>