Huh i'm probably in the wrong queue but drupal.org has a link that goes to https://new.drupal.org/download and then *that* page has a "Build with Drupal core" link that goes to https://www.drupal.org/download → … which redirects back to https://new.drupal.org/download
Not a great experience.
Ideally we have a prominent page that has both the releases information of https://www.drupal.org/project/drupal/releases/ → and the instructions on using composer the recommended way (not pinned to a point release) but for now probably being able to get to whatever www.drupal.org/download used to be, or at least https://new.drupal.org/download#drupal_core-2891986 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).
Active
Other
I'm going to temporarily direct that CTA to: https://www.drupal.org/project/drupal/#project-releases →
And then we can come back here and decide what the best destination for that CTA should be. (Maybe, as suggested in the summary, we can get the #anchor link to properly display the Core tab at the top).