Fix the documentation links

src/components/features/FeatureFive.astro

@@ -19,7 +19,7 @@ import Verticalgrid from "../assets/VerticalGrid.astro";
         </p>
         <div class="mt-6">
           <a
-            href="https://docs.tuist.io/building-at-scale/caching"
+            href="https://docs.tuist.io/documentation/tuist/binary-caching"
             class="inline-flex items-center justify-center px-6 py-3 text-sm font-normal text-white bg-white/5 rounded-xl group focus:outline-none focus-visible:outline-2 focus-visible:outline-offset-2 hover:bg-transparent duration-200 border-2 border-white/10 active:bg-cyan-50 active:text-white focus-visible:outline-cyan-50 hover:border-white hover:text-white">
             Read more
           </a>

src/components/features/FeatureTwo.astro

@@ -552,7 +552,7 @@ l0 427 380 0 380 0 0 210 0 210 -377 2 -378 3 -3 318 -2 317 -23 -1 c-12 -1
           <div class="flex flex-col sm:flex-row">
             <a
               class="inline-flex items-center justify-center w-full px-6 py-3 text-center text-white hover:to-indigo-400 duration-200 bg-gradient-to-r from-sky-400 to-indigo-500 font-medium hover:bg-white/5 rounded-xl hover:text-white focus:outline-none focus-visible:outline-black focus-visible:ring-black"
-              href="https://docs.tuist.io/tutorial/get-started"
+              href="https://docs.tuist.io/documentation/tuist"
               >Get started
             </a>
           </div>

src/components/global/Footer.astro

@@ -86,7 +86,7 @@ import Blurgradientleft from "../assets/Blurgradientleft.astro";
               <li>
                 <a
                   class="text-sm text-slate-400 hover:text-white inline-flex items-center"
-                  href="https://docs.tuist.io/tutorial/get-started"
+                  href="https://docs.tuist.io/documentation/tuist"
                   >Documentation</a
                 >
               </li>

src/components/global/Navigation.astro

@@ -65,7 +65,7 @@ import metadata from "../../utils/metadata.json";
         >
         <a
           class="px-2 lg:px-6 py-2 md:px-3 text-sm text-white font-normal hover:text-white/50"
-          href="https://docs.tuist.io/">Docs</a
+          href="https://docs.tuist.io/documentation/tuist">Docs</a
         >
 
         <a

src/content/posts/2018/07/28/introducing-tuist.mdx

@@ -118,7 +118,7 @@ You can check out [the project issues](https://github.com/tuist/tuist/issues) th
 
 ## 📱 Start using it
 
-Would you like to give Tuist a try? You can check out the [Get started](https://docs.tuist.io/tutorial/get-started/) guide that explains how to install the tool and how to bootstrap your first project.
+Would you like to give Tuist a try? You can check out the [Get started](https://docs.old.tuist.io/tutorial/get-started/) guide that explains how to install the tool and how to bootstrap your first project.
 
 ## 📒 Resources
 

src/content/posts/2019/06/21/version-0.16.0.mdx

@@ -14,7 +14,7 @@ I'm happy to announce the release of Tuist 0.16.0; I'm going to talk through the
 
 Liking against system libraries and frameworks explicitly is sometimes necessary. This is a common use-case when using 3rd-Party frameworks such as Firebase.
 
-We've [added support](https://docs.tuist.io/usage-3-dependencies#system-libraries-and-frameworks-dependencies) for a new dependency type `sdk`.
+We've [added support](https://docs.old.tuist.io/usage-3-dependencies#system-libraries-and-frameworks-dependencies) for a new dependency type `sdk`.
 
 ```swift
 Target(
@@ -34,7 +34,7 @@ Target(
 
 ## Add input & output paths for target action 🎯
 
-If you use tools which need the ability to configure a pre-build or post-build script with input and output files, we now [have added support for both](https://docs.tuist.io/usage-2-manifest#target-action).
+If you use tools which need the ability to configure a pre-build or post-build script with input and output files, we now [have added support for both](https://docs.old.tuist.io/usage-2-manifest#target-action).
 
 ```swift
 .pre(
@@ -47,7 +47,7 @@ If you use tools which need the ability to configure a pre-build or post-build s
 
 ## Generate Tuist projects with _no_ build settings 🧬
 
-If you have a custom setup and don't want Tuist to provide any default build settings then [you are now able to specify](https://docs.tuist.io/usage-2-manifest#settings) `.none` for `settings` on `Project` or `Target`.
+If you have a custom setup and don't want Tuist to provide any default build settings then [you are now able to specify](https://docs.old.tuist.io/usage-2-manifest#settings) `.none` for `settings` on `Project` or `Target`.
 
 ```swift
 import ProjectDescription

src/content/posts/2019/11/19/version-0.19.0.mdx

@@ -53,7 +53,7 @@ Before this version of Tuist, it was not possible to enable test coverage in sch
 let test = TestAction.targets(["MyAppTests"], codeCoverageTargets: true)
 ```
 
-You can check the documentation of the `TestAction` model [here](https://docs.tuist.io/usage-projectswift#test-action).
+You can check the documentation of the `TestAction` model [here](https://docs.old.tuist.io/usage-projectswift#test-action).
 
 ## Defining the deployment target
 

src/content/posts/2019/12/27/version-1.1.0.mdx

@@ -8,7 +8,7 @@ author: pepicrft
 Tuist 1.1.0 has been released and is shorter than usual because we have committed to a fixed biweekly.
 In the past,
 users were in situations where their projects were pointing to commits in main.
-Although that's possible thanks to [Tuist's version management](https://docs.tuist.io/guides/version-management/), that's an undesirable state to be in.
+Although that's possible thanks to [Tuist's version management](https://docs.old.tuist.io/guides/version-management/), that's an undesirable state to be in.
 We chose two weeks as the cadence because a week is to short as to be able to ship noticeable changes,
 and more than two weeks likely leaves users waiting for improvements and bug fixes coming along with new versions.
 

src/content/posts/2020/01/31/version-1.2.0.mdx

@@ -13,7 +13,7 @@ Firstly, warm welcome to another first-time Tuist contributor [Maciej Piotrowski
 
 ## Future of Tuist
 
-There are plenty of ideas floating around what other features Tuist should have and [Pedro](https://github.com/pepicrft) laid them out in nicely in [The journey towards Tuist 2.0](https://github.com/tuist/tuist/issues/951). In addition, he also opened a work-in-progress PR for Tuist's [manifesto](https://github.com/tuist/tuist/pull/952). With more and more people joining the project it's very important to lay down the core principles in writing to ensure that everyone is up to speed. For more practical information we also have a new [Best Practices](https://docs.tuist.io/building-at-scale/best-practices/) section on the website. It is quite short at the moment, but will contain a growing list of things that can be useful for both new Tuist users and developers trying to improve their setup.
+There are plenty of ideas floating around what other features Tuist should have and [Pedro](https://github.com/pepicrft) laid them out in nicely in [The journey towards Tuist 2.0](https://github.com/tuist/tuist/issues/951). In addition, he also opened a work-in-progress PR for Tuist's [manifesto](https://github.com/tuist/tuist/pull/952). With more and more people joining the project it's very important to lay down the core principles in writing to ensure that everyone is up to speed. For more practical information we also have a new [Best Practices](https://docs.old.tuist.io/building-at-scale/best-practices/) section on the website. It is quite short at the moment, but will contain a growing list of things that can be useful for both new Tuist users and developers trying to improve their setup.
 
 ## Focus on improving performance
 

src/content/posts/2020/02/26/version-1.3.0.mdx

@@ -44,7 +44,7 @@ Moreover, we made [some improvements](https://github.com/tuist/tuist/pull/980) i
 As the project grows,
 it's crucial for users, contributors, and maintainers to know what are our design pillars.
 For that reason,
-we updated our documentation to include a [manifesto](https://docs.tuist.io/contributors/manifesto/) that contains a set of principles that are foundational to the design and development of Tuist.
+we updated our documentation to include a [manifesto](https://docs.old.tuist.io/contributors/manifesto/) that contains a set of principles that are foundational to the design and development of Tuist.
 They help align users and contributors with the vision of the project.
 
 ## Installation from Google Cloud Storage

src/content/posts/2020/03/16/version-1.4.0.mdx

@@ -50,7 +50,7 @@ we lint your project definition to uncover errors that otherwise would cause com
 If developers wanted to run the linting logic without generating the project,
 there was no option to do so.
 Fortunately, that changes with Tuist 1.4.0 because it introduces [a new command](https://github.com/tuist/tuist/pull/1043) `tuist lint`.
-You can read more about how it works on the [commands](https://docs.tuist.io/commands/linting/) documentation page.
+You can read more about how it works on the [commands](https://docs.old.tuist.io/commands/linting/) documentation page.
 
 If you are currently using Tuist,
 we recommend you to set up a CI pipeline that runs that command for every commit.

src/content/posts/2020/03/25/version-1.5.0.mdx

@@ -23,7 +23,7 @@ you can set up a new manifest called `Template.swift` to generate
 Then you can run `tuist scaffold framework --name MyFramework` and you're all set!
 Or if you want to create a new feature framework following VIPER architecture,
 you might call `tuist scaffold viper --name Home`. The possibilites are really endless 🙂
-To read more about how it works you can do so on [commands](https://docs.tuist.io/commands/scaffold/) documentation page.
+To read more about how it works you can do so on [commands](https://docs.old.tuist.io/commands/scaffold/) documentation page.
 
 We are excited too see what _you_ will be able to do with it!
 

src/content/posts/2020/04/21/version-1.7.1.mdx

@@ -33,7 +33,7 @@ let baseSettings: [String: SettingValue] = [
 
 This is not ideal. Having to repeat the strings manually and finding the possible values is not only tedious, but also
 might lead to errors, since typos in strings are a common problem. Initially, I found myself using a few functions in
-my [project description helpers](https://docs.tuist.io/guides/helpers/) to make the settings both type safety and to reduce duplication
+my [project description helpers](https://docs.old.tuist.io/guides/helpers/) to make the settings both type safety and to reduce duplication
 of the strings. I raised the topic in the Tuist Slack group and adding these functions to `ProjectDescription` was a
 welcome idea. This is exactly within the goals of Tuist: to make developers' life easier and the task of generating
 projects less error prone. From now on, the code above can be written like this:
@@ -44,7 +44,7 @@ let baseSettings = SettingsDictionary()
     .swiftCompilationMode(.wholemodule)
 ```
 
-[Refer to the documentation](https://docs.tuist.io/manifests/project/#settingsdictionary) to see the list of built in
+[Refer to the documentation](https://docs.old.tuist.io/manifests/project/#settingsdictionary) to see the list of built in
 functions, and also to learn how you can add your own to your project description helpers. If you find yourself using a
 function that others can leverage as well, don't hesitate to open a Pull Request adding them.
 
@@ -57,7 +57,7 @@ The refactor done to adopt the new parser required Tuist to have a better separa
 so our code is even better now 💪.
 
 Another contribution by Marek is the support for generating new SwiftUI-based project with the
-[new `scaffold` command](https://docs.tuist.io/commands/scaffold/).
+[new `scaffold` command](https://docs.old.tuist.io/commands/scaffold/).
 
 If you would like to see all the changes in this version, check them out in the
 [release page](https://github.com/tuist/tuist/releases/tag/1.7.0).

src/content/posts/2020/04/28/why-tuist.mdx

@@ -42,7 +42,7 @@ There are also build phases, targets, or schemes, for which Xcode doesn't provid
 Other teams resort to scripts that run some checks on the projects,
 but that results in a poor experience for developers because those checks are not built into their workflows.
 
-Tuist solves this by providing [project description helpers](https://docs.tuist.io/guides/helpers/).
+Tuist solves this by providing [project description helpers](https://docs.old.tuist.io/guides/helpers/).
 All you need to do is to define what types of projects are supported,
 and codify them into functions that return templated projects:
 

src/content/posts/2020/05/26/dynamism.mdx

@@ -32,11 +32,11 @@ At this point, you may wonder how Tuist relates to this dynamism I'm talking abo
 
 Here are some examples of things that we were able to provide by leveraging the dynamism of project generation:
 
-- Having consistency across projects and targets by leveraging [project description helpers](https://docs.tuist.io/guides/helpers/).
-- [Defining dependencies](https://docs.tuist.io/guides/dependencies) explicitly with a simple and unified DSL.
-- [Setting up](https://docs.tuist.io/commands/up/) the environment deterministically to ensure Xcode behaviors and builds are reproducible.
+- Having consistency across projects and targets by leveraging [project description helpers](https://docs.old.tuist.io/guides/helpers/).
+- [Defining dependencies](https://docs.old.tuist.io/guides/dependencies) explicitly with a simple and unified DSL.
+- [Setting up](https://docs.old.tuist.io/commands/up/) the environment deterministically to ensure Xcode behaviors and builds are reproducible.
 - Throw errors early when projects have invalid configurations.
-- Generating a [visual dependency tree](https:://docs.tuist.io/commands/graph/) to have an overview of the project.
+- Generating a [visual dependency tree](https:://docs.old.tuist.io/commands/graph/) to have an overview of the project.
 
 And we are not done yet. We are streamlining more workflows like configuring the environment and the projects for signing and providing a standard CLI without having to mess around with script files or configure a Ruby environment properly.
 
@@ -63,4 +63,4 @@ Still, it also leads them to waste time that they could otherwise spend building
 **Tuist takes care of those things, ensuring that we provide a consistent and easy experience that sparks joy.**
 
 If you have been there and think it’s time to clean things up and make working with your project as enjoyable as it used to be when you first created the project with Xcode,
-you can check out our [Get Started](https://docs.tuist.io/tutorial/get-started/) documentation.
+you can check out our [Get Started](https://docs.old.tuist.io/tutorial/get-started/) documentation.

src/content/posts/2020/06/11/marek.mdx

@@ -10,7 +10,7 @@ interviewee_avatar: https://avatars0.githubusercontent.com/u/9371695?s=460&u=c41
 
 This post is the first one of a series of interviews about how different companies in the industry are doing app development at scale.
 Our first interviewee is Marek Fořt, iOS developer at [AckeeCZ](https://www.ackee.cz/en), an app development studio based in the Czech republic.
-Marek is a core member of Tuist, and has been the brain behind features like [scaffolding](https://docs.tuist.io/commands/scaffold/), and soon signing management.
+Marek is a core member of Tuist, and has been the brain behind features like [scaffolding](https://docs.old.tuist.io/commands/scaffold/), and soon signing management.
 
 Let's dive right into Marek's experience doing app development at scale:
 
@@ -24,7 +24,7 @@ We have a platform-oriented _(iOS, Android, web...)_ teams structure - every tea
 
 ### What code paradigms and architectures do you follow?
 
-We use MVVM architecture with [ReactiveSwift](https://github.com/ReactiveCocoa/ReactiveSwift) for all of our projects currently, although we have also started experimenting with [Composable architecture](https://github.com/pointfreeco/swift-composable-architecture) and Combine since we think that Redux-like approach might be a better option once we start using SwiftUI. Along with the MVVM architecture we have also started using [microfeatures](https://docs.tuist.io/building-at-scale/microfeatures/) approach for one of our larger projects - this has had the benefit of better separation of concerns, faster build times, we have also introduced an example app for each individual feature which means it is extremely easy to concentrate on the task at hand. You can check out our [MVVM template](https://github.com/AckeeCZ/iOS-MVVM-ProjectTemplate/): we are planning to publish a revamped version with the microfeatures and composable architecture approaches.
+We use MVVM architecture with [ReactiveSwift](https://github.com/ReactiveCocoa/ReactiveSwift) for all of our projects currently, although we have also started experimenting with [Composable architecture](https://github.com/pointfreeco/swift-composable-architecture) and Combine since we think that Redux-like approach might be a better option once we start using SwiftUI. Along with the MVVM architecture we have also started using [microfeatures](https://docs.old.tuist.io/building-at-scale/microfeatures/) approach for one of our larger projects - this has had the benefit of better separation of concerns, faster build times, we have also introduced an example app for each individual feature which means it is extremely easy to concentrate on the task at hand. You can check out our [MVVM template](https://github.com/AckeeCZ/iOS-MVVM-ProjectTemplate/): we are planning to publish a revamped version with the microfeatures and composable architecture approaches.
 
 ### If you have multiple apps, how do you share code between them and how do you use internal tools to automate repetitive processes?
 

src/content/posts/2020/06/17/version-1.11.0.mdx

@@ -35,7 +35,7 @@ No figuring out how to set up the Xcode build settings as that is done for you.
 And as a plus your signing artifacts will be automatically encrypted with
 your key at `master.key`, so you can safely push it to your remote
 repository, so other team members can run the apps on a device, too ✨
-You can find more info in the [documentation](https://docs.tuist.io/commands/signing/)
+You can find more info in the [documentation](https://docs.old.tuist.io/commands/signing/)
 
 You can also check out an introduction video where we
 show you the feature in action:

src/content/posts/2020/06/28/soren.mdx

@@ -92,7 +92,7 @@ Apart from the setup of new apps it also turned out to be a big pain to maintain
 
 ### What’s the feature that you like the most from Tuist and why?
 
-There are so many nice features in Tuist already but I think the [project description helpers](https://docs.tuist.io/guides/helpers/) are my favorite. It allows us to generalize and reuse the way an app or framework is configured.
+There are so many nice features in Tuist already but I think the [project description helpers](https://docs.old.tuist.io/guides/helpers/) are my favorite. It allows us to generalize and reuse the way an app or framework is configured.
 
 ### Do you use project description helpers? If so, how? Would you mind adding a code snippet that illustrates your usage.