microsoft · hawkticehurst · Mar 4, 2026
diff --git a/blogs/2016/02/01/introducing_insiders_build.md b/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.

diff --git a/blogs/2016/02/23/introducing-chrome-debugger-for-vs-code.md b/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.

diff --git a/blogs/2016/03/07/Feb2016Release.md b/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.

diff --git a/blogs/2016/03/11/ExtensionsRoundup.md b/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.

diff --git a/blogs/2016/03/14/Feb2016Recovery.md b/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

diff --git a/blogs/2016/04/14/vscode-1.0.md b/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.

diff --git a/blogs/2016/05/04/extension-roundup-may.md b/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.

diff --git a/blogs/2016/05/09/April2016Release.md b/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:

diff --git a/blogs/2016/05/23/evolution-of-insiders.md b/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.
 

diff --git a/blogs/2016/06/27/common-language-protocol.md b/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)

diff --git a/blogs/2016/07/29/extensions-roundup-git.md b/blogs/2016/07/29/extensions-roundup-git.md
@@ -1,15 +1,14 @@
 ---
 Order:
 TOCTitle: Extensions Roundup - Fun with Git
-PageTitle: Visual Studio Code Extensions Roundup - Git August 2016
+PageTitle: Extensions roundup, fun with Git
 MetaDescription: Extensions to super power your Git workflow.
 Date: 2016-08-02
 ShortDescription: Extensions to super power your Git workflow.
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
-# Extensions Roundup - Fun with Git
-
-August 2, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
 
 The first extension I built for Visual Studio Code was called [Git Blame](https://marketplace.visualstudio.com/items?itemName=waderyan.gitblame). It lets you quickly see which developer most recently modified the currently selected line ("blame"). It was simple and effective. Since the time when I built this extension, there have been many more awesome Git extensions added to the VS Code [Marketplace](https://marketplace.visualstudio.com/VSCode). Here are some of my favorite.
 

diff --git a/blogs/2016/08/15/introvideos.md b/blogs/2016/08/15/introvideos.md
@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: Intro Videos
-PageTitle: Visual Studio Code Introductory Videos
+PageTitle: Announcing intro videos
 MetaDescription: We want to help people get going with VS Code. Watch our new introductory videos to jump start your work with VS Code.
 Date: 2016-08-15
 ShortDescription: Watch our new intro videos to jump start your work with VS Code.
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
 
-# Announcing Intro Videos
-
-August 15, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
-
 On the product team, we're constantly trying to make Visual Studio Code better. We spend hours in interviews, usability studies, and interacting with you online.
 
 One theme we hear from users new to VS Code is that they would like more on-boarding material. They want to be able to get up and running with VS Code quickly and be able to take advantage of its powerful features right away.

diff --git a/blogs/2016/08/19/goodbyeuservoice.md b/blogs/2016/08/19/goodbyeuservoice.md
@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: Goodbye User Voice
-PageTitle: Goodbye User Voice
+PageTitle: Goodbye User Voice, hello GitHub Reactions!
 MetaDescription: Visual Studio Code is closing User Voice in favor of GitHub reactions.
 Date: 2016-08-23
 ShortDescription: Visual Studio Code is closing User Voice in favor of GitHub reactions.
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
 
-# Goodbye User Voice, Hello GitHub Reactions!
-
-August 23, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
-
 ## Feedback Channels
 
 Visual Studio Code's [User Voice site](https://visualstudio.uservoice.com/forums/293070-visual-studio-code) has always been the place for the community to suggest and vote on feature requests for VS Code. The ability to see the requests with the top votes or the most activity has allowed us to prioritize the VS Code backlog and deliver many of the top requests over the past 18 months. For example, we’ve added [Extensions](https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/9181439-plugins) (plugins), [Tabs](https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752519-implement-tabs) (tabbed headings) and an [Integrated Terminal](https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752357-integrated-terminal), all because of your feedback and participation in User Voice.

diff --git a/blogs/2016/08/22/introducing-ios-web-debugging-for-vs-code-on-windows-and-mac.md b/blogs/2016/08/22/introducing-ios-web-debugging-for-vs-code-on-windows-and-mac.md
@@ -1,15 +1,14 @@
 ---
 Order:
 TOCTitle: iOS Web Debugging
-PageTitle: Introducing iOS Web Debugging for VS Code on Windows and Mac
+PageTitle: iOS web debugging on Windows and Mac
 MetaDescription: iOS Web Debugging for VS Code on Windows and Mac
 Date: 2016-08-24
 ShortDescription: Today debugging websites running on iOS devices are limited to a subset of developers, as the Safari Web Inspector (Safari DevTools) requires an instance of desktop Safari which only is available for macOS users. With our new debugger we are aiming to change that, as our iOS Web Debugger for Visual Studio Code works both on Mac and Windows.
-Author: Kenneth Auchenberg
+Authors:
+  - name: Kenneth Auchenberg
+    social: https://twitter.com/auchenberg
 ---
-# iOS Web Debugging on Windows and Mac
-
-August 24, 2016 by [Kenneth Auchenberg](https://twitter.com/auchenberg)
 
 ## Update
 

diff --git a/blogs/2016/09/08/icon-themes.md b/blogs/2016/09/08/icon-themes.md
@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: File Icon Themes
-PageTitle: File and Folder Icons in Visual Studio Code
+PageTitle: File and folder icons in VS Code
 MetaDescription: File and Folder Icons in Visual Studio Code
 Date: 2016-09-08
 ShortDescription: The Visual Studio Code Explorer now supports file and folder icons. VS Code ships with two icon themes and more are available on the Marketplace.
-Author: Chris Dias
+Authors:
+  - name: Chris Dias
+    social: https://twitter.com/chrisdias
 ---
 
-# File and Folder Icons in VS Code!
-
-September 8, 2016 by Chris Dias,  [@chrisdias](https://twitter.com/chrisdias)
-
 ## Rebellion. Revolt. Uprising.
 
 These words all describe the first time we added icons to the File Explorer tree in VS Code, back in 2014. [@dmitar-asenov](https://github.com/dimitar-asenov) was an intern in [@egamma](https://github.com/egamma)'s Zurich lab and spent a couple of hours hacking in a basic set of icons because he wanted to differentiate between files and folders when quickly glancing at the tree.

diff --git a/blogs/2016/09/14/js_roundup_1.md b/blogs/2016/09/14/js_roundup_1.md
@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: JavaScript Extensions Part 1
-PageTitle: Visual Studio Code JavaScript Extensions Part 1 Sep 2016
+PageTitle: JavaScript extensions, part 1
 MetaDescription: Essential JavaScript extensions for Visual Studio Code.
 Date: 2016-09-14
 ShortDescription: Essential JavaScript extensions for Visual Studio Code.
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
 
-# JavaScript Extensions Part 1
-
-September 14, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
-
 > This is part one in a series on JavaScript extensions.
 
 I learned JavaScript during an internship in the summer of 2013. Although not a difficult programming language, JavaScript didn't come easy. I used a lightweight editor along with the rest of my team and missed the deep language integration features of Visual Studio (C#) and Eclipse (Java).

diff --git a/blogs/2016/10/31/js_roundup_2.md b/blogs/2016/10/31/js_roundup_2.md
@@ -1,15 +1,14 @@
 ---
 Order:
 TOCTitle: JavaScript Extensions Part 2
-PageTitle: Visual Studio Code JavaScript Extensions Part 2 Oct 2016
+PageTitle: JavaScript extensions, part 2
 MetaDescription: Essential JavaScript extensions for Visual Studio Code.
 Date: 2016-10-31
 ShortDescription: Essential JavaScript extensions for Visual Studio Code.
-Author: Wade Anderson
+Authors:
+  - name: Wade Anderson
+    social: https://twitter.com/waderyan_
 ---
-# JavaScript Extensions Part 2
-
-October 31, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
 
 Visual Studio Code has excellent support for JavaScript out of the box. As with other languages, JavaScript is powered by a language service. The [JavaScript language service](https://github.com/microsoft/TypeScript/wiki/JavaScript-Language-Service-in-Visual-Studio) is implemented by the TypeScript team, allowing JavaScript developers to leverage the best IntelliSense experience.
 

diff --git a/blogs/2016/11/15/formatters-best-practices.md b/blogs/2016/11/15/formatters-best-practices.md
@@ -1,17 +1,15 @@
 ---
 Order:
 TOCTitle: Creating a Formatter Extension
-PageTitle: Creating a Formatter Extension
+PageTitle: Creating a formatter extension
 MetaDescription: Best practices for creating a Visual Studio Code formatter extension.
 Date: 2016-11-21
 ShortDescription: Best practices for creating a Visual Studio Code formatter extension.
-Author: Johannes Rieken
+Authors:
+  - name: Johannes Rieken
+    social: https://twitter.com/johannesrieken
 ---
 
-# Creating a Formatter Extension
-
-November 21, 2016 by Johannes Rieken, [@johannesrieken](https://twitter.com/johannesrieken)
-
 Since its introduction, the Visual Studio Code extension API has provided support for source code formatters. The first language extensions we built, for example TypeScript, C# and Go, used the formatting API. We wrote this blog to explain the best practices for implementing formatters.
 
 VS Code's extension API follows a set of guiding principles. The essence of these principles is that VS Code provides the skeleton and extensions provide the "smarts". The common pattern is for VS Code to provide the UI around a feature and the extensions provide the necessary data to make it shine.