Start Migrating to v2 of the Content API, Deprecating v1 in December

To better support our developer community, we launched a new and improved v2 version of the Content API in December of last year. At that time, we announced that we would be deprecating v1 of the API on December 13, 2013. This deadline is fast approaching, so we have created a migration guide to help make it as simple as possible to move over.
The v2 API has evolved since last December and now has equivalent endpoints for most of the frequently used v1 API calls. Our migration guide identifies the functional parity for each API and provides equivalent v2 functionality for each v1 endpoint. This document also identifies APIs requiring administrator privileges, APIs without a current replacement in v2, APIs deprecated with v1 and new features introduced in v2. We are here to help make this transition as seamless as possible and will be providing more resources in the coming weeks.