Add internal links to updated headless CMS article (#17517)

Author: hashimwarren

docs/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/index.md

@@ -94,7 +94,7 @@ repo.
 
 # Solution: Contentful + Gatsby
 
-Contentful is a hosted headless CMS with a fantastic user experience. It’s
+Contentful is a hosted [headless CMS](/docs/headless-cms/) with a fantastic user experience. It’s
 similar to having a backend like Wordpress, but you are fully responsible for
 the frontend layer. The beauty of Contentful is threefold.
 

docs/blog/2018-02-16-bright-future-for-the-web/index.md

@@ -24,7 +24,7 @@ It was for those reasons that I was hesitant to pull the trigger on a static sit
 
 One day after airing my grievances about the current state of static site generators on Slack a fellow developer recommend that I check out Gatsby. Gatsby is yet another static site generator but what really set it apart for me was how it was built with [React](https://reactjs.org/) and emphasized a rich plugin system. This was a big plus for me as I was itching to learn more about React and the plugin system alleviated some initial pain that I would have had dealing with mundane tasks. Out of the box you get a fantastic development environment with live reloading that required almost no configuration. With Gatsby specific plugins and React components it can handle pretty much anything you throw at it.
 
-Next came integrating the statically generated site with data stored in a CMS. Again Gatsby was well suited for this and I was able to easily integrate with Contentful via the [gatsby-source-contentful](/packages/gatsby-source-contentful/) plugin. Contentful is an example of a headless CMS, meaning that is is not tied to any particular technology or language. Contentful allows you to store content using a pleasant user interface and it can then output the data via an API. Best of all Contentful puts you in the driver seat and lets you define your own content model however you see fit. Think [WordPress Advanced Custom Fields](https://www.advancedcustomfields.com/) on steroids. With the content stored in Contentful Gatsby then uses the Contentful API along with the awesome power of [GraphQL](http://graphql.org/) to query data at build time. Cool stuff!
+Next came integrating the statically generated site with data stored in a CMS. Again Gatsby was well suited for this and I was able to easily integrate with Contentful via the [gatsby-source-contentful](/packages/gatsby-source-contentful/) plugin. Contentful is an example of a [headless CMS](/docs/headless-cms/), meaning that is is not tied to any particular technology or language. Contentful allows you to store content using a pleasant user interface and it can then output the data via an API. Best of all Contentful puts you in the driver seat and lets you define your own content model however you see fit. Think [WordPress Advanced Custom Fields](https://www.advancedcustomfields.com/) on steroids. With the content stored in Contentful Gatsby then uses the Contentful API along with the awesome power of [GraphQL](http://graphql.org/) to query data at build time. Cool stuff!
 
 The final piece of the puzzle was determining where to host the website. I had recently experimented with Netlify on a somewhat [pointless website for my dog](https://www.doggoforhire.com/) and I was impressed by its ease of use and how they offered a fully featured developer tier for free. In no time I was able to get my Gatsby powered website up and running on Netlify. Then with the help of webhooks I was able to have Contentful tell Netlify to “rebuild” the website whenever a new post was published. Finally with Netlify’s form handling functionality I hooked up a contact form all without a single line of backend code or even a database.
 

docs/blog/2018-04-10-how-to-handle-comments-in-gatsby-blogs/index.md

@@ -48,7 +48,7 @@ You could link your comment form to an email address. Then you could copy and pa
 
 ## Crazy
 
-There are many other options. Some crazier than others. You could push comments to WordPress. Then pull them from WordPress into Gatsby at build time. Or push them to a headless CMS. Via a serverless setup maybe.
+There are many other options. Some crazier than others. You could push comments to WordPress. Then pull them from WordPress into Gatsby at build time. Or push them to a [headless CMS](/docs/headless-cms/). Via a serverless setup maybe.
 
 You could create a comment form. Then have it generate a mailto link. Then people email you the comment. Then you copy and paste it into Git. Or the mailto link points to a service like mailgun. Then incoming emails turn into webhooks. Then forward to serverless. Then land as pull requests.
 

docs/blog/2018-04-27-building-eviction-free-nyc-with-gatsbyjs-and-contentful/index.md

@@ -84,7 +84,7 @@ perfect fit for a number of reasons:
 System](https://en.wikipedia.org/wiki/Content_management_system), or CMS.
 Traditional CMS platforms, like WordPress or Drupal, allow authors and editors
 to easily create websites and publish content such as text articles, image, or
-video embeds. A headless CMS takes those publishing features (and the easy admin
+video embeds. A [headless CMS](/docs/headless-cms/) takes those publishing features (and the easy admin
 tools that come with them) and additionally gives you total flexibility as to
 how the website itself is constructed.
 

docs/blog/2018-06-18-why-narative-loves-gatsby/index.md

@@ -33,7 +33,7 @@ Gatsby does not only allow us to deliver fast websites, it has also sped up our
 
 # Separation between view and data layers
 
-Many popular CMS tools are tightly coupled to their source of data. Gatsby offers a clear separation between the data and view layer building on top of the Headless CMS principles. The advantage for Narative is that we can develop without CMS lock-in such as WordPress. If our team decides to go with a new view layer the migration would be less painful than migrating all the data as well. Often times flexibility in software means more complexity to manage but in this case the flexibility is in the right spots where it reduces complexity.
+Many popular CMS tools are tightly coupled to their source of data. Gatsby offers a clear separation between the data and view layer building on top of the [headless CMS](/docs/headless-cms/) principles. The advantage for Narative is that we can develop without CMS lock-in such as WordPress. If our team decides to go with a new view layer the migration would be less painful than migrating all the data as well. Often times flexibility in software means more complexity to manage but in this case the flexibility is in the right spots where it reduces complexity.
 
 We pass this flexibility on to our partners. They are able to manage their data while _our team is able to deliver an excellent product on top of their existing infrastructure. This has made our solutions to revamping legacy projects even stronger than before_.
 

docs/blog/2018-08-13-using-decoupled-drupal-with-gatsby/index.md

@@ -17,7 +17,7 @@ Take a look at the source code of [the official Gatsby + Drupal example site](ht
 
 [A delicious Gatsby + Drupal site](https://using-drupal.gatsbyjs.org/)
 
-Using Drupal as a headless CMS with Gatsby is a great way to get an enterprise-quality CMS for free, paired with a great modern development experience and all the benefits of the JAMstack, like performance, scalability, and security.
+Using Drupal as a [headless CMS](/docs/headless-cms/) with Gatsby is a great way to get an enterprise-quality CMS for free, paired with a great modern development experience and all the benefits of the JAMstack, like performance, scalability, and security.
 
 It only takes a few steps to use Gatsby with Drupal as a headless CMS (also known as decoupled Drupal).
 

docs/blog/2018-1-18-strapi-and-gatsby/index.md

@@ -67,7 +67,7 @@ Note: Within the content below we provide links that open a running _localhost_
 
 ### 1. Introduction
 
-This video series will take you step by step through creating a blog in Gatsby and teach you how to connect it to the open sourced headless CMS - Strapi.
+This video series will take you step by step through creating a blog in Gatsby and teach you how to connect it to the open sourced [headless CMS](/docs/headless-cms/) - Strapi.
 
 <iframe
   width="1206"

docs/blog/2018-1-24-creative-software-destruction-new-presentation-layer/index.md

@@ -41,7 +41,7 @@ It is trite but true to say that every company is becoming a software company. T
 
 We now live in a world of cheap compute and storage, cloud/edge capabilities, and generally fast and pervasive network coverage. So it seems the time has come to dramatically improve the presentation layer. In this world, for instance, running traditional web servers and web content management systems may not make sense anymore. It is incredibly inefficient to have a web server talking to a content management system to pull information, create a response page and send it back to the user. Serverless is gaining interest in terms of the backend architecture, so why not apply a similar approach to the presentation layer?
 
-For developers, there has always been rapid evolution in the area of presentation layer languages and frameworks. With the backing of Facebook (and fixing the open source licensing!), React may finally unify mobile and web client development. Developers have also been actively adopting API-driven headless CMS solutions. Another Facebook technology called GraphQL could provide a unified abstraction to backend data and services.
+For developers, there has always been rapid evolution in the area of presentation layer languages and frameworks. With the backing of Facebook (and fixing the open source licensing!), React may finally unify mobile and web client development. Developers have also been actively adopting API-driven [headless CMS](/docs/headless-cms/) solutions. Another Facebook technology called GraphQL could provide a unified abstraction to backend data and services.
 
 Based on these new technologies, it seems that we can move to a new serverless presentation layer architecture with pre-built JavaScript code served from cloud/edge caches talking directly to backend or third-party microservices. Web and content management servers are no longer runtime components and instead, there is a process to build and deploy static or pre-compiled experiences. This new serverless architecture provides a number of dramatic improvements over the current approach, including:
 

docs/blog/2018-10-10-unbundling-of-the-cms/index.md

@@ -31,7 +31,7 @@ Best-of-breed products have emerged to provide top-notch alternatives in each of
 
 One popular, paywalled, news site that currently stores all content and data in Drupal 7 is migrating to a microservices setup. They’ll handle stories in [Wordpress](https://wordpress.org/), store video in [JWPlayer](https://www.jwplayer.com/), and user data in [Auth0](https://auth0.com/). They’re doing development in React and using [Segment](https://segment.com) for analytics, [Stripe](http://stripe.com) for payments and [Recurly](https://recurly.com/) for subscriptions.
 
-Another digital consumer brand moved from using Sitecore as a content and development platform to using [Contentful](https://www.contentful.com/) as a headless CMS, [Yotpo](https://www.yotpo.com/) for user-generated content -- primarily reviews, while development transitioned to React to provide a modern look and feel.
+Another digital consumer brand moved from using Sitecore as a content and development platform to using [Contentful](https://www.contentful.com/) as a [headless CMS](/docs/headless-cms/), [Yotpo](https://www.yotpo.com/) for user-generated content -- primarily reviews, while development transitioned to React to provide a modern look and feel.
 
 <figure>
   <img alt="The modularization of the CMS" height="400" src="./modular-cms-architecture.png" />
@@ -51,7 +51,7 @@ Enterprises who have purchased these CMS solutions are left asking themselves on
 <figure>
   <img alt="The modularization of the CMS" height="400" src="./headless-cms-landscape.png" />
   <figcaption>
-   The headless CMS landscape
+   The [headless CMS](/docs/headless-cms/) landscape
   </figcaption>
 </figure>
 

docs/blog/2018-10-11-rise-of-modern-web-development/index.md

@@ -84,4 +84,4 @@ Modern web development frameworks like React and Angular are the latest step tra
 
 In the next blog post, [Why Mobile Performance is Crucial](/blog/2018-10-16-why-mobile-performance-is-crucial), we’ll move on to the final piece of the changing content landscape puzzle.
 
-We'll discuss how growing smartphone usage both in the US and globally has made mobile performance crucial -- as well as suddenly easier to optimize in the Headless CMS world. We’ll also explore two modern, complementary trends for improving web performance and how website teams can get the best of both out of the box.
+We'll discuss how growing smartphone usage both in the US and globally has made mobile performance crucial -- as well as suddenly easier to optimize in the [headless CMS](/docs/headless-cms/) world. We’ll also explore two modern, complementary trends for improving web performance and how website teams can get the best of both out of the box.

docs/blog/2018-10-18-creating-compelling-content-experiences/index.md

@@ -63,7 +63,7 @@ The challenge for website teams is: how to achieve this without a lot of costly,
 
 The answer: choose a content mesh. A content mesh:
 
-- pulls in data from your headless CMS systems
+- pulls in data from your [headless CMS](/docs/headless-cms/) systems
 
 - enables you to develop in your preferred UI library while providing website tooling
 

docs/blog/2018-12-19-gatsby-scales-with-expertise-and-scope/index.md

@@ -16,7 +16,7 @@ In any scenario, this individual of disparate experience and expertise was able
 
 I myself am even an example of this general scaling idea. I began my career doing UI design, and have since been doing HTML, CSS, and JavaScript for several years now. As my skills have broadened, so too have they improved and scaled by adding Gatsby to my go-to toolchain.
 
-In this post, I want to explain how Gatsby led me into learning React and how your Gatsby project can scale by considering my [personal site](https://www.lekoarts.de/en) and experience, as an example. Gatsby seamlessly scales from basic React usage to complex React patterns, from basic Markdown to full-featured headless CMS — Gatsby scales with your expertise and scope.
+In this post, I want to explain how Gatsby led me into learning React and how your Gatsby project can scale by considering my [personal site](https://www.lekoarts.de/en) and experience, as an example. Gatsby seamlessly scales from basic React usage to complex React patterns, from basic Markdown to full-featured [headless CMS](/docs/headless-cms/) — Gatsby scales with your expertise and scope.
 
 ## The beginnings
 

docs/blog/2018-12-19-kentico-cloud-and-gatsby-take-you-beyond-static-websites/index.md

@@ -19,7 +19,7 @@ The great presentation by Callum MacDonald explained basic Gatsby features and p
 
 ## Why static site?
 
-One of the websites in our company stack is [Kentico Advantage](http://bit.ly/2T0ynXJ). It is a content-oriented website where we provide our customers with our own methodology on how to build amazing and successful websites with traditional CMS. The website was originally also built on top of a traditional CMS until we switched to MVC during this year. We did that to be able to use a headless CMS as content storage and drop all the pieces that required maintenance like the database server. The business logic was in the MVC layer and we hosted the front-end on Microsoft Azure.
+One of the websites in our company stack is [Kentico Advantage](http://bit.ly/2T0ynXJ). It is a content-oriented website where we provide our customers with our own methodology on how to build amazing and successful websites with traditional CMS. The website was originally also built on top of a traditional CMS until we switched to MVC during this year. We did that to be able to use a [headless CMS](/docs/headless-cms/) as content storage and drop all the pieces that required maintenance like the database server. The business logic was in the MVC layer and we hosted the front-end on Microsoft Azure.
 
 So why did I decide to make Kentico Advantage a static site? A key aspect was performance. We wanted to enable our clients to access the site while being on-site with their customers, using mobile devices and a slow internet connection. I personally wanted the source code to be as little as possible, in a language that everyone would understand. I won't be the only developer on the project for eternity and we tend to have more front-end developers in-house these days. And obviously I did not want to spend months on it. With Gatsby we were fine on all those counts. I was not familiar with React all that much before, but having the site content-oriented and well structured, the implementation was a piece of cake. Saving money on server costs was a nice side-effect, but more on that later.
 

docs/blog/2018-2-6-choosing-a-back-end/index.md

@@ -25,7 +25,7 @@ I found Gatsby a real pleasure. You can find tutorials on their site for setup a
 
 I got the site setup pretty quickly after learning about it. There’s a tonne of tutorials and instructional material around. And you can use as much or as little React as you want. There’s also a [massive list of available plugins](/docs/plugins/), which is only going to grow.
 
-So if you have any experience with React, or if you’re just getting started, this is a great choice. Gatsby doesn’t tell you how your code has to look. In fact it’s setup so you can use Markdown files for pages, but I didn’t fancy that, so I don’t. Simple as that! Likewise, if I want to scale this to build websites for other people, I don’t want to spend ages teaching them how to use Markdown, clone a Git repo and add it to the Git repo. Queue a Headless CMS.
+So if you have any experience with React, or if you’re just getting started, this is a great choice. Gatsby doesn’t tell you how your code has to look. In fact it’s setup so you can use Markdown files for pages, but I didn’t fancy that, so I don’t. Simple as that! Likewise, if I want to scale this to build websites for other people, I don’t want to spend ages teaching them how to use Markdown, clone a Git repo and add it to the Git repo. Queue a [headless CMS](/docs/headless-cms/).
 
 You build your site. You’ve got your Sass, you’ve got your Markdown files (or not), but everything’s blank! So now what? How do we populate it with content?
 

docs/blog/2019-01-14-modern-publications-with-gatsby-ghost.md

@@ -24,7 +24,7 @@ Our latest updates allow you to completely replace the default Handlebars theme
 
 Many developers use static site generators alongside locally stored Markdown files, using a code editor to create content and a GIT workflow to publish. While this works great and is suitable for some sites, it quickly becomes unmanageable for publishers that need to scale, or teams that are not solely developers.
 
-This is where a headless CMS comes in, which provides an admin client for authoring and content management, while still bringing all of the benefits of having a static front-end. Developers can use their preferred stack, and writers have an editor, content scheduling, SEO and much more at their fingertips.
+This is where a [headless CMS](/docs/headless-cms/) comes in, which provides an admin client for authoring and content management, while still bringing all of the benefits of having a static front-end. Developers can use their preferred stack, and writers have an editor, content scheduling, SEO and much more at their fingertips.
 
 When you look at the bigger picture of the [content mesh](/blog/2018-10-04-journey-to-the-content-mesh/), it really starts to feel like an inevitable future for building publishing websites.
 

docs/blog/2019-03-26-what-the-jamstack-means-for-marketing/index.md

@@ -130,7 +130,7 @@ I've already covered some of the benefits of opting to use JAMstack instead of a
 
 **The "downsides":**
 
-- Even if using a headless CMS, there may still be parts of the site that exist entirely in code. So you'll need to get comfortable with editing content and meta data in more than one place.
+- Even if using a [headless CMS](/docs/headless-cms/), there may still be parts of the site that exist entirely in code. So you'll need to get comfortable with editing content and meta data in more than one place.
 - Shipping new marketing material might take a little longer compared to relying on well known methods (depends on your stack and your team, though).
 - New tech means you might stumble upon some exciting new bugs or issues that can take a while to resolve.