[WelcomeUX] Revisit "Interface overview"

[joaomoreno]

• The arrows are tiny, barely noticeable
• view errors and warnings points to the wrong spot. How do we maintain this, going forward?
• Where is Find and run all commands pointing to? There's nothing behind it to click.
• The text is hard to read because it overlays on top of existing text
• The text's content brings nothing new to the table
• I only noticed that keybindings are there after seeing my own screenshot in this issue

It just looks way out of style with everything else.

I suggest to open https://code.visualstudio.com/docs/editor/codebasics instead.

[joaomoreno]

Another thought: I believe the interactive playground is much more useful in bringing users up to speed with what we can do. Could we place that in the first position instead?

[chrmarti]

The reason we put the overview first and the playground last is our assumption that new users prefer to start with the most essential information and customization to make themselves feel "at home" and only after some exploring proceed to more detailed documentation like the playground.

Quick replies on the other points:

• Arrows need some more treatment, partly theme dependent (Dark+ looks better).
• View errors and warnings: Layout is currently static, tracked with [WelcomeUX] Help overlay is misaligned #18861.
• Find and run all commands points at an image of the command palette IF the window is wide enough, might need some tweaking.
• On "hard to read": Agree, needs theme-specific tweaking.
• On "nothing new": To new users, everything is new.
• On "keybindings": Agree, more theme-specific tweaking.

[rakkarage]

also if you move side bar right then the arrows still point to left side of screen

[vscodebot]

We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

[edburns]

We closed this issue because we don't plan to address it in the foreseeable future.

Can we at least get a little arrow pointing to the "remote" indicator in the lower left corner?