cleanup links to /beta-features/ and add redirects #7040 (#7070)

website/content/docs/configuration-options.md

@@ -24,7 +24,7 @@ You can find details about all configuration options below. Note that [YAML synt
 
 The `backend` option specifies how to access the content for your site, including authentication. Full details and code samples can be found in [Backends](/docs/backends-overview).
 
-**Note**: no matter where you access Decap CMS — whether running locally, in a staging environment, or in your published site — it will always fetch and commit files in your hosted repository (for example, on GitHub), on the branch you configured in your Decap CMS config.yml file. This means that content fetched in the admin UI will match the content in the repository, which may be different from your locally running site. It also means that content saved using the admin UI will save directly to the hosted repository, even if you're running the UI locally or in staging. If you want to have your local CMS write to a local repository, try the `local_backend` setting, [currently in beta](/docs/beta-features/#working-with-a-local-git-repository).
+**Note**: no matter where you access Decap CMS — whether running locally, in a staging environment, or in your published site — it will always fetch and commit files in your hosted repository (for example, on GitHub), on the branch you configured in your Decap CMS config.yml file. This means that content fetched in the admin UI will match the content in the repository, which may be different from your locally running site. It also means that content saved using the admin UI will save directly to the hosted repository, even if you're running the UI locally or in staging. If you want to have your local CMS write to a local repository, try the `local_backend` setting, [currently in beta](/docs/working-with-a-local-git-repository/).
 
 ### Commit Message Templates
 

website/content/docs/open-authoring.md

@@ -3,7 +3,6 @@ group: Workflow
 weight: 20
 title: Open Authoring
 ---
-**This is a [beta feature](/docs/beta-features#open-authoring).**
 
 When using the [GitHub backend](/docs/github-backend), you can use Decap CMS to accept contributions from GitHub users without giving them access to your repository. When they make changes in the CMS, the CMS forks your repository for them behind the scenes, and all the changes are made to the fork. When the contributor is ready to submit their changes, they can set their draft as ready for review in the CMS. This triggers a pull request to your repository, which you can merge using the GitHub UI.
 

website/content/docs/site-generator-overview.md

@@ -29,6 +29,7 @@ It is up to developers to determine how to build the raw content into something
 
 To learn how to query raw content managed by Decap CMS and reformat them for delivery to end users, please refer the dedicated section for your site generator in the Table of Content.
 ___
+
 ### Local development
 
-If you are experimenting with Decap CMS or testing things out, you can connect it to a local Git repository instead of a live one. Learn how to do it [here](/docs/beta-features/#working-with-a-local-git-repository).
+If you are experimenting with Decap CMS or testing things out, you can connect it to a local Git repository instead of a live one. Learn how to do it [here](/docs/working-with-a-local-git-repository/).

website/static/_redirects

@@ -16,3 +16,4 @@ https://www.netlifycms.org/* https://decapcms.org/:splat 301!
 /docs/quick-start                       /docs/add-to-your-site 301
 /chat                                   https://discord.gg/KZRDXmTm9v 301
 /docs/update-the-cms-version            /docs/releases 301
+/docs/beta-features/                    /docs/ 301