Analyze content performance reports and recommend actions

[BillWagner]

There are two reports we'll use to determine actions for different areas of our content:

• Content performance
• Low / No page views

Possible actions to recommend may be:

• Correcting metadata: The default article type when content was migrated was "article" or "conceptual". That may not be accurate in all cases where it is used.
• Archiving outdated content: Some low page view content may need to be archived as it only applies to outdated versions.
• Edit pass: Some content may need a general update.

Top level folders to examine:

• Architecture
• Azure
• core
• csharp
• devops
• framework
  • additional-apis (these are necessary for compliance and already marked as managed-reference)
  • app-domains
  • configure-apps (set ms.topic to reference for file-schema subfolder; archive WIF reference)
  • cross-platform
  • data
  • debug-trace-profile
  • deployment
  • get-started
  • install
  • interop
  • mef
  • migration-guide
  • misc
  • net-native (Note: This is slated to be moved to the Windows repo)
  • network-programming
  • performance
  • reflection-and-codedom
  • resources
  • tools
  • ui-automation
  • unmanaged-api
  • wcf
  • whats-new
  • windows-services
  • windows-workflow-foundation
• fsharp
• fundamentals
• iot
• standard
• visual-basic

Check off any folder as you start working on it so we don't duplicate efforts. Unassign yourself when you've finished your areas.

This issue is scoped to the investigation of each area. This issue is addressed when we've created issues in the improve content performance project for:

• Updated metadata tags or created an issue in the improve content performance project to update metadata tags.
• Added a recommendation for archiving articles in the tracking spreadsheet.