deploy: fb49f4b953

.ackrc

@@ -1,7 +0,0 @@
---ignore-dir=public
---ignore-dir=static
---ignore-dir=src/img
---ignore-dir=src/img
---type-add=svg:ext:svg
---no-xml
---no-svg

.editorconfig

@@ -1,34 +0,0 @@
-# EditorConfig helps developers define and maintain consistent
-# coding styles between different editors and IDEs
-# editorconfig.org
-
-root = true
-
-
-[*]
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-indent_style = space
-indent_size = 2
-
-[*.js]
-indent_style = space
-indent_size = 2
-
-[*.hbs]
-insert_final_newline = false
-indent_style = space
-indent_size = 2
-
-[*.css]
-indent_style = space
-indent_size = 2
-
-[*.html]
-indent_style = space
-indent_size = 2
-
-[*.{diff,md}]
-trim_trailing_whitespace = false

.eslintrc.js

@@ -1,48 +0,0 @@
-module.exports = {
-  root: true,
-  parserOptions: {
-    ecmaVersion: 6,
-    sourceType: 'module',
-  },
-  extends: 'eslint:recommended',
-  globals: {
-    "document": true,
-    "window": true,
-    "jQuery": true,
-    "$": true,
-    "require": true,
-    "__dirname": true,
-    "process": true,
-    "ENV": true,
-    "module": true
-  },
-  env: {
-    browser: true,
-    "es6": true
-  },
-  rules: {
-    "no-cond-assign": [
-      2,
-      "except-parens"
-    ],
-    "curly": 2,
-    "no-console": 0,
-    "no-debugger": 0,
-    "eqeqeq": 2,
-    "no-eval": 2,
-    "guard-for-in": 0,
-    "wrap-iife": 0,
-    "linebreak-style": 0,
-    "new-cap": 0,
-    "no-caller": 2,
-    "no-empty": 0,
-    "no-extra-boolean-cast": 0,
-    "no-new": 0,
-    "no-plusplus": 0,
-    "no-undef": 2,
-    "dot-notation": 0,
-    "strict": 0,
-    "no-eq-null": 2,
-    "no-unused-vars": 2
-  }
-};

.github/ISSUE_TEMPLATE/request-a-new-feature.md

@@ -1,26 +0,0 @@
----
-name: Request a New Feature
-about: For requesting new feature(s) to be added to the docs.
-title: ''
-labels: ''
-assignees: ''
----
-
-## Related Issues
-
-<!--
-List any issues or tickets on other platforms that are associated with the request. For example, include a link to the issue tracking that feature in the Rancher repo, or list the Jira ticket number for the request. 
--->
-
-## Summary
-
-<!--
-Describe the new feature. If QA has not yet tested the new feature/process, please also file a ticket with QA for their review.
--->
-
-## Details
-
-<!--
-- Include all pertinent information, e.g., screenshots, resource requirements, workarounds, links, etc.
-- List page link(s) in the current docs where the new feature applies, if applicable.
--->

.github/ISSUE_TEMPLATE/request-an-update.md

@@ -1,18 +0,0 @@
----
-name: Request an Update
-about: For fixing docs errors/typos, adding needed/missing information, updating verbiage, deleting outdated info, etc.
-title: ''
-labels: ''
-assignees: ''
----
-
-## Related Issues
-<!--
-List any issues or tickets on other platforms that are associated with the request. For example, include a link to the issue tracking that feature in the Rancher repo, or list the Jira ticket number for the request.
--->
-
-## Summary
-
-<!--
-Describe the requested update giving as much detail as possible. Please also list page link(s) in the current docs where the update applies.
--->

.github/dependabot.yml

@@ -1,8 +0,0 @@
-version: 2
-
-updates:
-  - package-ecosystem: gitsubmodule
-    schedule:
-        interval: "daily"
-    directory: /
-    

.github/pull_request_template.md

@@ -1,27 +0,0 @@
-<!--
-Check the Rancher docs issues to see if there is an existing issue for this pull request. If there is, enter the issue number below.
--->
-
-Fixes #[issue_number]
-
-## Reminders
-
-- See the [README](../README.md) for more details on how to work with the Rancher docs.
-
-- Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.
-
-- If the pull request is dependent on an upcoming release, remember to add a "MERGE ON RELEASE" label and set the proper milestone.
-
-## Description
-
-<!--
-- What is the goal of this pull request? 
-- What did you change? 
-- Are there any other pull requests, tickets, or issues associated with this pull request?
--->
-
-## Comments
-
-<!--
-Any additional notes a reviewer should know before we review.
--->

.github/workflows/deploy.yml

@@ -1,51 +0,0 @@
-name: Deploy to GitHub Pages
-
-on:
-  push:
-    branches:
-      - main
-    paths-ignore:
-      - '**/README.md'
-
-jobs:
-  build:
-    name: Build Docusaurus
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 18
-          cache: yarn
-
-      - name: Install dependencies
-        run: yarn install --frozen-lockfile
-      - name: Build website
-        env:
-          NODE_OPTIONS: "--max_old_space_size=7168"
-        run: yarn build --no-minify
-
-      - name: Upload Build Artifact
-        uses: actions/upload-pages-artifact@v3
-        with:
-          path: build
-
-  deploy:
-    name: Deploy to GitHub Pages
-    needs: build
-
-    permissions:
-      pages: write
-      id-token: write
-    
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-
-    runs-on: ubuntu-latest
-    steps:
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v4

.github/workflows/test-deploy.yml

@@ -1,30 +0,0 @@
-name: Test deployment
-
-on:
-  pull_request:
-    paths-ignore:
-      - '**/README.md'
-
-jobs:
-  test-deploy:
-    name: Test deployment
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 18
-          cache: yarn
-
-      - name: Install dependencies
-        run: yarn install --frozen-lockfile
-      - name: Check Markdown links
-        run: yarn run remark --quiet --frail --use remark-validate-links ./docs
-      - name: Check External links
-        run: yarn run remark --quiet --use remark-lint-no-dead-urls ./docs
-      - name: Test build website
-        env:
-          NODE_OPTIONS: "--max_old_space_size=7168"
-        run: yarn build --no-minify

.github/workflows/vale.yml

@@ -1,61 +0,0 @@
-# This action gets all changed markdown files in /docs and /versioned_docs using tj-actions/changed-files@v42
-# It compares new commits in the PR with the base commit (github.event.pull_request.base.sha)
-# It checks if no markdown files are changed 
-# It shows a count of markdown files and lists all changed markdown files
-# It uses Vale (https://vale.sh/docs/vale-cli/installation/) to provide feedback base off the SUSE Style Guide / OpenSUSE style rules (https://github.com/openSUSE/suse-vale-styleguide)
-
-name: Style check
-on:
-  pull_request:
-    paths-ignore:
-      - '**/README.md'
-
-jobs:
-  vale-lint:
-    name: runner / vale
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        continue-on-error: true
-        with:
-          fetch-depth: 0  # OR "2" -> To retrieve the preceding commit.
-          submodules: true
-      - name: Get all changed markdown files
-        continue-on-error: true
-        id: changed-markdown-files
-        uses: tj-actions/changed-files@v42
-        with:
-            # Avoid using single or double quotes for multiline patterns
-            files: |
-               docs/**
-               versioned_docs/**
-            separator: ","
-            base_sha: ${{ github.event.pull_request.base.sha }}
-        env:
-            ALL_CHANGED_FILES: ${{ 0 }}
-      - name: No files changed?
-        continue-on-error: true
-        if: steps.changed-markdown-files.outputs.any_changed == 'false'
-        run: |
-              echo "No files changed"
-              echo "ALL_CHANGED_FILES=$ALL_CHANGED_FILES" >> $GITHUB_ENV
-      - name: List all changed files markdown files
-        continue-on-error: true
-        if: steps.changed-markdown-files.outputs.any_changed == 'true'
-        env:
-            ALL_CHANGED_FILES: ${{ steps.changed-markdown-files.outputs.all_changed_files }}
-            ALL_CHANGED_FILES_COUNT: ${{ steps.changed-markdown-files.outputs.all_changed_files_count }}
-            SHA: ${{ github.head_ref }}
-            HEAD: ${{ github.base_ref }}
-        run: |
-            echo "Total Files Changed:" ${ALL_CHANGED_FILES_COUNT}
-            echo ${ALL_CHANGED_FILES}
-            echo "ALL_CHANGED_FILES=$ALL_CHANGED_FILES" >> $GITHUB_ENV
-      - uses: errata-ai/vale-action@v2.1.0
-        continue-on-error: true
-        if: steps.changed-markdown-files.outputs.any_changed == 'true'
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          separator: ", "
-          files: ${{ env.ALL_CHANGED_FILES }}

.gitignore

@@ -1,25 +0,0 @@
-# Dependencies
-/node_modules
-
-# Production
-/build
-
-# Generated files
-.docusaurus
-.cache-loader
-
-# Misc
-.DS_Store
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
-
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
-.idea/
-
-/dev-resources/algolia-search/.env
-/dev-resources/algolia-search/algolia-index.sh

.gitmodules

@@ -1,3 +0,0 @@
-[submodule ".github/styles/suse-vale-styleguide"]
-	path = .github/styles/suse-vale-styleguide
-	url = https://github.com/openSUSE/suse-vale-styleguide

.old-drone.yml

@@ -1,122 +0,0 @@
----
-kind: pipeline
-name: pull-request
-
-platform:
-  os: linux
-  arch: amd64
-
-steps:
-- name: test
-  pull: default
-  image: plugins/docker
-  settings:
-    context: .
-    dockerfile: Dockerfile.prod
-    dry_run: true
-    repo: rancher/docs
-  when:
-    event:
-    - pull_request
-
----
-kind: pipeline
-name: dev
-
-platform:
-  os: linux
-  arch: amd64
-
-steps:
-- name: publish-dev
-  pull: default
-  image: plugins/docker
-  settings:
-    context: .
-    dockerfile: Dockerfile.dev
-    group: publish
-    repo: rancher/docs
-    tag: dev
-    password:
-      from_secret: docker_password
-    username:
-      from_secret: docker_username
-  when:
-    branch:
-    - master
-    event:
-    - push
-
----
-kind: pipeline
-name: staging
-
-platform:
-  os: linux
-  arch: amd64
-
-steps:
-- name: publish-staging
-  pull: default
-  image: plugins/docker
-  settings:
-    context: .
-    dockerfile: Dockerfile.staging
-    group: publish
-    repo: rancher/docs
-    tag: staging
-    password:
-      from_secret: docker_password
-    username:
-      from_secret: docker_username
-  when:
-    branch:
-    - staging
-    event:
-    - push
-
----
-kind: pipeline
-name: production
-
-platform:
-  os: linux
-  arch: amd64
-
-steps:
-- name: publish-latest
-  pull: default
-  image: plugins/docker
-  settings:
-    context: .
-    dockerfile: Dockerfile.prod
-    group: publish
-    repo: rancher/docs
-    tag: latest
-    password:
-      from_secret: docker_password
-    username:
-      from_secret: docker_username
-  when:
-    branch:
-    - master
-    event:
-    - push
-
-- name: publish-algolia
-  pull: default
-  image: plugins/docker
-  settings:
-    context: .
-    dockerfile: Dockerfile.algolia
-    repo: rancher/docs
-    tag: algolia
-    password:
-      from_secret: docker_password
-    username:
-      from_secret: docker_username
-  when:
-    branch:
-    - master
-    event:
-    - push

.sass-lint.yml

@@ -1,24 +0,0 @@
-options:
-  formatter: stylish
-  merge-default-rules: true
-files:
-  include: 'src/sass/**/*.scss'
-rules:
-  bem-depth: 1
-  brace-style: 0
-  class-name-format:
-    - 1
-    - convention: 'hyphenatedbem'
-    - allow-single-line: false
-  empty-args: 0
-  indentation:
-    - 1
-    - size: 4
-  mixin-name-format:
-    - 1
-    - convention: 'hyphenatedbem'
-  no-color-keywords: 0
-  no-color-literals: 0
-  property-sort-order: 0
-  no-ids: 0
-  one-declaration-per-line: 1

.vale.ini

@@ -1,7 +0,0 @@
-StylesPath = .github/styles/suse-vale-styleguide
-
-[formtats]
-mdx = md
-
-[*.md]
-BasedOnStyles = common

2.7/reference-guides/rancher-security/hardening-guides/k3s-hardening-guide/k3s-self-assessment-guide-with-cis-v1.23-k8s-v1.24/index.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/v2.7/reference-guides/rancher-security/hardening-guides/k3s-hardening-guide/k3s-self-assessment-guide-with-cis-v1.24-k8s-v1.24">
+    <link rel="canonical" href="/v2.7/reference-guides/rancher-security/hardening-guides/k3s-hardening-guide/k3s-self-assessment-guide-with-cis-v1.24-k8s-v1.24" />
+  </head>
+  <script>
+    window.location.href = '/v2.7/reference-guides/rancher-security/hardening-guides/k3s-hardening-guide/k3s-self-assessment-guide-with-cis-v1.24-k8s-v1.24' + window.location.search + window.location.hash;
+  </script>
+</html>

CODEOWNERS

@@ -1 +0,0 @@
-* @btat @LucasSaintarbor @martyav @sunilarjun

LICENSE

@@ -1,178 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-

README.md

@@ -1,108 +0,0 @@
-# Contribute to Rancher Docs
-
-Welcome to the [Rancher docs](https://ranchermanager.docs.rancher.com/) repository. See the [Rancher software](https://github.com/rancher/rancher) repository if you have questions or requests for the Rancher platform.
-
-## Make a Suggestion
-
-You can suggest changes to the Rancher docs in two ways: 
-
-1. [Open an issue](https://github.com/rancher/rancher-docs/issues/new/choose).
-1. Edit the docs in the way you see fit and open a pull request.
-
-## Edit the Docs
-
-To get started, [fork](https://github.com/rancher/rancher-docs/fork) and clone the rancher-docs repository.
-
-Our repository doesn't allow you to make changes directly to the `main` branch. Create a working branch and make pull requests from your fork to [rancher/rancher-docs](https://github.com/rancher/rancher-docs).
-
-For most updates, you'll need to edit a file in the `/docs` directory, which represents the ["Latest"](https://ranchermanager.docs.rancher.com/) version of our published documentation. The "Latest" version is a mirror of the most recently released version of Rancher. As of August 2024, the most recently released version of Rancher is 2.9.
-
-Whenever an update is made to `/docs`, you should apply the same change to the corresponding file in `/versioned_docs/version-2.9`. If a change only affects older versions, you don't need to mirror it to the `/docs` directory.
-
-If a file is moved or renamed, you'll also need to edit the `sidebars.js` files for each affected version, as well as the list of redirects in `docusaurus.config.js`. See [Moving or Renaming Docs](./moving-or-renaming-docs.md).
-
-### Navigate the Repo
-
-The file paths in the repo correspond to the URLs for pages on the docs website. The docs for the latest version of Rancher are located in `/docs`. All images are in `/static/img` in the top level of the repo. Older docs are found within `/versioned_docs` and generally follow the same structure as the files in `/docs`.
-
-### Style & Formatting
-
-The docs are written in [Markdown](https://www.markdownguide.org/getting-started/). We use standard American English and many pages are also available in Simplified Chinese.
-
-Moving forward, we are referring to the SUSE [style guide](https://documentation.suse.com/style/current/pdf/style-guide_en.pdf). The **Style check / runner / vale (pull_request)** check used [Vale](https://vale.sh/) to make style and grammar suggestions for new or updated documentation based on the SUSE style guide. To review these suggestions when working on a PR:
-
-1. Select the details of the **Style check / runner / vale (pull_request)** check.
-1. In the logs, go to **Run errata-ai/vale-action@v2.1.0** and select **Running vale with reviewdog 🐶 ...** to view the suggestions.
-1. New or updated files are checked against the SUSE style guide. Suggestions have the following format: '{"message": "[suse-vale-styleguide.Rule] Rule description", "location": {"path": "file-path", "range": {"start": {"line": , "column": }}}, "severity": " "}'
-
-    For example: '{"message": "[suse-vale-styleguide.Usage] Use 'certain' instead of 'some'", "location": {"path": "docs/contribute-to-rancher.md", "range": {"start": {"line": 3, "column": 132}}}, "severity": "WARNING"}'
-
-1. Incorporate the suggestions when possible and appropriate.
-
-Every docs page contain metadata in the first few lines:
-
-```
----
-title: Some Title
----
-```
-
-The `title` is rendered as the page's headline. The site renderer wraps the `title` value in `H1` tags, which are equivalent to `#` in Markdown syntax. This means that all subsequent headers on the page should be second level (`##`) or more.
-
-## Run the Docs Website
-
-The Rancher Docs website is built with [Docusaurus 2](https://docusaurus.io/), a modern static website generator.
-
-You can run the site on your local machine, to preview how pages on your working branch will look live.
-
-First, install Docusaurus 2:
-
-1. If you haven't already, install [Node](https://nodejs.org/en/download/) and [Yarn](https://yarnpkg.com/getting-started/install).
-1. Go into your local rancher-docs folder.
-1. The Rancher Docs repository already contains a yarn.lock file, which contains the dependencies you need to build the website. Run `yarn` to install Docusaurus and associated dependencies.
-
-### Start Site
-
-```
-yarn start
-```
-
-This command starts a local development server for Docusaurus 2, and opens up a browser window. Most changes are reflected live without having to restart the server.
-
-**Note:** The `yarn start` command won't include some important static site features. For example, switching between languages from the site's dropdown menu is not available. If you need these features, use `yarn build`.
-
-### Build Site
-
-```
-yarn build
-```
-
-This command generates static content into the `build` directory and can be served using any static contents hosting service.
-
-### Launch With Docker
-
-You can also use [Docker](https://www.docker.com/) to launch the website.
-
-The below command can be used to install the dependencies and run the site inside a container:
-
-```
-docker run --rm -it -v $PWD:$PWD -w $PWD -p 3000:3000 node:18 /bin/sh -c "yarn install && yarn start -h 0.0.0.0"
-```
-
-Subsequent executions will check for updated dependencies, if there are none, it will skip the updates and quickly start the server.
-
-License
-=======
-Copyright (c) 2014-2024 [Rancher Labs, Inc.](https://rancher.com)
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-[http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0)
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.

api/api-reference.htm/index.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/api-reference">
+    <link rel="canonical" href="/api/api-reference" />
+  </head>
+  <script>
+    window.location.href = '/api/api-reference' + window.location.search + window.location.hash;
+  </script>
+</html>

api/api-reference.html.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/api-reference">
+    <link rel="canonical" href="/api/api-reference" />
+  </head>
+  <script>
+    window.location.href = '/api/api-reference' + window.location.search + window.location.hash;
+  </script>
+</html>

api/api-tokens.htm/index.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/api-tokens">
+    <link rel="canonical" href="/api/api-tokens" />
+  </head>
+  <script>
+    window.location.href = '/api/api-tokens' + window.location.search + window.location.hash;
+  </script>
+</html>

api/api-tokens.html.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/api-tokens">
+    <link rel="canonical" href="/api/api-tokens" />
+  </head>
+  <script>
+    window.location.href = '/api/api-tokens' + window.location.search + window.location.hash;
+  </script>
+</html>

api/quickstart.htm/index.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/quickstart">
+    <link rel="canonical" href="/api/quickstart" />
+  </head>
+  <script>
+    window.location.href = '/api/quickstart' + window.location.search + window.location.hash;
+  </script>
+</html>

api/quickstart.html.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/quickstart">
+    <link rel="canonical" href="/api/quickstart" />
+  </head>
+  <script>
+    window.location.href = '/api/quickstart' + window.location.search + window.location.hash;
+  </script>
+</html>

api/v3-rancher-api-guide.htm/index.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/v3-rancher-api-guide">
+    <link rel="canonical" href="/api/v3-rancher-api-guide" />
+  </head>
+  <script>
+    window.location.href = '/api/v3-rancher-api-guide' + window.location.search + window.location.hash;
+  </script>
+</html>

api/v3-rancher-api-guide.html.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/v3-rancher-api-guide">
+    <link rel="canonical" href="/api/v3-rancher-api-guide" />
+  </head>
+  <script>
+    window.location.href = '/api/v3-rancher-api-guide' + window.location.search + window.location.hash;
+  </script>
+</html>

api/workflows/projects.htm/index.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/workflows/projects">
+    <link rel="canonical" href="/api/workflows/projects" />
+  </head>
+  <script>
+    window.location.href = '/api/workflows/projects' + window.location.search + window.location.hash;
+  </script>
+</html>

api/workflows/projects.html.html

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="refresh" content="0; url=/api/workflows/projects">
+    <link rel="canonical" href="/api/workflows/projects" />
+  </head>
+  <script>
+    window.location.href = '/api/workflows/projects' + window.location.search + window.location.hash;
+  </script>
+</html>