>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3533806. --> Reported by: [mlncn](https://www.drupal.org/user/64383) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Huh i'm probably in the wrong queue but drupal.org has a link that goes to <a href="https://new.drupal.org/download">https://new.drupal.org/download</a> and then *that* page has a "Build with Drupal core" link that goes to <a href="https://www.drupal.org/download">https://www.drupal.org/download</a> &hellip; which redirects back to <a href="https://new.drupal.org/download">https://new.drupal.org/download</a></p> <p>Not a great experience.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Ideally we have a prominent page that has both the releases information of <a href="https://www.drupal.org/project/drupal/releases/">https://www.drupal.org/project/drupal/releases/</a> <em>and</em> the instructions on using composer the recommended way (not pinned to a point release) but for now probably being able to get to whatever <a href="http://www.drupal.org/download">www.drupal.org/download</a> used to be, or at least <a href="https://new.drupal.org/download#drupal_core-2891986">https://new.drupal.org/download#drupal_core-2891986</a> if that hash, used by the JS to switch which download instructions are shown, worked like it ought to when going to the site (it does not).</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>