adding better tracking codes and tags

src/content/posts/2020-07-13-graphql-on-azure-part-1-getting-started.md

@@ -3,9 +3,11 @@ title = "GraphQL on Azure: Part 1 - Getting Started"
 date = 2020-07-13T14:45:30+10:00
 description = "Let's get started looking at GraphQL on Azure"
 draft = false
-tags = ["azure", "serverless", "azure-functions"]
+tags = ["azure", "serverless", "azure-functions", "graphql"]
 series = "graphql-azure"
 series_title = "Getting Started"
+tracking_area = "javascript"
+tracking_id = "7129"
 +++
 
 I've done a few posts recently around using GraphQL, especially with [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/?{{<cda>}}), and also [on some recent streams](https://www.youtube.com/channel/UCT1QtGr1IzVPNSF_YMrKCAw). This has led to some questions coming my way around the best way to use GraphQL with Azure.

src/content/posts/2020-07-21-graphql-on-azure-part-2-app-service-with-dotnet.md

@@ -3,9 +3,11 @@ title = "GraphQL on Azure: Part 2 - dotnet and App Service"
 date = 2020-07-21T08:16:33+10:00
 description = "Let's look at how we can create a dotnet GraphQL server and deploy it to an AppService"
 draft = false
-tags = ["azure", "serverless", "azure-functions", "dotnet"]
+tags = ["azure", "serverless", "azure-functions", "dotnet", "graphql"]
 series = "graphql-azure"
 series_title = "App Service with dotnet"
+tracking_area = "dotnet"
+tracking_id = "7129"
 +++
 
 In my [introductory post]({{<ref "/posts/2020-07-13-graphql-on-azure-part-1-getting-started.md">}}) we saw that there are many different ways in which you can host a GraphQL service on Azure and today we'll take a deeper look at one such option, [Azure App Service](https://docs.microsoft.com/azure/app-service/?{{<cda>}}), by building a GraphQL server using dotnet. If you're only interested in the Azure deployment, you can jump forward to [that section]({{<relref "#deploying-to-app-service">}}). Also, you'll find the complete sample [on my GitHub](https://github.com/aaronpowell/appservice-graphql-dotnet/).

src/content/posts/2020-08-07-graphql-on-azure-part-3-serverless-with-javascript.md

@@ -3,9 +3,11 @@ title = "GraphQL on Azure: Part 3 - Serverless With JavaScript"
 date = 2020-08-07T11:08:58+10:00
 description = "Let's look at how we can create a JavaScript GraphQL server and deploy it to an Azure Function"
 draft = false
-tags = ["azure", "serverless", "azure-functions", "javascript"]
+tags = ["azure", "serverless", "azure-functions", "javascript", "graphql"]
 series = "graphql-azure"
 series_title = "Serverless with JavaScript"
+tracking_area = "javascript"
+tracking_id = "7129"
 +++
 
 Last time we look at how to get started with [GraphQL on dotnet]({{<ref "/posts/2020-07-21-graphql-on-azure-part-2-app-service-with-dotnet.md">}}) and we looked at the [Azure App Service](https://docs.microsoft.com/azure/app-service/?{{<cda>}}) platform to host our GraphQL server. Today we're going to have a look at a different approach, using [Azure Functions](https://docs.microsoft.com/azure/functions/?{{<cda>}}) to create run GraphQL in a Serverless model. We'll also look at using JavaScript (or specifically, TypeScript) for this codebase, but there's no reason you couldn't deploy a dotnet GraphQL server on Azure Functions or deploy JavaScript to App Service.

src/content/posts/2020-09-04-graphql-on-azure-part-4-serverless-comsosdb.md

@@ -3,9 +3,11 @@ title = "GraphQL on Azure: Part 4 - Serverless CosmosDB"
 date = 2020-09-04T11:04:32+10:00
 description = "Let's take a look at how to integrate a data source with GraphQL on Azure"
 draft = false
-tags = ["azure", "serverless", "azure-functions", "dotnet"]
+tags = ["azure", "serverless", "azure-functions", "dotnet", "graphql"]
 series = "graphql-azure"
 series_title = "CosmosDB and GraphQL"
+tracking_area = "dotnet"
+tracking_id = "7129"
 +++
 
 A few months ago [I wrote a post]({{<ref "/posts/2020-04-07-using-graphql-in-azure-functions-to-access-cosmosdb.md">}}) on how to use GraphQL with CosmosDB from Azure Functions, so this post might feel like a bit of a rehash of it, with the main difference being that I want to look at it from the perspective of doing .NET integration between the two.

src/content/posts/2020-09-17-graphql-on-azure-part-5-can-we-make-graphql-type-safe-in-code.md

@@ -3,9 +3,11 @@ title = "GraphQL on Azure: Part 5 - Can We Make GraphQL Type Safe in Code"
 date = 2020-09-17T15:21:02+10:00
 description = "We're defining a GraphQL schema with a type system, but can we use that type system for our application?"
 draft = false
-tags = ["azure", "serverless", "azure-functions", "javascript"]
+tags = ["azure", "serverless", "azure-functions", "javascript", "graphql"]
 series = "graphql-azure"
 series_title = "Can We Make GraphQL Type Safe in Code?"
+tracking_area = "javascript"
+tracking_id = "7129"
 +++
 
 I've been doing a lot of work recently with GraphQL on [Azure Functions](https://docs.microsoft.com/azure/functions/?WT.mc_id=servsept20-devto-aapowell) and something that I find works nicely is the schema-first approach to designing the GraphQL endpoint.