Live data from Hacker News

Scoop: A Glimpse Into the NYTimes CMS

open.blogs.nytimes.com

71–76 of 76 posts

Re: Scoop: A Glimpse Into the NYTimes CMS

#71
post #67
post #11

Earlier quoted context omitted.

No. We use a pretty normal ("boring") Java stack with Spring, Hibernate and Jersey. Some of the older components use Struts + JSPs whereas the newer components use Backbone (and related libraries).

Which database? A JDBC one?

scoop uses mysql for its managed repository. we also use mongodb for our published repository that serves our apis to everybody else.

Re: Scoop: A Glimpse Into the NYTimes CMS

#72
post #15

I was always under the impression that they're Django/Python. Can anyone confirm?

The NYT devs consist of several dev groups and a mix of stacks...some which are business-facing/product, and others that are in editorial (i.e. interactive news graphics). On the editorial side, they are one of the few in the news business that were using Ruby/Rails (the vast majority of newsrooms use Python/Django). There's also obviously a primarily-JavaScript group.

See krishy's comment above. It looks like they do not use Ruby/Rails for the CMS for editors, but use Java instead.

Re: Scoop: A Glimpse Into the NYTimes CMS

#73
post #15

Earlier quoted context omitted.

The NYT devs consist of several dev groups and a mix of stacks...some which are business-facing/product, and others that are in editorial (i.e. interactive news graphics). On the editorial side, they are one of the few in the news business that were using Ruby/Rails (the vast majority of newsrooms use Python/Django). There's also obviously a primarily-JavaScript group.

See krishy's comment above. It looks like they do not use Ruby/Rails for the CMS for editors, but use Java instead.

Right...I should've clarified...by "editorial", I meant the team that focuses on the public facing news projects, such as Derek Willis's campaign finance apps and utilities (http://itemizer.herokuapp.com/)...I don't think they do a lot of monolithic-type Rails apps currently, though, at least compared to client-side-heavy projects

Re: Scoop: A Glimpse Into the NYTimes CMS

#74

The CMS is in a renaissance period with Wordpress, Joomla, Drupal and the like falling out of favor. I 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…

Take any normal CMS, cache the html, and you have a static site generator.

Exactly. My favorite static site generator is Varnish.

Re: Scoop: A Glimpse Into the NYTimes CMS

#75

Are there any google docs based CMS's ? Seems like you could offload the editing, saving, tracking changes to google docs - a platform many people seem familiar with now - and then keep the actual CMS to a bare minimum. Have it import the text & spit out a static page even.

That is a very interesting idea, but since NYTimes opensourced their ICE editor, I am not sure what Google Docs would provide.

Re: Scoop: A Glimpse Into the NYTimes CMS

#76
post #75

Are there any google docs based CMS's ? Seems like you could offload the editing, saving, tracking changes to google docs - a platform many people seem familiar with now - and then keep the actual CMS to a bare minimum. Have it import the text & spit out a static page even.

That is a very interesting idea, but since NYTimes opensourced their ICE editor, I am not sure what Google Docs would provide.

Transparent version control, tracking of changes, collaborative editing, familiar interface, familiar workflow (just drop finished articles into this directory to be available to the CMS)
Post reply on HN