permalinks for latest docs versions + release guidelines

README.md

@@ -338,6 +338,10 @@ start the release process (in case anything is missing).
 4. **You may now do the release by following the instructions outlined in the
 [Rasa Open Source README](#steps-to-release-a-new-version) !**
 
+#### After a Major release
+
+After a Major release has been completed, please follow [these instructions to complete the documentation update](./docs/README.md#manual-steps-after-a-new-version).
+
 ### Steps to release a new version
 Releasing a new version is quite simple, as the packages are build and distributed by GitHub Actions.
 

docs/README.md

@@ -2,6 +2,8 @@
 
 The docs are built using [Docusaurus 2](https://v2.docusaurus.io/).
 
+## Useful commands
+
 ### Installation
 
 ```
@@ -27,3 +29,10 @@ This command generates static content into the `build` directory and can be serv
 ### Deployment
 
 Deployment is handled by Netlify: it is setup for listening to changes on the `documentation` branch.
+
+
+## Manual steps after a new version
+
+When a new docs version has been released, we'll need to do the following manual steps:
+- Update the wording and links of the top banner, configured in `docusaurus.config.js` in `announcementBar`.
+- Update Netlify redirects in `netflify.toml`, under `# Redirects for latest version permalinks`

docs/netlify.toml

@@ -176,6 +176,17 @@
   from = "/docs/rasa/prototype-an-assistant"
   to = "/docs/rasa/playground/"
 
+# Redirects for latest version permalinks
+# this needs to be updated when we cut a new version
+[[redirects]]
+  from = "/docs/rasa/2.x"
+  to = "/docs/rasa"
+
+[[redirects]]
+  from = "/docs/rasa/2.x/*"
+  to = "/docs/rasa/:splat"
+# end permalink section
+
 # FIXME: this requires some feedback as to the 404, like in the website
 [[redirects]]
   from = "/docs/rasa/*"