Consider what content to include in built-in walkthroughs

[daviddossett]

Ref #165846

My hunch is that there is an opportunity to get more crisp on what we want users to know in the first seconds/minutes of using the product and reflect that in the getting started experience.

In general, it feels like the specific steps of the walkthroughs are somewhat arbitrary in their order and grouping. My sense is that users wouldn't know which section contains what content by looking at the titles alone. And sometime the titles say one thing where the content implies another. Example: "Get Started with VS Code" is framed as customization, but the steps are related to productivity-boosters like the command palette. Or basic JTBD like opening your code.

These aren't exhaustive comments, but some "first" impressions with fresh eyes:

Get Started with VS Code

Settings sync feels like a advanced feature to throw in as a second step in the very first walkthrough. And should opening your code be much higher up the list? Seems like a grab bag of activities here.

Learn the fundamentals

This also feels like a mixed framing re: features vs. outcomes. What is the goal of this section? Is it coding faster/smarter, or learning about features like the terminal or settings?

Boost your productivity

While shortcuts and side-by-side fit nicely here, using git feels like a core concept that might be better served in an earlier walkthrough.