Changing the install type (vs code, sdk) should change the permalink, so we can share specific instructions

[sethladd]

Page URL

https://docs.flutter.dev/get-started/install/macos/web/

Page source

https://github.com/flutter/website/tree/main/src/content/get-started/install/macos/web.md

Describe the problem

When I switch between "Use VS Code to install" and "Download and install", that choice isn't permanent. When I make a choice, then I copy the URL to send someone, they aren't directed to the same view I was looking at.

Expected fix

When choosing between two methods, change the permalink. Something like #vs-code or #cli-sdk

Additional context

No response

I would like to fix this problem.

• I will try and fix this problem on docs.flutter.dev.

[parlough]

At least for these two particular examples, I recommend you share links to the newer https://docs.flutter.dev/install/with-vs-code and https://docs.flutter.dev/install/manual pages instead. These pages will also adapt to the OS of the user.

[sethladd]

Will https://docs.flutter.dev/get-started/install/macos/web/ be deleted , and replaced with https://docs.flutter.dev/install/with-vs-code or https://docs.flutter.dev/install/manual ?

Because https://docs.flutter.dev/get-started/install/macos/web/ is still the default path. home page > getting started > mac > ios , will land you on https://docs.flutter.dev/get-started/install/macos/web/

[parlough]

Good question :)

The goal is to replace the current get-started flow with a combination of https://docs.flutter.dev/get-started/quick and https://docs.flutter.dev/install#get-started that I've recently built up. Essentially recommending the quick flow but falling back to the get-started flow for developers the quick flow doesn't fit.

The change needs some approval/buy in though, as:

1. https://docs.flutter.dev/get-started/quick

• At least in its current form, assumes the developer is using VS Code (or a Code - OSS based editor) for simplest instructions.
• Doesn't give the developer a choice of an initial platform to set up so that they can try Flutter development, hot reload, and impactful dev tools (the sidebar, debugging, widget previews, mcp support, or whatever we want to highlight) quickly by targeting the web.

2. https://docs.flutter.dev/install#get-started

• Similar content to current flow, but reduced and simplified.
• Instructions for adding a platform (of their choice) is on separate pages that I've recently rewritten (such as Set up iOS development) to reduce duplication and make the steps able to be followed at any point of time.

If I can get buy in to that change (or a modified version of it), I will remove all content currently in the existing get started flow and bring users to the new, simplified one.

[sethladd]

Do you have a document with a list of the "before" and "after" ? that is, what exactly is the proposal that needs approval, and who do you need approval from?

I'd love to get to one set of install pages, glad you pointed out that we currently have two sets. Let's get this resolved. How can I help?

[parlough]

Do you have a document with a list of the "before" and "after"?

#11911 has some of the background. However, since a lot of the required docs already exist now, I opened #12341 as a good way to see a potential "after" compared to the before.

Who do you need approval from?

Platform owners mostly, as the quick start / happy path defaults to only setting up development for the web in favor of showing developers Flutter's developer experience faster.

[sethladd]

Thanks @parlough . Glad you opened #12341

We can close this issue, and get your changes landed. Then we'll see what kind of permalinking support we'll need.

Please work with @twerske to figure out the right path to land your changes and get to one set of install docs. Thank you!