Adjust FAQ Slack link + dead link checker (k3s-io#61)

* Adjust slack link
* Add external link checker
* Fix dead external links

Signed-off-by: Derek Nola <[email protected]>

Author: dereknola

.github/workflows/test-deploy.yml

@@ -18,8 +18,8 @@ jobs:
 
       - name: Install dependencies
         run: yarn install --frozen-lockfile
-      - name: Check internal links
-        run: yarn run remark --quiet --frail ./docs
+      - name: Check links
+        run: yarn run remark --use remark-lint-no-dead-urls --use remark-validate-links --frail ./docs
       - name: Test build website
         run: yarn build
 

docs/advanced/advanced.md

@@ -279,7 +279,7 @@ There are several ways to run K3s in Docker:
 <Tabs>
 <TabItem value='K3d' default>
 
-[k3d](https://github.com/k3s-io/k3d) is a utility designed to easily run K3s in Docker.
+[k3d](https://github.com/k3d-io/k3d) is a utility designed to easily run K3s in Docker.
 
 It can be installed via the the [brew](https://brew.sh/) utility on MacOS:
 

docs/faq/faq.md

@@ -53,6 +53,6 @@ If you are having an issue with deploying K3s, you should:
 
 3) Search the [K3s GitHub existing issues](https://github.com/k3s-io/k3s/issues) for one that matches your problem.
 
-4) Join the [Rancher K3s Slack](https://rancher-users.slack.com/archives/CGGQEHPPW) channel to get help. 
+4) Join the [Rancher Slack](https://rancher-users.slack.com/) K3s channel to get help. 
 
 5) Submit a [New Issue](https://github.com/k3s-io/k3s/issues/new/choose) on the K3s Github describing your setup and the issue you are experiencing.

docs/installation/network-options.md

@@ -78,7 +78,7 @@ You should see that IP forwarding is set to true.
 </TabItem>
 <TabItem value="Calico" default>
 
-Follow the [Calico CNI Plugins Guide](https://docs.projectcalico.org/master/docs/reference/cni-plugin/configuration). Modify the Calico YAML so that IP forwarding is allowed in the `container_settings` section, for example:
+Follow the [Calico CNI Plugins Guide](https://projectcalico.docs.tigera.io/reference/cni-plugin/configuration). Modify the Calico YAML so that IP forwarding is allowed in the `container_settings` section, for example:
 
 ```yaml
 "container_settings": {

docs/reference/binary-tools.md

@@ -9,7 +9,7 @@ Command | Description
 --------|------------------
 `k3s server`| Run the K3s management server, which will also launch Kubernetes control plane components such as the API server, controller-manager, and scheduler.
 `k3s agent`|  Run the K3s node agent. This will cause K3s to run as a worker node, launching the Kubernetes node services `kubelet` and `kube-proxy`.
-`k3s kubectl`| Run an embedded [kubectl](https://kubernetes.io/docs/docs/reference/kubectl/overview/) CLI. If the `KUBECONFIG` environment variable is not set, this will automatically attempt to use the config file that is created at `/etc/rancher/k3s/k3s.yaml` when launching a K3s server node.
+`k3s kubectl`| Run an embedded [kubectl](https://kubernetes.io/docs/reference/kubectl) CLI. If the `KUBECONFIG` environment variable is not set, this will automatically attempt to use the config file that is created at `/etc/rancher/k3s/k3s.yaml` when launching a K3s server node.
 `k3s crictl`| Run an embedded [crictl](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md). This is a CLI for interacting with Kubernetes's container runtime interface (CRI). Useful for debugging.
 `k3s ctr`| Run an embedded [ctr](https://github.com/projectatomic/containerd/blob/master/docs/cli.md). This is a CLI for containerd, the container daemon used by K3s. Useful for debugging.
 `k3s etcd-snapshot` | Perform on demand backups of the K3s cluster data and upload to S3. See [Backup and Restore](../backup-restore/backup-restore.md#backup-and-restore-with-embedded-etcd-datastore) for more information.

package.json

@@ -22,6 +22,8 @@
     "react": "^17.0.2",
     "react-dom": "^17.0.2",
     "remark-cli": "^11.0.0",
+    "remark-lint": "^9.1.1",
+    "remark-lint-no-dead-urls": "^1.1.0",
     "remark-validate-links": "^12.1.0"
   },
   "devDependencies": {