Excellent work with v1 @mikenikles! I really like the tone of it. Some small suggestions for improvement:

• At the end of each section add a 'Next button' to move e.g. from 'What is Gitpod?' to 'Prebuilds do the heavy lifting'
  • Blocked by Allow extension contributed walkthroughs to specify a "Next section" link. microsoft/vscode#129735
• For the CTAs (click here for e.g. the docker command, open ports) kumquat coloured buttons will work better
  • Enabled kumquat colours for the Gitpod Light (default) & Gitpod Dark themes.
    Screenshots

    Light	Dark

• Describe in 'Full access to a terminal' the shortcut how to open one (or let the button ^ do all the work)
• Include a button at the VS Code Desktop Support that does the same as Gitpod: Open in VS Code

And another thing: I think the Get Started with Gitpod onboarding flow should replace the Welcome Tab (or open as the primary one next to the Welcome one)

• Include a button at the VS Code Desktop Support that does the same as Gitpod: Open in VS Code

Would be great to fit a Open in VS Code: Insiders there, too!

At the end of each section add a 'Next button' to move e.g. from 'What is Gitpod?' to 'Prebuilds do the heavy lifting'
Blocked by microsoft/vscode#129735

For the CTAs (click here for e.g. the docker command, open ports) kumquat coloured buttons will work better
✅ shipped

Describe in 'Full access to a terminal' the shortcut how to open one (or let the button ^ do all the work)
👍. We have to consider operating-system dependent shortcuts. Will see what we can do.

Include a button at the VS Code Desktop Support that does the same as Gitpod: Open in VS Code
👍. Will see what's possible in v2

Get Started with Gitpod onboarding flow should replace the Welcome Tab
✅ shipped

That's already there if you click either of the links, unless I misunderstand what you're looking for.

What I meant is having a real button :)

💡 Let's use the first step of the Gitpod onboarding walkthrough as a "What's new?" step where we highlight the most recent changelog entries.

Ideally, IMHO, the changelog is more prominent than that, but adding it to the walkthrough is better than no in-product changelog or a very limited "What's new" dialog.

When should we show walk through? Right now it pops up each page reload. It's very annoying. Should we remember that a user seen it already and if does not change since then don't show it again?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

I believe this should still be open, it's still a good idea to update the onboarding exp

Thanks Filip. Yes Anton, that sounds like a sensible approach.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.