Websites/Press-Center-Consolidation/Development: Difference between revisions

Websites/Press-Center-Consolidation/Development (view source)

Revision as of 21:22, 31 January 2012

1 byte added , 31 January 2012

m

→‎Hosting and Serving

Craigcook

Confirmed users

137

edits

@@ Line 4: / Line 4: @@
 ===Hosting and Serving===
-Though the content will be managed via WordPress, we don't wish to inroduce WP to the technology stack that powers the rest of the mozilla.com/org domain (WP is an extremely popular platform and thus a common target for hackers, so we want to keep it isolated in the event of disaster). Furthermore, WP sites are fully dynamic by nature, with every pageload requiring some database queries that can be costly in terms of performance. Serving static pages that don't involve hitting a database is much lighter and more responsive under heavy traffic.
+Though the content will be managed via WordPress, we don't wish to introduce WP to the technology stack that powers the rest of the mozilla.com/org domain (WP is an extremely popular platform and thus a common target for hackers, so we want to keep it isolated in the event of disaster). Furthermore, WP sites are fully dynamic by nature, with every pageload requiring some database queries that can be costly in terms of performance. Serving static pages that don't involve hitting a database is much lighter and more responsive under heavy traffic.
 We'll solve both of these problems at once by hosting the original content offsite at the blog.mozilla.com subdomain (probably blog.mozilla.com/press) and parsing the output to generate static copies that will be hosted at mozilla.org/press. In effect, the official Press Center section of mozilla.org will be a static mirror of the dynamic WP-powered Press Center hosted elsewhere, updated at regular intervals to automatically fetch new content.