Investigate Getting Started Walkthrough flow

[cwebster-99]

We should investigate the flow we are encouraging in the Getting Started with Python walkthrough to ensure it reflects best practice's and the idealized use of the tool.

We currently guide users to:

• Create a Python file
• Select a Python Interpreter
• Run and debug a Python file
• Explore more resources

We also show a different flow if the user has a workspace open:

• Create a Python file
• Create a Python environment
• Run and debug a Python file
• Explore more resources

Some considerations are if we should encourage the user to open a folder instead of a file, where we should prompt the user to create an environment, if these tiles are in the best order, etc.

Ref #20649

[cwebster-99]

We could adapt our current views to reflect a more ideal flow (i.e. using a workspace, using a virtual environment, etc.)

For users that are visiting the getting started page with a workspace open when can encourage them to take the following steps:

• Create a Python file
• Create a Python environment
• Run and debug your Python file
• Explore more resources (could include information about compatible tool extensions)

For users visiting the getting started page with no workspace open we can encourage them to take the following steps:

• Create a new project folder
• Create a Python file
• Create a Python environment
• Run and debug your Python code
• Explore more resources (could include information about compatible tool extensions)

Currently in "Explore more resources" we have:

• Explore features in the command palette
• Link to Getting Start with Data Science in Python walkthrough
• Link to Release Notes
• "Learn More" button that leads to our tutorial

Changing the wording on the "Learn More" button to something more related to the tutorial might make new users more likely to interact with it. Perhaps, "Python Tutorial" or "Follow Along with the Python Tutorial"

[karrtikr]

Looks good. It would be great if we can somehow teach what "Select Interpreter" tile does as well. Something like: "Create a Python environment or use <...> to select an existing one".

[luabud]

good point on learn more, +1 to "Follow Along with the Python Tutorial"

I think the ideal would be to make #20249 happen, then we could just guide people on "Select Interpreter" from both flows 😁

[karrtikr]

When doing getting started or supporting a Create workspace command, I think we should prioritize "Create Environment" over the "Select Interpreter" list, as we want to encourage users to use an environment.

#20249 exposes "Create Environment" as a secondary option though 😅 so many users can simply end up choosing a global interpreter and moving on.

[cwebster-99]

I think we should prioritize "Create Environment" over the "Select Interpreter" list, as we want to encourage users to use an environment.

I agree, whichever one we think is more important should be the top level option, and then the nested one is secondary.

[luabud]

Yes good point. This is especially important when there isn't a virtual environment in the workspace (or a folder open).

Would the idea here be to expose a picker with "Create environment" and "Select an existing interpreter" first?

[karrtikr]

Would the idea here be to expose a picker with "Create environment" and "Select an existing interpreter" first?

I like it 🙂 kind of like mirror idea of #20249:

[cwebster-99]

Closing as this investigation is finished with the following issues as a result:

• Add a Python: New Workspace command #20649
• Provide Create Environment within the Select Interpreter quick pick #20249