Once v2 will go live, will the docs still live under the /v2/ slug? And do we need to prepare for that?

Yes, we still need to prepare for that. I mainly need to work on this in the https://github.com/timber/docs repository.

I thought about moving the /v2/ slug to the main docs path (https://timber-docs.test/docs/). But then, all existing links that specifically link to v2 documentation will not work anymore. We would have to create redirects for those (complicated). And also, all links to v1 docs wouldn’t lead to the intended page.

The solution I think would work better is to keep the version in the path. The Laravel Documentation already does something similar (e.g. with a link https://laravel.com/docs/10.x/installation).

To make this work well, the following steps are needed:

• Make the homepage (https://timber-docs.test/docs/) show the v2 docs.
• Create https://timber-docs.test/docs/v1/ as an entry point for the v1 docs, but keep all v1 pages without /v1/ in the path.
• Show a banner in all v1 pages with an info that 2.x is the newer version. This could be similar to how Twig does this.
  

Once v2 will go live, will the docs still live under the /v2/ slug? And do we need to prepare for that?

Yes, we still need to prepare for that. I mainly need to work on this in the https://github.com/timber/docs repository.

I thought about moving the /v2/ slug to the main docs path (https://timber-docs.test/docs/). But then, all existing links that specifically link to v2 documentation will not work anymore. We would have to create redirects for those (complicated). And also, all links to v1 docs wouldn’t lead to the intended page.

The solution I think would work better is to keep the version in the path. The Laravel Documentation already does something similar (e.g. with a link https://laravel.com/docs/10.x/installation).

To make this work well, the following steps are needed:

* Make the homepage (https://timber-docs.test/docs/) show the v2 docs.

* Create https://timber-docs.test/docs/v1/ as an entry point for the v1 docs, but keep all v1 pages without /v1/ in the path.

* Show a banner in all v1 pages with an info that 2.x is the newer version. This could be similar to how Twig does this.
  ![CleanShot 2023-10-26 at 14 05 42](https://user-images.githubusercontent.com/2084481/278323869-bac48139-5df6-4e98-911e-e8aec56d5a31.png)

Let me know if you need some help with that @gchtr

Let me know if you need some help with that @gchtr

Thanks for offering your help. I will create a pull request in the docs repo that you can then test in a local environment.

@Levdbas I’ve created a pull request in timber/docs#80. I’d be happy if you could check that out!

Another fix in d7163f1 to make the section archives work, see timber/docs#80 (comment).