1. washingtonpost.com  Introduction  Who we are - four very different sites –washingtonpost.com –budgettravelonline.com –newsweek.com –slate.com

6. washingtonpost.com CMS  Publish multiple sites from same CMS –washingtonpost.com / budgettravelonline.com  Custom built Content Management System  Largely automated

8. washingtonpost.com - CMS  CMS is a hybrid of “baking” and “frying” –All content is rendered statically by the CMS and then pushed out to live WWW site Better performance Improved search engine optimization –Template driven – templates control the look and feel

9. Article Example

10. Dynamic Application – “Fried” Example

11. Content Storage  Database storage –All article content stored in database –Multimedia stored outside of DB with metadata in database –Articles stored as plain text. Formatting done by templates

12. CMS Challenges –Managing multiple sites –Performance CMS performance & site performance –Dynamic site features Content is rendered statically. This can be a challenge for dynamic applications

13. Managing Multiple Sites  Database tracks content via a context column  Templates defined for each site  Challenge to support dynamic site applications –“E-mail a friend” application is now “site aware”

14. CMS Performance  Content constantly coming in from feeds and staff –Publish an average of 5,000+ items per day –Amount of content continues to increase –Content archive continues to grow

15. Site Performance  RSS traffic continues to grow –Aggregators and clients all behave differently  Page weight –Impact on bandwidth usage and cost –Impact on page load time

16. Bandwidth Impact of Simple RSS Change

17. Dynamic Applications  Dynamic applications –CMS and WWW site in different locations –Replicate necessary data for site applications –Content stored in database and then retrieved by dynamic applications on site such as “e-mail an article”, WAP, mywashingtonpost.com, etc.

19. mobile.washingtonpost.com

20. www.mywashingtonpost.com

21. Future Challenges  Future challenges –Increased demand for dynamic features – personalization, etc. –Increased demand for rich media –Sharing content across properties

22. Thank You! chris.contakes@washingtonpost.com