Replace 'the Moovweb XDN'

Author: tristanlee85

guides/caching.md

@@ -1,6 +1,6 @@
 # Caching
 
-This guide introduces the caching capabilities of the Moovweb XDN
+This guide introduces the caching capabilities of {{ PRODUCT_NAME }}
 
 ## Environments and Caching
 
@@ -281,7 +281,7 @@ The cache will automatically be cleared when you make changes to your router. A
 
 ## Clearing the Cache
 
-The cache is automatically cleared when you deploy to an environment. You can also clear the cache using the environment's Caching tab in the Moovweb XDN console.
+The cache is automatically cleared when you deploy to an environment. You can also clear the cache using the environment's Caching tab in {{ PRODUCT_NAME }} console.
 
 ![deployments](/images/caching/purge.png)
 

guides/cli.md

@@ -81,7 +81,7 @@ xdn completion >> ~/.bashrc
 
 ### deploy
 
-Builds and deploys your site on the Moovweb XDN.
+Builds and deploys your site on {{ PRODUCT_NAME }}.
 
 #### Parameters
 
@@ -136,7 +136,7 @@ xdn dev
 
 ### init
 
-Run in an existing app to add all required packages and files need to publish your app on the Moovweb XDN
+Run in an existing app to add all required packages and files need to publish your app on {{ PRODUCT_NAME }}
 
 #### Example
 

guides/contributing.md

@@ -2,7 +2,7 @@
 
 The XDN is all about putting power in the hands of developers and our documentation is no different. The source code for the XDN developer docs (i.e. this site your reading now) is in an open [repository on Github](https://github.com/moovweb-docs/xdn-docs) and we welcome feedback and pull requests. If you've found a typo or a better way to explain something, please submit a pull request or a file issue! Others will likely stumble over the same problem and benefit from your insight.
 
-## Running locally 
+## Running locally
 
 To run the XDN docs on your machine, first clone the repository locally,
 
@@ -27,7 +27,7 @@ Finally, visit the site in your browser at http://127.0.0.1:3000.
 
 ## Architecture
 
-The XDN docs are a simple Next.js application running on the Moovweb XDN (yes we [dogfood](https://en.wikipedia.org/wiki/Eating_your_own_dog_food)). The content is stored as pages called "guides". Each guide is a Markdown file located in the [guides folder](https://github.com/moovweb-docs/xdn-docs/tree/master/guides) and the [guides.json](https://github.com/moovweb-docs/xdn-docs/blob/master/guides/guides.json) controls the navigation menu for reaching the guides.
+The XDN docs are a simple Next.js application running on {{ PRODUCT_NAME }} (yes we [dogfood](https://en.wikipedia.org/wiki/Eating_your_own_dog_food)). The content is stored as pages called "guides". Each guide is a Markdown file located in the [guides folder](https://github.com/moovweb-docs/xdn-docs/tree/master/guides) and the [guides.json](https://github.com/moovweb-docs/xdn-docs/blob/master/guides/guides.json) controls the navigation menu for reaching the guides.
 
 ## How to contribute
 
@@ -42,4 +42,3 @@ We recommend the following process for submitting a change:
 5. Submit a [pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests) back to the XDN Docs repository via Github web interface.
 
 For more details, the Pro Git book has a [helpful contributing guide](https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project) that walks you through the process of submitting a pull request to an open source repository on Github.
-

guides/cookies.md

@@ -4,5 +4,5 @@ This guide covers the cookies that Moovweb XDN creates and uses.
 
 ## Split testing cookies
 
-* `xdn_bucket`: a number between 1 and 100 randomly assigned by the Moovweb XDN to all clients connecting to it. It is a long-lived non-session cookie allowing predictable cohorts during split testing. Its value is not accessible from client-side JavaScript code.
-* `xdn_destination`: the name of the experience to which split testing has assigned the user based on the value of `xdn_bucket`. Its value is accessible to client-side JavaScript code and can thus be safely included in client-side metrics.
+- `xdn_bucket`: a number between 1 and 100 randomly assigned by {{ PRODUCT_NAME }} to all clients connecting to it. It is a long-lived non-session cookie allowing predictable cohorts during split testing. Its value is not accessible from client-side JavaScript code.
+- `xdn_destination`: the name of the experience to which split testing has assigned the user based on the value of `xdn_bucket`. Its value is accessible to client-side JavaScript code and can thus be safely included in client-side metrics.

guides/core_web_vitals.md

@@ -27,7 +27,7 @@ Instead of relying solely on Google Search Console, we recommend tracking Core W
 
 ## Installation
 
-In order to start tracking Core Web Vitals on the Moovweb XDN, you need add the `@xdn/rum` client library to your application. There are a number of ways to do this:
+In order to start tracking Core Web Vitals on {{ PRODUCT_NAME }}, you need add the `@xdn/rum` client library to your application. There are a number of ways to do this:
 
 ### Script Tag
 
@@ -156,19 +156,19 @@ new XDN.Metrics({
   pageLabel: 'home',
 
   // When running a split test, use this field to specify which variant is active.
-  // This is automatically set for sites that are deployed on the Moovweb XDN.
+  // This is automatically set for sites that are deployed on {{ PRODUCT_NAME }}.
   splitTestVariant: 'name-of-variant',
 
   // The version of your application that is running.
   appVersion: 'v1.0.0',
 
   // Whether or not the page was served from the CDN cache, if this is known.
-  // This is automatically set for sites that are deployed on the Moovweb XDN.
+  // This is automatically set for sites that are deployed on {{ PRODUCT_NAME }}.
   cacheHit: true | false,
 
   // The country code in which the browser is running. This is often provided by CDNs
   // as a request header that can be embedded in your script tab by your application code.
-  // This is automatically set for sites that are deployed on the Moovweb XDN.
+  // This is automatically set for sites that are deployed on {{ PRODUCT_NAME }}.
   country: 'US',
 })
 ```

guides/deploying.md

@@ -1,10 +1,10 @@
 # Deploying
 
-This guide walks you through deploying your first site to the Moovweb XDN.
+This guide walks you through deploying your first site to {{ PRODUCT_NAME }}.
 
 ## Create your Account
 
-To deploy your site to the Moovweb XDN, you must first sign up for an account. [Sign up here for free.](https://moovweb.app/signup)
+To deploy your site to {{ PRODUCT_NAME }}, you must first sign up for an account. [Sign up here for free.](https://moovweb.app/signup)
 
 ## Install the XDN CLI
 
@@ -22,26 +22,27 @@ yarn global add @xdn/cli
 
 ## xdn login
 
-Run the following to authenticate with your XDN account on the Moovweb XDN:
+Run the following to authenticate with your XDN account on {{ PRODUCT_NAME }}:
 
 ```bash
 xdn login
 ```
+
 ## xdn deploy
 
-Then, run the following to deploy your site to your private space on the Moovweb XDN:
+Then, run the following to deploy your site to your private space on {{ PRODUCT_NAME }}:
 
 ```bash
 xdn deploy
 ```
 
-The CLI will automatically detect the framework you're using, create an optimized production build, and upload it to the Moovweb XDN. This takes about a minute for most applications.
+The CLI will automatically detect the framework you're using, create an optimized production build, and upload it to {{ PRODUCT_NAME }}. This takes about a minute for most applications.
 
 Once the deployment is complete, the CLI will output the URL for your site. The site name is automatically derived from the `name` field in `package.json`. This can be overriden by using `--site` option when running `xdn deploy`.
 
 ## Branches and Deployments
 
-Each time you deploy your site to the Moovweb XDN a "deployment" is created and given a unique and permanent URL based on the team name, site name, branch name in source control, and an incrementing deployment number. If you use Git, the branch name is set by the default. If not, you can specify the `--branch` option when running `xdn deploy`.
+Each time you deploy your site to {{ PRODUCT_NAME }} a "deployment" is created and given a unique and permanent URL based on the team name, site name, branch name in source control, and an incrementing deployment number. If you use Git, the branch name is set by the default. If not, you can specify the `--branch` option when running `xdn deploy`.
 
 ![deployments](/images/deploying/deployments.png)
 
@@ -65,14 +66,14 @@ You should always store your deploy token using your CI environment's secrets ma
 
 ![video](https://www.youtube.com/watch?v=F8uN03ps1As)
 
-Here is an example GitHub action that deploys your site to the Moovweb XDN:
+Here is an example GitHub action that deploys your site to {{ PRODUCT_NAME }}:
 
 This action assumes that you have created environments called "staging" and "production" and you have created a deploy key for your site and added it as a secret in your repo called "xdn_deploy_token".
 
 ```yml
 # Add this file to your project at .github/workflows/xdn.yml
 #
-# This GitHub action deploys your site on the Moovweb XDN.
+# This GitHub action deploys your site on {{ PRODUCT_NAME }}.
 #
 # The site is deployed each time commits are pushed. The environment to which the changes are deployed
 # is based on the following rules:
@@ -135,7 +136,7 @@ jobs:
 
 ## Jenkins Pipeline
 
-Here is an example Jenkins pipeline that deploys your site to the Moovweb XDN:
+Here is an example Jenkins pipeline that deploys your site to {{ PRODUCT_NAME }}:
 
 This guide assumes:
 
@@ -147,7 +148,7 @@ This guide assumes:
 ```groovy
 // Add this file to your project at ./Jenkinsfile
 //
-// This Jenkins pipeline deploys your site on the Moovweb XDN.
+// This Jenkins pipeline deploys your site on {{ PRODUCT_NAME }}.
 //
 // The site is deployed each time commits are pushed. The environment to which the changes are deployed
 // is based on the following rules:

guides/frontity.md

@@ -1,6 +1,6 @@
 # Frontity
 
-This guide shows you how to deploy [Frontity](https://frontity.org/) apps on the Moovweb XDN
+This guide shows you how to deploy [Frontity](https://frontity.org/) apps on {{ PRODUCT_NAME }}
 
 ## Example Site
 
@@ -25,7 +25,7 @@ If you don't already have a Frontity app, use the terminal (or command prompt on
 npx frontity create my-app
 ```
 
-To prepare your Frontity app for deployment on the Moovweb XDN, run the following in the root folder of your project:
+To prepare your Frontity app for deployment on {{ PRODUCT_NAME }}, run the following in the root folder of your project:
 
 ```
 npm install -g @xdn/cli
@@ -34,7 +34,7 @@ xdn init
 
 This will automatically add all of the required dependencies and files to your project. These include:
 
-- The `@xdn/core` package - Allows you to declare routes and deploy your application on the Moovweb XDN
+- The `@xdn/core` package - Allows you to declare routes and deploy your application on {{ PRODUCT_NAME }}
 - The `@xdn/frontity` package - Provides router middleware that automatically adds Frontity routes to the XDN router.
 - The `@xdn/prefetch` package - Allows you to configure a service worker to prefetch and cache pages to improve browsing speed
 - The `@xdn/react` package - Provides a `Prefetch` component for prefetching pages
@@ -98,7 +98,7 @@ xdn dev --cache
 
 ## Deploying
 
-Deploying requires an account on the Moovweb XDN. [Sign up here for free.](https://moovweb.app/signup) Once you have an account, you can deploy to the Moovweb XDN by running the following in the root folder of your project
+Deploying requires an account on {{ PRODUCT_NAME }}. [Sign up here for free.](https://moovweb.app/signup) Once you have an account, you can deploy to {{ PRODUCT_NAME }} by running the following in the root folder of your project
 
 ```
 xdn deploy

guides/gatsby.md

@@ -1,6 +1,6 @@
 # Gatsby
 
-This guide shows you how to deploy an Gatsby application on the Moovweb XDN:
+This guide shows you how to deploy an Gatsby application on {{ PRODUCT_NAME }}:
 
 ![video](https://www.youtube.com/watch?v=ici9j6oF_5E)
 
@@ -55,7 +55,7 @@ xdn dev
 
 ## Deploying
 
-Deploying requires an account on the Moovweb XDN. [Sign up here for free.](https://moovweb.app/signup) Once you have an account, you can deploy to the Moovweb XDN by running the following in the root folder of your project:
+Deploying requires an account on {{ PRODUCT_NAME }}. [Sign up here for free.](https://moovweb.app/signup) Once you have an account, you can deploy to {{ PRODUCT_NAME }} by running the following in the root folder of your project:
 
 ```bash
 xdn deploy

guides/image_optimization.md

@@ -1,6 +1,6 @@
 # Image Optimization
 
-The Moovweb XDN provides a simple HTTP service for optimizing images:
+{{ PRODUCT_NAME }} provides a simple HTTP service for optimizing images:
 
 ```js
 https://opt.moovweb.net

guides/isg.md

@@ -2,11 +2,11 @@
 
 The Next.js framework first introduced the pattern of Incremental Static (Re)Generation (commonly referred to as **ISG**) to the JAMStack community. With ISG, some URLs are rendered at build time, while others aren't rendered until a user actually visits the page (the app essentially falls back to server-side rendering). A static loading page is returned while server-side rendering is in progress. Individual statically rendered URLs can also be configured to expire after some time (this is the *re*generation part).
 
-The Moovweb XDN provides full support for Incremental Static (Re)Generation, not just on apps built with Next.js (where the `@xdn/next` package makes this automatic), but on apps built with any framework.
+{{ PRODUCT_NAME }} provides full support for Incremental Static (Re)Generation, not just on apps built with Next.js (where the `@xdn/next` package makes this automatic), but on apps built with any framework.
 
 ## Adding ISG to Next.js apps
 
-Developers using Next.js don't need to do anything special to support ISG on the Moovweb XDN. Simply use the `NextRoutes` router plugin:
+Developers using Next.js don't need to do anything special to support ISG on {{ PRODUCT_NAME }}. Simply use the `NextRoutes` router plugin:
 
 ```js
 // routes.js