Getting Started: Consider supporting stripped down version of markdown in walkthrough descriptions

[Tyriar]

I tried to use italics and code within the walkthrough tasks but it seems to be just plain text.

[digitarald]

@JacksonKearl seems like links should be also allowed to link to docs. What are your thoughts on also providing links that run commands (with parameters)? Could be scoped out for later, but it seems a common theme in current start pages and blank states in viewlets.

[JacksonKearl]

Yes, my thinking is to adopt something very similar to the views welcome contribution point based on general feedback about wanting more flexibility.

[JacksonKearl]

now support

``code``,  __italics__, and **bold** , along with [Commands](command:blah), [Links](https://aka.ms), and

[Buttons](command:blah or https://blah)

in addition we have the command:toSide:blah syntax to attempt to make some other editor group active before running the command, creating it if it does not exist already (and theres enough room to do so)

[JacksonKearl]

Oh, and the command syntax above should support JSON-encoded arguments as the query parameter:

[Open Markdown File](command:toSide:workbench.action.quickOpen?%22.md%22)
[Open Markdown File](command:toSide:workbench.action.quickOpen?%22.md%22)
[Open HTML File](command:toSide:workbench.action.quickOpen?%22.html%22)
[Add a keybinding](command:workbench.action.openGlobalKeybindings?%22md-to-html.convertToHTML%22)

[Tyriar]

Does this toSide thing only work with quickOpen? Should it be a quickOpenToSide command instead?