Scoop: A Glimpse Into the NYTimes CMS
open.blogs.nytimes.com
Scoop: A Glimpse Into the NYTimes CMS
1–10 of 76 posts
Re: Scoop: A Glimpse Into the NYTimes CMS
#2Re: Scoop: A Glimpse Into the NYTimes CMS
#3Re: Scoop: A Glimpse Into the NYTimes CMS
#4I believe the CMS is bifurcating into two specialized directions.
Several online publishers are coming out and describing their new, home-grown custom CMS. The features are rich and provide robust, innovative tools across the long-form content lifecycle: writing, editing, and publication. There is special attention to collaboration.
On the other hand, more and more website developers align themselves with the goals and properties of static site generators. SSGs are best suited what I call "malleable" websites.
Thus, I think the way to think about this CMS renaissance is that traditional the CMS tried (and failed) to optimize for both long-form content and the malleable website. As a result, people are sick of trying to patch the traditional CMS with plugin after plugin and instead are simply crafting their own.
Re: Scoop: A Glimpse Into the NYTimes CMS
#5Re: Scoop: A Glimpse Into the NYTimes CMS
#6I could see this as premium wordpress service successfully charging $15 - 25 a month for bloggers.
Re: Scoop: A Glimpse Into the NYTimes CMS
#7Very interesting and cool article, although I wonder what the point of this is? Just a show and tell? Doesn't seem like they're open sourcing it.
Re: Scoop: A Glimpse Into the NYTimes CMS
#8I could see this as premium wordpress service successfully charging $15 - 25 a month for bloggers.
I don't, and it would be too expensive even at $15 imo. But even if something like this had a market there's the problem of the editor, as it uses contenteditable which is at best inconsistent across browser and at worst completely broken. That's also the reason Google Docs dropped it and started doing editing the hard way. As long as you know who uses your software and you can enforce the use of a given browser (as…