When I click on the text link to Astro Studio in Astro Docs, I get a 502 error.

[Yusaku01]

Overview

When I click on the text link to Astro Studio, I get a 502 error. Has Astro Studio perhaps been discontinued? The following situation:

Source

According to the official article (https://astro.build/blog/goodbye-astro-studio/), it seems it ended in March 2025. So, perhaps the links for existing users are no longer available?

Device and environment used for checking

• M1 Macbook Air
• Chrome 145+
• English（language version on the Docs）

In my opinion

I think guidance for existing users is necessary. However, if existing users encounter a 502 error when accessing that link, should the text link itself still be present? Even if you are a long-time user, if the link results in a 502 error, I personally feel that it would be fine without the link.🤔🤔

However, for individuals who have previously used Astro or Astro Studio and are now resuming its use after a considerable hiatus, it would be more considerate to retain the links as well, facilitating an easier catch-up on the evolution from past to present. This presents a challenge.😅

[delucis]

I think we can probably start thinking about removing this section. It’s been >1 year that Studio shut down and usage was never super high. So seems safe to remove!

[Yusaku01]

Yes, it's been over a year indeed. If we're removing it, would that just mean removing the link itself? Even though that Studio has shut down, removing the entire section might inconvenience some users🤨？

[Yusaku01]

The Current situation note:

• Some maintaners agree with remove the section and link.
• So Chris fixed it so that the studio subdomain just redirects to our main landing page.
• Finally, I've confirmed that the link to the Studio dashboard now redirects to the top of the LP. The issue with it going to the 502 page is fixed for now.

So, I haven't changed the sections or the content themselves, but I think I've managed to prevent the issue where users accidentally click on links that lead to 502 error pages.

I think this is resolved for now, so I'm going to close this discussion. If we need it again later, we can just refer back to it or reopen it.