Ian Kallen, Manager of systems and software at Salon.com presented this, um, presentation about their choice of publishing and workflow framework. If you know about these topics already you can quickly skip through nearly half the slides.

His conclusion is to go with Apache, mod_perl and mason over a fairly large range of open source and commercial options.

I whole heartedly agree with nearly all of his reasoning.

However, I think that he missed a great possibility (especially with regards to workflow) when he disregarded the ArsDigita Community System (now OpenACS) with the following silly (and unprofessional) takedown:

Phil Greenspun has spoke extensively but unconvincingly of the virtues of the AOLServer. We don't agree that Tcl is the world's greatest language and Alex seems nice and everything but a good dog doesn't make a good publishing technology.

OpenACS addresses many of his complaints against the other competitors and shares most (not all) of it's flaws with his chosen platform.

mod_perl and mason is a killer combination that I am growing to love, but in situations where OpenACS is an appropriate choice, it can save you 6 months to a year of development time. Seriously.