Content Development Project Process

Strategy & Planning

Strategy, Sitemap, Wireframes

• When the Strategy & Planning phase of the project begins, the Web Content Manager will create a Keep/Delete content inventory spreadsheet using a site index report of the client’s current website.
  • The client will be asked to use this document to indicate which pages from their current website they want to keep, archive, or delete.
  • The Web Content Manager will present this document as a part of the “What Is Content” presentation, which reviews the content process at a high level and gives the client a chance to start thinking about how they need to organize their team to handle the upcoming workload.
  • The completed document will be due by the start of Implementation Planning.

• When the Sitemap has been approved and the Content Sections and Sitemap Pages & Annotations tabs in the Content Organization Guide have been completed:
  • The Web Content Manager will schedule a meeting with the Digital Strategist and other team members as necessary to review the content scope, Sitemap, Content Organization Guide, and taxonomy needs.
  • The Project Manager will invite the Web Content Manager to all future project status meetings where content is on the agenda.

• When Wireframes are approved, the Web Content Manager will attend the Content Organization Guide Walkthrough (Content Kickoff) meeting with the client.
  • The Web Content Manager will introduce the content development process. This is an opportunity to begin answering client questions about content, set expectations, and start planning with the client before Implementation. Some items that can be addressed:
    • Identifying client-side people who will be creating, reviewing, and approving content
    • Communications and coaching process during content development
    • Cloning the current website or starting from a blank slate (see Implementation Planning below)
    • Content development schedule and deadlines
    • Content Inventory document
    • Starting client on taxonomy creation (if taxonomy will be used)
    • Present Content Organization Guide and Content Tracker.

Implementation Planning

• Before development planning begins, the client will determine whether to clone/copy the current site’s content to the staging website or build the new website as a “blank slate” and reenter older content the client decides to keep.

1. 1. 1. If the current website will be cloned, the following considerations will be addressed as part of Implementation Planning:
         1. The clone date and duration of the subsequent content freeze will be agreed upon with the client and planned within the development and content schedules.
         2. Before the content freeze date, the Web Content Manager will work with the client on developing new content outside of WordPress. An application of the client’s choosing (such as OneDrive, Google Docs, etc.) can be used for this purpose.
         3. Once the current website has been cloned and moved into staging, a content freeze will go into effect.
            1. The client must stop entering new content on the current website OR
            2. Commit to double-entry of new content (in current site and staging site).
         4. After the clone, during the content freeze period, the Web Content Manager will work with the client on developing new content in WordPress per the Implementation process outlined below.
      2. If the new website will be built as a “blank slate,” content development will follow the Implementation process outlined below.

• When development planning begins:
  • The Project Manager will invite the Web Content Manager to all development planning meetings.
  • The Web Content Manager will work with the client to finalize a content schedule based on the development schedule.

Implementation

The following describes one development and release cycle of any duration. If multiple release cycles occur in development, the process described here repeats for each.

• Front- and Back-End Development
  • Designer/Developer build new templates and features
  • Designer/Developer deploy new templates and features to staging site
  • Designer and/or Developer perform QA
  • Designer writes documentation for new page templates and features
• The Web Content Manager will attend a client training session to review documentation and train the client on how to use the new templates and features. The Designer may also attend when training on more complex features is required.
• Content Development
  • Client assumes responsibility for assigning work, writing, reviewing, and approving new content.
  • Web Content Manager helps the client monitor progress and provides content guidance as agreed upon during the Strategy & Planning phase of the project (see Strategy & Planning above).
  • Web Content Manager reports on content progress to the internal team at project status meetings.