From fdbc9c6d6aa038d430b9abb78a166085d30a66b3 Mon Sep 17 00:00:00 2001
From: tparnell <tparnell@cargurus.com>
Date: Tue, 22 Jan 2019 09:07:40 -0500
Subject: [PATCH] fix external links

---
 src/TerribleDev.Blog.Web/MarkExtension/ExternalLinkParser.cs    | 2 +-
 .../Posts/Building-dotnet-core-apps-and-packages-with-gulp.md   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/TerribleDev.Blog.Web/MarkExtension/ExternalLinkParser.cs b/src/TerribleDev.Blog.Web/MarkExtension/ExternalLinkParser.cs
index d6c2afe..713987c 100644
--- a/src/TerribleDev.Blog.Web/MarkExtension/ExternalLinkParser.cs
+++ b/src/TerribleDev.Blog.Web/MarkExtension/ExternalLinkParser.cs
@@ -63,7 +63,7 @@ namespace TerribleDev.Blog.Web.MarkExtension
             private void RenderTargetAttribute(Uri uri, HtmlRenderer renderer, LinkInline linkInline)
             {
 
-                linkInline.SetAttributes(new HtmlAttributes() { Properties = new List<KeyValuePair<string, string>>() { new KeyValuePair<string, string>("target", "_blank") } });
+                linkInline.SetAttributes(new HtmlAttributes() { Properties = new List<KeyValuePair<string, string>>() { new KeyValuePair<string, string>("target", "_blank"), new KeyValuePair<string, string>("rel", "noopener"),  } });
 
             }
         }
diff --git a/src/TerribleDev.Blog.Web/Posts/Building-dotnet-core-apps-and-packages-with-gulp.md b/src/TerribleDev.Blog.Web/Posts/Building-dotnet-core-apps-and-packages-with-gulp.md
index 3a5df5a..d16a599 100644
--- a/src/TerribleDev.Blog.Web/Posts/Building-dotnet-core-apps-and-packages-with-gulp.md
+++ b/src/TerribleDev.Blog.Web/Posts/Building-dotnet-core-apps-and-packages-with-gulp.md
@@ -7,7 +7,7 @@ tags:
 - docker
 ---
 
-Here we are, its 2017 dotnet core is out, and finally dotnet has a proper cli. In a previous post [we explored the new cli](http://blog.terribledev.io/Exploring-the-dotnet-cli/). In short you can use the dotnet cli to build, test, package, and publish projects. However sometimes just using the cli is not enough. Sometimes, you land in a place where you have many projects to compile, test, and package. 
+Here we are, its 2017 dotnet core is out, and finally dotnet has a proper cli. In a previous post [we explored the new cli](/Exploring-the-dotnet-cli/). In short you can use the dotnet cli to build, test, package, and publish projects. However sometimes just using the cli is not enough. Sometimes, you land in a place where you have many projects to compile, test, and package. 
 <!-- more -->
 
 You sometimes need a more complex tool to help you manage your versions, and set the right properties as part of your builds. This is where a tasking system like [gulp](http://gulpjs.com/) can help. Now gulp is not the only task engines. There are Rake, Cake, MSBuild, etc. Plenty to pick from. I personally use gulp a lot, because I'm a web developer. I need a JS based system, to help me run the [babels](https://babeljs.io), and [webpacks](https://webpack.github.io/docs/) of the world.