Update documentation to reflect new branch structure

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to the Quarkus.io website
 
-Contributions are welcome, please submit pull requests for the `develop` branch.
+Contributions are welcome, please submit pull requests for the `main` branch.
 
 **Important:** the guides are maintained in the main Quarkus repository and pull requests should be submitted there:
 https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc.

README.md

@@ -58,7 +58,7 @@ These instructions will get you a copy of the Quarkus.io website up and running
 
 ### Deploying to GitHub Pages
 
-The website deployment is automatically performed by GitHub Actions (when commits are pushed to the `develop` branch).
+The website deployment is automatically performed by GitHub Actions (when commits are pushed to the `main` branch).
 If for some reason you need to deploy from your local machine, follow these instructions:
 
 1. Install the [act](https://github.com/nektos/act#installation) executable to run GitHub Actions locally
@@ -68,10 +68,10 @@ If for some reason you need to deploy from your local machine, follow these inst
 
 To write a blog:
 
-- create an author entry in [_data/authors.yaml](https://github.com/quarkusio/quarkusio.github.io/blob/develop/_data/authors.yaml)
+- create an author entry in [_data/authors.yaml](https://github.com/quarkusio/quarkusio.github.io/blob/main/_data/authors.yaml)
   - `emailhash` you can get by running `echo -n [email protected] | md5sum` on Linux or `echo -n [email protected] | md5` on macOS using an email you have registered from the [Gravatar service](https://gravatar.com),
 
-- create an blog entry under [_posts](https://github.com/quarkusio/quarkusio.github.io/tree/develop/_posts)
+- create an blog entry under [_posts](https://github.com/quarkusio/quarkusio.github.io/tree/main/_posts)
   - the file name is `yyyy-mm-dd-slug.adoc` Set the date to the same value in the asciidoc preamble.
 - `tags` should be used with some care as an archive page is created for of them. Below are some basic rules to try follow:
   - `quarkus-release` used for Quarkus release blogs
@@ -82,9 +82,9 @@ To write a blog:
   - add a tech specific, like `kafka`, if your post has a significant mention/relevance to that technology.
   - tags is space separated list `tags:extension grpc`
   - tags must be in lowercase
-- it's in asciidoc format, there is an example as shown with [2019-06-05-quarkus-and-web-ui-development-mode.adoc](https://github.com/quarkusio/quarkusio.github.io/blob/develop/_posts/2019-06-05-quarkus-and-web-ui-development-mode.adoc)
+- it's in asciidoc format, there is an example as shown with [2019-06-05-quarkus-and-web-ui-development-mode.adoc](https://github.com/quarkusio/quarkusio.github.io/blob/main/_posts/2019-06-05-quarkus-and-web-ui-development-mode.adoc)
   - Be aware that the `date` attribute in the asciidoc preamble defines when the article will be published. Add a `--future` flag when testing locally to ensure the article is included in the generated site. 
-- send a pull request against the develop branch and voilà
+- send a pull request against the main branch and voilà
 
 ## Translations/Localization (l10n)
 

_guides/doc-contribute-docs-howto.adoc

@@ -131,7 +131,7 @@ As content evolves, you might want to restructure an existing piece of Quarkus c
 If you are retiring or renaming a published Quarkus AsciiDoc source file, ensure that the restructure does not break existing bookmarks and links to the original content.
 Configure a URL redirect in the link:https://github.com/quarkusio/quarkusio.github.io/[Quarkus.io Website] GitHub repository by using the following steps:
 
-. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
+. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
 . Create a redirection file in Markdown format with a filename that matches the original AsciiDoc source filename that you want to retire.
 . Add the following contents to the Markdown redirection file:
 +
@@ -346,7 +346,7 @@ If you disagree with the Vale results, add the yellow PR label `needs-vale-rule-
 
 == Previewing doc changes on the Quarkus website
 
-After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
+After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
 
 [IMPORTANT]
 ====

_versions/2.16/guides/doc-contribute-docs-howto.adoc

@@ -76,7 +76,7 @@ As content evolves, you might want to restructure an existing piece of Quarkus c
 If you are retiring or renaming a published Quarkus AsciiDoc source file, ensure that the restructure does not break existing bookmarks and links to original content. 
 Configure a URL redirect in the link:https://github.com/quarkusio/quarkusio.github.io/[Quarkus.io Website] GitHub repository by using the following steps:
 
-. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_redirects/guides[quarkusio/quarkusio.github.io] repository, and open the `_redirects/guides` folder.
+. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_redirects/guides[quarkusio/quarkusio.github.io] repository, and open the `_redirects/guides` folder.
 . Create a redirection file in Markdown format with a filename that matches the original AsciiDoc source filename that you want to retire. 
 . Add the following contents to the Markdown redirection file:
 +
@@ -229,7 +229,7 @@ If you disagree with the Vale results, be sure to add the yellow PR label `needs
 
 == Previewing doc changes on the Quarkus website
 
-After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
+After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
 
 [IMPORTANT]
 ====

_versions/3.2/guides/doc-contribute-docs-howto.adoc

@@ -130,7 +130,7 @@ As content evolves, you might want to restructure an existing piece of Quarkus c
 If you are retiring or renaming a published Quarkus AsciiDoc source file, ensure that the restructure does not break existing bookmarks and links to the original content.
 Configure a URL redirect in the link:https://github.com/quarkusio/quarkusio.github.io/[Quarkus.io Website] GitHub repository by using the following steps:
 
-. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
+. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
 . Create a redirection file in Markdown format with a filename that matches the original AsciiDoc source filename that you want to retire.
 . Add the following contents to the Markdown redirection file:
 +
@@ -345,7 +345,7 @@ If you disagree with the Vale results, add the yellow PR label `needs-vale-rule-
 
 == Previewing doc changes on the Quarkus website
 
-After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
+After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
 
 [IMPORTANT]
 ====

_versions/3.8/guides/doc-contribute-docs-howto.adoc

@@ -131,7 +131,7 @@ As content evolves, you might want to restructure an existing piece of Quarkus c
 If you are retiring or renaming a published Quarkus AsciiDoc source file, ensure that the restructure does not break existing bookmarks and links to the original content.
 Configure a URL redirect in the link:https://github.com/quarkusio/quarkusio.github.io/[Quarkus.io Website] GitHub repository by using the following steps:
 
-. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
+. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
 . Create a redirection file in Markdown format with a filename that matches the original AsciiDoc source filename that you want to retire.
 . Add the following contents to the Markdown redirection file:
 +
@@ -346,7 +346,7 @@ If you disagree with the Vale results, add the yellow PR label `needs-vale-rule-
 
 == Previewing doc changes on the Quarkus website
 
-After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
+After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
 
 [IMPORTANT]
 ====

_versions/main/guides/doc-contribute-docs-howto.adoc

@@ -131,7 +131,7 @@ As content evolves, you might want to restructure an existing piece of Quarkus c
 If you are retiring or renaming a published Quarkus AsciiDoc source file, ensure that the restructure does not break existing bookmarks and links to the original content.
 Configure a URL redirect in the link:https://github.com/quarkusio/quarkusio.github.io/[Quarkus.io Website] GitHub repository by using the following steps:
 
-. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
+. Switch to the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_redirects/guides[`quarkusio/quarkusio.github.io`] repository, and open the `_redirects/guides` folder.
 . Create a redirection file in Markdown format with a filename that matches the original AsciiDoc source filename that you want to retire.
 . Add the following contents to the Markdown redirection file:
 +
@@ -346,7 +346,7 @@ If you disagree with the Vale results, add the yellow PR label `needs-vale-rule-
 
 == Previewing doc changes on the Quarkus website
 
-After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/develop/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
+After your PR is merged to `main` and the branch is synchronized with the link:https://github.com/quarkusio/quarkusio.github.io/tree/main/_generated-doc[Quarkus.io] website repository, you can preview the resulting build output on the link:https://quarkus.io/version/main/guides/[Main branch (SNAPSHOT)] documentation page of the Quarkus site.
 
 [IMPORTANT]
 ====