Re-link contributing links to the new contributing documentation.

README.md

@@ -35,7 +35,7 @@ open a formal Godot improvement proposal like you do with engine features, but s
 or joining the discussion on the [Godot Contributors Chat](https://chat.godotengine.org/channel/website) is a good
 idea.
 
-[^1]: https://docs.godotengine.org/en/latest/contributing/workflow/index.html
+[^1]: https://contributing.godotengine.org/en/latest/other/website.html
 [^2]: https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/CSS_layout/Supporting_Older_Browsers
 [^3]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs
 

_includes/header.html

@@ -29,7 +29,7 @@
 			<ul class="right">
 				<li><a href="/download/windows/" class="set-os-download-url">{% t header.download %}</a></li>
 				<li><a href="https://docs.godotengine.org">{% t header.docs %}</a></li>
-				<li><a href="https://docs.godotengine.org/en/stable/contributing/how_to_contribute.html">{% t header.contribute %}</a></li>
+				<li><a href="https://contributing.godotengine.org/en/latest/organization/how_to_contribute.html">{% t header.contribute %}</a></li>
 				{% if page.localize %}
 					<li class="language-selector" onclick="this.classList.toggle('open')">
 						<a class="mobile-language-selector" href="#">{% t header.language %}: </a>

_layouts/download.html

@@ -285,7 +285,7 @@ <h2>Preview builds</h2>
 					</li>
 					<li>
 						Follow the instructions from the
-						<a href="https://docs.godotengine.org/en/stable/contributing/development/compiling/index.html">official documentation</a>.
+						<a href="https://docs.godotengine.org/en/stable/engine_details/development/compiling/index.html">official documentation</a>.
 					</li>
 				</ul>
 			</div>

collections/_article/80-funded-celebrating-patreon-rewards-upgrade.md

@@ -14,7 +14,7 @@ I have to admit, the financial support that we got over the last two weeks has b
 When we started working on the Patreon page with Juan, we expected that it would take a few months and the publication of Godot 3.0 to bring us near to our $3,000 monthly goal which could secure us Juan's full-time dedication to the project.
 
 And here we are, two weeks in and already 80% funded, with barely $600 missing to reach our main goal - and it keeps growing [slowly but steadily](https://graphtreon.com/creator/godotengine), with a daily influx of new donors.
-We want to thank you all for your incredible support! Whether you [contribute to the engine's development](http://docs.godotengine.org/en/latest/community/contributing/ways_to_contribute.html) via code, bug reports, testing, teaching, developing awesome games or donating to the project, you all participate in making Godot!
+We want to thank you all for your incredible support! Whether you [contribute to the engine's development](https://contributing.godotengine.org/en/latest/organization/how_to_contribute.html) via code, bug reports, testing, teaching, developing awesome games or donating to the project, you all participate in making Godot!
 
 And this is also very invigorating. We are a non-profit project, dedicated to making the best free and open source game engine not for our own sake, but for anyone wanting to develop games.
 Seeing that we are able to crowdfund the development of our engine proves us the worth of our voluntary work as free software contributors, and that we are creating something really unique with Godot.

collections/_article/become-godot-contributor-hacktoberfest-2018.md

@@ -30,10 +30,10 @@ Here's how to get started:
 - The [*Hacktoberfest*](https://github.com/godotengine/godot/labels/Hacktoberfest) label on the [source code repository](https://github.com/godotengine/godot) lists some "newcomer-friendly" issues that you can have a look at. Note that you are not limited to those issues, you can work on anything you want - this selection is just a shortlist.
 - Similarly, the [*Hero wanted!*](https://github.com/godotengine/godot/labels/hero%20wanted%21) label also has a selection of issues ready to be worked on, where project maintainers or users have done enough initial debugging to point you in the right direction (see our [recent blog post](/article/hero-wanted-31-version) about the "Hero wanted!" campaign).
 - You can also browse all other issues of the code repository which are in the [*3.1 milestone*](https://github.com/godotengine/godot/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.1) (our main focus currently), and especially the ones [labelled as *bug*](https://github.com/godotengine/godot/issues?q=is%3Aopen+label%3Abug+milestone%3A3.1).
-- Have a look at the [contributor's documentation](http://docs.godotengine.org/en/latest/community/contributing/index.html), especially the [CONTRIBUTING.md](https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md), the [Pull Request workflow](http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html) and the [Code style guidelines](http://docs.godotengine.org/en/latest/community/contributing/code_style_guidelines.html).
+- Have a look at the [contributor's documentation](https://contributing.godotengine.org/en/latest/organization/how_to_contribute.html), especially the [CONTRIBUTING.md](https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md), the [Pull Request workflow](https://contributing.godotengine.org/en/latest/organization/pull_requests/creating_pull_requests.html) and the [Code style guidelines](https://contributing.godotengine.org/en/latest/engine/guidelines/code_style.html).
 - Join the [`#godotengine-devel`](http://webchat.freenode.net/?channels=#godotengine-devel) IRC channel on Freenode (also bridged on [Matrix](https://matrix.to/#/#freenode_#godotengine-devel:matrix.org)) to discuss with fellow engine contributors.
 
-If you want to work on the class reference, have a look at the [dedicated page](http://docs.godotengine.org/en/latest/community/contributing/updating_the_class_reference.html).
+If you want to work on the class reference, have a look at the [dedicated page](https://contributing.godotengine.org/en/latest/documentation/class_reference.html).
 
 ### Documentation contributions
 
@@ -42,9 +42,9 @@ To contribute to the [online documentation and tutorials](http://docs.godotengin
 Here's how to get started:
 
 - Check the [list of issues](https://github.com/godotengine/godot-docs/issues) and see if there's anything you'd like to work on.
-- Review the documentation on [how to write documentation](http://docs.godotengine.org/en/latest/community/contributing/documentation_guidelines.html) (yes, that has to be documented too!).
+- Review the documentation on [how to write documentation](https://contributing.godotengine.org/en/latest/documentation/guidelines/index.html) (yes, that has to be documented too!).
 - Join the `#documentation` channel on [Godot's Discord](https://discord.gg/zH7NUgz) server (most active place to discuss with fellow documentation contributors), or if you prefer the [`#godotengine-doc`](http://webchat.freenode.net/?channels=#godotengine-doc) IRC channel on Freenode (but it's less active).
 
-That's it! It's a lot of links and documentation, but you of course don't need to review everything in depth, look in priority at the [contributor's documentation](http://docs.godotengine.org/en/latest/community/contributing/index.html) and then pick something you'd like to work on.
+That's it! It's a lot of links and documentation, but you of course don't need to review everything in depth, look in priority at the [contributor's documentation](https://contributing.godotengine.org/en/latest/organization/how_to_contribute.html) and then pick something you'd like to work on.
 
 Enjoy your Hacktoberfest and have fun contributing to your very own engine!

collections/_article/bugs-lets-catch-em-all-saturday.md

@@ -31,5 +31,5 @@ You're free to join for one hour or for the whole day, the important is that we
 
 - [List of issues in the 3.0 milestone](https://github.com/godotengine/godot/milestone/4) (meant to be fixed before 3.0 is released, or eventually moved to the next milestone if non critical).
 - [List of "Hero Wanted!" issues](https://github.com/godotengine/godot/issues?q=is%3Aopen+is%3Aissue+label%3A%22hero+wanted%21%22).
-- [Contributing docs](http://docs.godotengine.org/en/latest/community/contributing/ways_to_contribute.html), especially the parts of the [PR workflow](http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html) and the [code style guidelines](http://docs.godotengine.org/en/latest/community/contributing/code_style_guidelines.html).
+- [Contributing docs](https://contributing.godotengine.org/en/latest/organization/how_to_contribute.html), especially the parts of the [PR workflow](http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html) and the [code style guidelines](http://docs.godotengine.org/en/latest/community/contributing/code_style_guidelines.html).
 - [#godotengine-devel on Freenode](http://webchat.freenode.net/?channels=#godotengine-devel)

collections/_article/dev-snapshot-godot-4-3-dev-1.md

@@ -17,7 +17,7 @@ Here are the highlights of this build, and you can also go ahead and read a more
 
 - Major refactoring of the rendering system ([GH-83452](https://github.com/godotengine/godot/pull/83452)), which paves the way to several big improvements coming soon ([here's one of them](/article/collaboration-with-google-forge-2023/)). In the meantime, please test anything and everything related to rendering. Even though this change has been rigorously evaluated by a multitude of experienced contributors, we, as always, rely on our community to make absolutely sure things are as smooth and stable as they seem.
 
-- The new Direct3D 12 rendering driver is here for all your Microsoft-adjacent cross-platform needs ([GH-70315](https://github.com/godotengine/godot/pull/70315)). Being based on proprietary technology, D3D12 support comes as an optional feature keeping the open source spirit of the engine intact. Make sure to check the [updated documentation](https://docs.godotengine.org/en/latest/contributing/development/compiling/compiling_for_windows.html) for compiling Godot with D3D12 enabled (there is also an [update regarding cross-compilation](https://github.com/godotengine/godot-docs/pull/8624) getting ready to be merged).
+- The new Direct3D 12 rendering driver is here for all your Microsoft-adjacent cross-platform needs ([GH-70315](https://github.com/godotengine/godot/pull/70315)). Being based on proprietary technology, D3D12 support comes as an optional feature keeping the open source spirit of the engine intact. Make sure to check the [updated documentation](https://docs.godotengine.org/en/latest/engine_details/development/compiling/compiling_for_windows.html) for compiling Godot with D3D12 enabled (there is also an [update regarding cross-compilation](https://github.com/godotengine/godot-docs/pull/8624) getting ready to be merged).
 
 - Multiple controllers can now contribute to input actions ([GH-84943](https://github.com/godotengine/godot/pull/84943)), which expands upon previous fixes to multiple devices triggering input at the same time.
 

collections/_article/dev-snapshot-godot-4-3-dev-3.md

@@ -66,7 +66,7 @@ In the [4.3 dev 1 snapshot](/article/dev-snapshot-godot-4-3-dev-1/), we introduc
 
 In this build however, we enabled Direct3D 12 support in our official builds, including the open source Mesa NIR library and Godot's D3D12 implementation. `dxil.dll` is still required, but not provided, so by default you will still only have access to the Vulkan backend. To enable the D3D12 support, you need to download the [DirectX Shader Compiler](https://github.com/Microsoft/DirectXShaderCompiler/releases), and copy the relevant `dxil.dll` file for your architecture next to your Godot editor or exported project's executable.
 
-We are still evaluating options for being able to provide a D3D12 support that works out of the box, without a proprietary component. But for now to test things you will have to do this manual step (or [compile from source](https://docs.godotengine.org/en/latest/contributing/development/compiling/compiling_for_windows.html#compiling-with-support-for-direct3d-12), which does it for you).
+We are still evaluating options for being able to provide a D3D12 support that works out of the box, without a proprietary component. But for now to test things you will have to do this manual step (or [compile from source](https://docs.godotengine.org/en/latest/engine_details/development/compiling/compiling_for_windows.html#compiling-with-support-for-direct3d-12), which does it for you).
 
 ### Editor theme and UX improvements
 

collections/_article/dev-snapshot-godot-4-5-beta-1.md

@@ -297,7 +297,7 @@ Internationalization has always been an extremely crucial part of the Godot proj
 
 Similarly, the ability to swap languages on-the-fly within the editor is now possible thanks to the efforts of [Tomasz Chabora](https://github.com/KoBeWi) in [GH-102562](https://github.com/godotengine/godot/pull/102562). Now users can preview *and* experience multiple language options in a single editor session.
 
-We also want to give a shout-out to all the translators who tirelessly work on localizing the Godot editor, the class reference and the online documentation. If you'd like to join that effort, head to [Weblate](https://hosted.weblate.org/projects/godot-engine/) and review our [documentation](https://docs.godotengine.org/en/latest/contributing/documentation/editor_and_docs_localization.html#doc-editor-and-docs-localization) for instructions.
+We also want to give a shout-out to all the translators who tirelessly work on localizing the Godot editor, the class reference and the online documentation. If you'd like to join that effort, head to [Weblate](https://hosted.weblate.org/projects/godot-engine/) and review our [documentation](https://contributing.godotengine.org/en/latest/documentation/translation/index.html) for instructions.
 
 ### Navigation
 

collections/_article/fill-blank-class-reference.md

@@ -15,13 +15,13 @@ The good news is, contributing to the class reference is quite easy; it's a (par
 
 ## Current status
 
-So that's where [we need YOU](http://docs.godotengine.org/en/latest/contributing/updating_the_class_reference.html). There was already an important effort before 2.0 to complete the class reference, but the work is far from finished. As of today, the class reference has 369 classes, 4420 methods, 1763 constants, 152 member variables and 142 signals. Out of which only 34% have proper descriptions so far. (You can get a nice overview for yourself using bojidar\_bg's awesome script in ``doc/tools/doc_status.py``)
+So that's where [we need YOU](https://contributing.godotengine.org/en/latest/documentation/class_reference.html). There was already an important effort before 2.0 to complete the class reference, but the work is far from finished. As of today, the class reference has 369 classes, 4420 methods, 1763 constants, 152 member variables and 142 signals. Out of which only 34% have proper descriptions so far. (You can get a nice overview for yourself using bojidar\_bg's awesome script in ``doc/tools/doc_status.py``)
 
 You can also see the detailed status in [this collaborative pad](https://etherpad.net/p/godot-classref-status) that we use to coordinate the contribution effort.
 
 ## How to help?
 
-Everything is described in the docs page [Updating the class reference](http://docs.godotengine.org/en/latest/contributing/updating_the_class_reference.html). Basically the workflow is to fork and clone Godot's source repository, edit the ``doc/base/classes.xml`` file and make a pull request for your changes.
+Everything is described in the docs page [Updating the class reference](https://contributing.godotengine.org/en/latest/documentation/class_reference.html). Basically the workflow is to fork and clone Godot's source repository, edit the ``doc/base/classes.xml`` file and make a pull request for your changes.
 
 For more efficiency, and because it's funnier to work on such things together (especially when you have questions about what a given method does), you are very welcome to join the [#godotengine-doc](http://webchat.freenode.net/?channels=#godotengine-doc) IRC channel on Freenode to discuss live with the rest of the documentation team.
 
@@ -38,6 +38,6 @@ So don't wait, and help us give Godot the documentation it deserves!
 ## Useful links
 
 - [Online class reference](http://docs.godotengine.org/en/latest/classes/_classes.html)
-- [Contributing to the class reference](http://docs.godotengine.org/en/latest/contributing/updating_the_class_reference.html)
+- [Contributing to the class reference](https://contributing.godotengine.org/en/latest/documentation/class_reference.html)
 - [Collaborative pad](https://etherpad.net/p/godot-classref-status)
 - [Recent class reference changes](https://github.com/godotengine/godot/commits/master/doc)

collections/_article/first-godot-3-docs-sprint-sept-9.md

@@ -13,8 +13,8 @@ After 5 docs sprints, the class reference **went up from 35% to 60% complete**!
 
 **3 steps to become a Contributor**
 
-1. Read the **[Contributor's Guide](http://docs.godotengine.org/en/latest/community/contributing/updating_the_class_reference.html)**
-2. Follow the **[Writer's Guidelines](http://docs.godotengine.org/en/latest/community/contributing/docs_writing_guidelines.html)**
+1. Read the **[Contributor's Guide](https://contributing.godotengine.org/en/latest/documentation/class_reference.html)**
+2. Follow the **[Writer's Guidelines](https://contributing.godotengine.org/en/latest/documentation/guidelines/docs_writing_guidelines.html)**
 3. Use the shared pad to **[tell us what you're working on](https://hackmd.io/s/H1es51Oeqb)**
 
 

collections/_article/godot-3-0-released.md

@@ -421,7 +421,7 @@ Godot 3.1 will bring a new and more powerful animation tree, modern occlusion cu
 
 You can greatly help us improve Godot, as well as make it faster and better. Besides contributing code (if you are a programmer), you can help us a lot by [becoming our patron](https://www.patreon.com/godotengine). Additionally, spreading the word will always benefit us, as most game developers still have never tried (or even heard of) Godot. Finally, the best contribution might be to use Godot to develop and publish awesome games!
 
-See our [community documentation](http://docs.godotengine.org/en/latest/community/contributing/ways_to_contribute.html) for a description of all the ways you can contribute to Godot and how.
+See our [community documentation](https://contributing.godotengine.org/en/latest/organization/how_to_contribute.html) for a description of all the ways you can contribute to Godot and how.
 
 Have fun with this long-awaited release!
 

collections/_article/godot-3-2-docs-sprint.md

@@ -35,15 +35,15 @@ Join me for a 4 hours livestream starting on Sunday, June 9, 11PM UTC. *The vide
 
 ## How can I participate? ##
 
-If you want to contribute to the code reference, starting by reading the [**Contribute to the Class Reference**](https://docs.godotengine.org/en/latest/community/contributing/updating_the_class_reference.html) page to learn about the workflow.
+If you want to contribute to the code reference, starting by reading the [**Contribute to the Class Reference**](https://contributing.godotengine.org/en/latest/documentation/class_reference.htmlhtml) page to learn about the workflow.
 
 
 I made a complete video tutorial to show you the entire workflow, explain the best practices, and my techniques to be as productive as possible:
 
 <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/5jeHXxeX-JY" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
 
-Then, you can get started anytime. If you feel like writing the reference straight, check out the [**Docs writing guidelines**](https://docs.godotengine.org/en/latest/community/contributing/docs_writing_guidelines.html), then make sure to check the [existing documentation-related issues](https://github.com/godotengine/godot/issues?q=is%3Aopen+is%3Aissue+label%3Adocumentation) to see what other contributors reported.
+Then, you can get started anytime. If you feel like writing the reference straight, check out the [**Docs writing guidelines**](https://contributing.godotengine.org/en/latest/documentation/guidelines/docs_writing_guidelines.html), then make sure to check the [existing documentation-related issues](https://github.com/godotengine/godot/issues?q=is%3Aopen+is%3Aissue+label%3Adocumentation) to see what other contributors reported.
 
 Use this shared document to let everyone know what you're working on: https://hackmd.io/@gdquest/godot-docs-sprint