Updated name, addressing suggestions

Author: TMoMoreau

docs/.vuepress/config.js

@@ -225,7 +225,7 @@ module.exports = {
                   '/how-to/websites-on-ipfs/link-a-domain',
                   '/how-to/websites-on-ipfs/introducing-fleek',
                   '/how-to/websites-on-ipfs/static-site-generators',
-                  '/how-to/websites-on-ipfs/gateway-redirects'
+                  '/how-to/websites-on-ipfs/_redirects-file-support'
                 ]
               },
               {

docs/how-to/websites-on-ipfs/gateway-redirects.md

@@ -1,36 +1,27 @@
 ---
-title: Gateway redirects
-description: What gateway redirects are and how to use them with a website on IPFS.
+title: _redirects file support
+description: What the _redirect file is and how to use them with a website on IPFS.
 ---
+# `_redirects` file support
 
-# THIS IS A DRAFT. DO NOT MERGE.
+The `_redirects` file provides support for URL redirects and rewrites for websites hosted on Subdomain or DNSLink gateways. This feature enables support for single-page applications, progressive web applications, custom 404 pages, and avoids link rot when moving to IPFS-backed hosting. As well as the ability to change the appearance of a URL, change where content is located without breaking existing links, and enable URL rewriting.
 
-# To do:
-1. How to redirect old URL to a new place (301 and 302 redirects)
-1. How to use it for PWA/SPA hosting (catch-all 200) 
-1. How to use it to provide custom `404 not found` pages (superceding what `ipfs-404.html` does - ideally not mention old way)
+This `_redirects` implementaion is a subset of pre-existing standards supported by [Cloudflare](https://developers.cloudflare.com/pages/platform/redirects) and [Netlify](https://docs.netlify.com/routing/redirects/).
 
-# Gateway Redirects
-
-Gateway Redirects provide support for URL redirects and rewrites for websites hosted on Subdomain or DNSLink gateways. This feature enables support for single-page applications, and avoids link rot when moving to IPFS-backed hosting.
-
-Using Gateway Redirects, you can change the appearance of a URL, change where content is located without breaking existing links, redirect invalid URLs to a custom 404 page, and enable URL rewriting.
+For more detailed information, check out the [`_redirects` file support specs](https://github.com/ipfs/specs/pull/290).
 
 # Supported HTTP status codes
 
 * `200` - OK (redirect will be treated as a rewrite, returning OK without changing the URL shown in the browser).
 * `301` - Permanent redirect (the default status).
 * `302` - Found (commonly used for temporary redirects).
-* `303` - See other (replaces PUT and POST with GET).
-* `307` - Temporary redirect (preserves the body and HTTP method of the original request).
-* `308` - Permanent redirect (preserves the body and HTTP method of the original request).
 * `404` - Not found (can be used redirect to custom 404 pages).
 * `410` - Gone (the requested content has been permanently removed).
 * `451` - Unavailable for legal reasons.
 
-# How to set up gateway redirects
+# How to set up the `_redirects` file
 
-To use Gateway Redirects, there must be a file named `_redirects` stored underneath the root CID of the website. This `_redirects` file must be a text file containing one or more lines that follow the format explained below.
+To use the `_redirects` file, there must be a file named `_redirects` stored underneath the root CID of the website. This `_redirects` file must be a text file containing one or more lines that follow the format explained below.
 
 ## Format of the `_redirects` file
 
@@ -40,47 +31,61 @@ Each line contained within the `_redirects` file has 3 basic components:
 1. The `to` path, this specifies the path to be redirected to.
 1. The `status` component, this part is optional and specifies the HTTP status code that will be returned. (301, 404, etc.)
 
-For example, if I want to redirect a page to a custom `404` page, the `_redirects` file will contain a line that looks something like this:
+For example, if for whatever reason I wanted to temporarily redirect traffic from my home page to my index page, the `_redirects` file will contain a line that looks something like this:
+
 ```
-/<requested page> /custom404.html 404
+/home /index.html 302 \n
 ```
 
 The same format is used for all redirects.
 
-## Placeholders
+# Examples
 
-Placeholders are named variables that can be used to match path segments in the `from` path and inject them into the `to` path.
+## Catch all and PWA/SPA support
 
-For example, if I wanted to search for an article titled "hello world" that was written on June 15, 2022, I could search for it like this: `/posts/06/15/2022/hello-world` and be redirected to `/articles/2022/06/15/hello-world`
+The `200` status will be treated as a rewrite, returning OK without changing the URL shown in the browser. This staus code can be used to build [Progressive Web Apps](https://en.wikipedia.org/wiki/Progressive_web_app) and [Single Page Applications](https://en.wikipedia.org/wiki/Single-page_application).
 
-## Splat
+```
+/home /index.html 200 \n
+```
+
+## Redirect an old URL to a new place
+
+The `301` status is a permanent redirect, this is the default status code used when no others are spcified. 
 
-If the `from` path ends with an asterisk (`*`), the rest of the `from` path will be slurped up into the special `:splat` placeholder, which can then be injected into the `to` path.
 ```
-/posts/* /articles/:splat
+/index /docs.html 301 \n
 ```
-:::note
-Splat logic must only apply to a single trailing asterisk, as it is a greedy match that consumes the remainder of the path. :::
 
-## Comments
+The `302` status is commonly used for temporary redirects.
 
-Any line in the `_redirects` file that begins with `#` will be ignored and treated as a comment.
+```
+/home /under-construction.html 302 \n
+```
 
-## Line termination
+## Add a custom 404 page to your website
 
-Each line in the `_redirects` file must be terminated with either `\n` or `\r\n`.
+Use the `_redirects` file support to add a custom 404 page to your website.
 
 ```
-/<requsted page> /custom404.html 404 \n
-/home /index.html \n
+/home /custom-404.html 404 \n
 ```
-# Evaluation
 
-Rules must only be evaluated when hosted on a subdomain or DNSLink gateway, this is to maintain same-origin isolation.
+## Placeholders
+
+Placeholders are named variables that can be used to match path segments in the `from` path and inject them into the `to` path.
+
+This is useful for redirecting users to their desired content, even if their search was not completely accurate.
 
-## Order
+For example, if I wanted to search for an article titled "hello world" that was written on June 15, 2022, I could search for it like this: `/posts/06/15/2022/hello-world` and be redirected to `/articles/2022/06/15/hello-world`
+
+```
+/posts/<month>/<day>/<year>/<slug> /articles/<year>/<month>/<day>/<slug> \n
+```
+
+# Evaluation
 
-Rules must be evaluated in order, redirecting or rewriting using the first matching pair.
+The `_redirects` file  is only supported on subdomain and DNSLink gateways, which provides [unique origin per root CID](https://en.wikipedia.org/wiki/Same-origin_policy).
 
 ## No forced redirects