- Issue created by @Grienauer
- 🇦🇹Austria Grienauer Vienna
after I created this issue there was some discussion over at slack.
https://drupal.slack.com/archives/C07B218LQH5/p1733151734862979
I think it is important to link it here.
TL;DR: everything is right how it was designed, and this is no bug or error. as there will be a complete new Drupal version on drupal.org this is a working way, to make that transition happen and in the end new.drupal.org will be redirected back to drupal.org links. - 🇺🇸United States hestenet Portland, OR 🇺🇸
This is actually deliberate, for a couple of reasons:
There are some technical reasons why new.drupal.org will run in parallel with www.drupal.org for a while - while content exists in both places.
We’re definitely concerned about the ranking of the new site as pages move. Having both D7 & modern Drupal coexist on www.drupal.org was our first choice, but routing the asset & API paths to make the pages complete is not something we can do on the timeline we’re being asked to deliver. For example, I think D7 & modern Drupal have the same Views autocomplete API path, so that can’t be routed reliably. A subdomain is more straightforward than a subdirectory for us
You can think of it a bit like the old.reddit.com vs new.reddit.com, except we are avoiding duplicated content, for example:
eg: https://www.drupal.org/about/11 → now redirects to https://new.drupal.org/about/11, so there aren’t two pages with the same content.As sections are migrated they are being 302 redirected and we're managing this in Google Site Owner Tools. Once all the content areas are fully migrated www. will take over fully.