Update blog post titles, author field, and other metadata

Author: hawkticehurst

blogs/2016/02/01/introducing_insiders_build.md

@@ -1,18 +1,16 @@
 ---
 Order:
-TOCTitle: The Insiders Build
-PageTitle: Introducing the Insiders Build
+TOCTitle: The Insiders build
+PageTitle: Introducing VS Code Insiders
 MetaDescription: insiders build
 MetaSocialImage: /assets/blogs/2016/02/01/opengraph_insiders.png
 Date: 2016-02-01
 ShortDescription: VS Code has its roots in the web (built using TypeScript and Node.js) and one thing we love about cloud based applications is that they are always up to date. Update the service and all of your users are instantly on the latest fixes and features, with no user interaction.
-Author: Chris Dias
+Authors:
+  - name: Chris Dias
+    social: https://twitter.com/chrisdias
 ---
 
-# Introducing the Insiders Build
-
-February 1, 2016 by Chris Dias, [@chrisdias](https://twitter.com/chrisdias)
-
 VS Code has its roots in the web (built using TypeScript and Node.js) and one thing we love about cloud based applications is that they are always up to date. Update the service and all of your users are instantly on the latest fixes and features, with no user interaction.
 
 This is why VS Code has automatic updates on by default. We periodically query the update service to see if a new version is available, download it when ready, and then gently prompt you to restart.

blogs/2016/02/23/introducing-chrome-debugger-for-vs-code.md

@@ -1,17 +1,17 @@
 ---
 Order:
 TOCTitle: Introducing Chrome Debugging
-PageTitle: Introducing Chrome Debugging for VS Code
+PageTitle: Introducing Chrome debugging for VS Code
 MetaDescription: Chrome debugger extension for Visual Studio Code
 Date: 2016-02-23
 ShortDescription: Since the first release of Visual Studio Code, one of our focuses has been to simplify the daily workflow for developers by enabling them to debug their code directly from the editor. We started out with .NET and Node.js debugging, and today we are taking the next step by introducing our Chrome Debugger for Visual Studio Code.
-Author: Andy Sterland
+Authors:
+  - name: Andy Sterland
+    social: https://twitter.com/AndySterland    
+  - name: Kenneth Auchenberg
+    social: https://twitter.com/auchenberg
 ---
 
-# Introducing Chrome Debugging for VS Code
-
-February 23, 2016 by [Andy Sterland](https://twitter.com/AndySterland) and [Kenneth Auchenberg](https://twitter.com/auchenberg)
-
 Since the first release of Visual Studio Code, one of our focuses has been to simplify the daily workflow for developers by enabling them to debug their code directly from the editor. We started out with .NET and Node.js debugging, and today we are taking the next step by introducing our Chrome Debugger for Visual Studio Code.
 
 Our Chrome Debugger allows front-end developers to debug their client-side JavaScript code running inside Google Chrome directly from Visual Studio Code.

blogs/2016/03/07/Feb2016Release.md

@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: February 2016 Release
-PageTitle: Visual Studio February 2016 Release
+PageTitle: February 2016 release
 MetaDescription: Announcing the Visual Studio Code February 2016 Release
 Date: 2016-03-07
 ShortDescription: Announcing the February 2016 Release of VS Code
-Author: Chris Dias
+Authors:
+  - name: VS Code Team
+    social: https://twitter.com/code
 ---
 
-# February 2016 Release
-
-March 7, 2016 by The VS Code Team, [@code](https://twitter.com/code)
-
 Today we are releasing the February 2016 build of Visual Studio Code. This release brings many improvements to your development experience, including:
 
 * **JavaScript**: [Salsa](https://github.com/microsoft/TypeScript/issues/4789) is now the default JavaScript/TypeScript language service, bringing support for React and React Native to VS Code.

blogs/2016/03/11/ExtensionsRoundup.md

@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: Extensions Roundup
-PageTitle: Visual Studio Code Extensions Roundup
+PageTitle: VS Code extensions
 MetaDescription: New, useful, and interesting extensions in Visual Studio Code.
 Date: 2016-03-17
 ShortDescription: New, useful, and interesting extensions in Visual Studio Code.
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
 
-# VS Code Extensions
-
-March 17, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
-
 In November 2015, we open sourced Visual Studio Code and introduced the [extensions API](https://code.visualstudio.com/docs/extensionAPI/vscode-api). The VS Code extensions [Marketplace](https://marketplace.visualstudio.com/VSCode) has over 850 extensions. Many new languages (Go, PowerShell, PHP, Python) and frameworks (Apache Cordova, React Native) are now supported.
 
 We will continue to iterate on improving the API and we would love your [feedback](https://github.com/microsoft/vscode/issues). If you are new to VS Code extensions, check out the [docs](/docs/configure/extensions/extension-marketplace.md) for instructions on finding and installing new extensions. We are invested in empowering the community to make VS Code the world's greatest code editor.

blogs/2016/03/14/Feb2016Recovery.md

@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: February 2016 Recovery Release
-PageTitle: Visual Studio Code February 2016 Recovery Release
+PageTitle: February 2016 recovery release
 MetaDescription: Visual Studio Code February 2016 Recovery Release
 Date: 2016-03-14
 ShortDescription: The February 2016 Recovery Release of VS Code
-Author: Chris Dias
+Authors:
+  - name: VS Code Team
+    social: https://twitter.com/code
 ---
 
-# February 2016 Recovery Release
-
-March 14, 2016 by The VS Code Team, [@code](https://twitter.com/code)
-
 If we find critical issues after a major update, we do what we call a "recovery" release. Today we're updating the February 2016 build with fixes for the following four issues:
 
 - [3903](https://github.com/microsoft/vscode/issues/3903): [js] syntax highlight for 'var' and 'function' not working in Default VS theme

blogs/2016/04/14/vscode-1.0.md

@@ -1,18 +1,16 @@
 ---
 Order:
 TOCTitle: 1.0 Release
-PageTitle: Visual Studio Code 1.0 Release
+PageTitle: Visual Studio Code 1.0!
 MetaDescription: Visual Studio Code releases 1.0.
 Date: 2016-04-14
 ShortDescription: Visual Studio Code releases 1.0.
-Author: PJ Meyer
+Authors:
+  - name: VS Code Team
+    social: https://twitter.com/code
 MetaSocialImage: /assets/blogs/2016/04/14/header.png
 ---
 
-# Visual Studio Code 1.0!
-
-April 14, 2016 by The VS Code Team, [@code](https://twitter.com/code)
-
 ![header graphic](header.png)
 
 Today we’re very proud to release version 1.0 of Visual Studio Code. Since our initial launch one year ago, 2 million developers have installed VS Code. Today, we’re excited to report that more than 500,000 developers actively use VS Code each month.

blogs/2016/05/04/extension-roundup-may.md

@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: Extensions Roundup
-PageTitle: Visual Studio Code Extensions Roundup May 2016
+PageTitle: Extensions roundup
 MetaDescription: New, useful, and interesting extensions in Visual Studio Code for May 2016.
 Date: 2016-05-04
 ShortDescription: New, useful, and interesting extensions in Visual Studio Code.
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
 
-# Extensions Roundup
-
-May 4, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
-
 The Visual Studio Code Extension [Marketplace](https://marketplace.visualstudio.com/VSCode) does a great job of highlighting **Featured**, **Most Popular** and **Newly Added** extensions and we encourage you to browse the site to see what's new and what plug-ins other developers are using. In our extension roundups, we like to call out extensions that we've found interesting and useful.
 
 If you are new to VS Code extensions, check out the [docs](/docs/configure/extensions/extension-marketplace.md) for instructions on finding and installing new extensions.

blogs/2016/05/09/April2016Release.md

@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: April 2016 Release
-PageTitle: Visual Studio April 2016 Release
+PageTitle: April 2016 release
 MetaDescription: Announcing the Visual Studio Code April 2016 Release
 Date: 2016-05-09
 ShortDescription: Announcing the April 2016 Release of VS Code
-Author: Chris Dias
+Authors:
+  - name: VS Code Team
+    social: https://twitter.com/code
 ---
 
-# April 2016 Release
-
-May 9, 2016 by The VS Code Team, [@code](https://twitter.com/code)
-
 Today we are releasing the April 2016 build of Visual Studio Code. This is our first monthly release after our 1.0 announcement last month and we really appreciate your support and feedback.
 
 With this release, we're bringing many improvements to your development experience:

blogs/2016/05/23/evolution-of-insiders.md

@@ -1,19 +1,17 @@
 ---
 Order:
 TOCTitle: Evolution of VS Code Insiders
-PageTitle: Evolution of Visual Studio Code Insiders
+PageTitle: Evolution of VS Code Insiders
 MetaDescription: Evolution of the Visual Studio Code Insiders Build
 MetaSocialImage: /assets/blogs/2016/11/30/opengraph_insiders.png
 Date: 2016-05-23
 ShortDescription: Evolution of the Insiders Build
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
 
-# Evolution of the Insiders Build
-
-May 23, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
-
-Today over five thousand developers use the Visual Studio Code [Insiders Build](https://code.visualstudio.com/blogs/2016/02/01/introducing_insiders_build) for early access to new features and to validate bug fixes. We love the Insiders build because we get valuable feedback and usage insights prior to each Stable release. Thank you for your help!
+Today over five thousand developers use the Visual Studio Code [Insiders](https://code.visualstudio.com/blogs/2016/02/01/introducing_insiders_build) for early access to new features and to validate bug fixes. We love the Insiders build because we get valuable feedback and usage insights prior to each Stable release. Thank you for your help!
 
 Initially, we released an Insiders build once per month, a few days before the Stable release. Over time, we increased the frequency of Insiders builds and today we ship new Insiders builds roughly once a week.
 

blogs/2016/06/27/common-language-protocol.md

@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: The Language Server Protocol
-PageTitle: Common Language Server Protocol
+PageTitle: A common protocol for languages
 MetaDescription: A Common Language Server Protocol for any tool and any language.
 Date: 2016-06-27
 ShortDescription: Common Language Server Protocol
-Author: PJ Meyer
+Authors:
+  - name: VS Code Team
+    social: https://twitter.com/code
 ---
 
-# A Common Protocol for Languages
-
-June 27, 2016 by The VS Code Team, [@code](https://twitter.com/code)
-
 Visual Studio Code is an editor for any developer, no matter what programming language you use.  Between languages bundled in the tool or extensions in the [Marketplace](https://marketplace.visualstudio.com/VSCode), we have support for over [150 languages](/blogs/2016/04/14/vscode-1.0.md).  We’re also committed to developing VS Code in the open, and making the components that power VS Code available and open source.  One of our most notable components is the [Monaco editor](https://github.com/microsoft/monaco-editor), but another technology that powers VS Code is an [open, JSON-based protocol](https://github.com/microsoft/language-server-protocol) that anyone can use to add support for a new programming language to VS Code by implementing a "language server".
 
 ![any developer any language any tool](any-developer-any-language-any-tool.png)