[Feature] Document helpful VSCode / XML tricks for usability

[katyhuff]

What's needed

Part of the workshop will need to guide users in the facilitated use of VSCode for XML file navigation. It may be helpful to have a quick reference cheat sheet for their use.

Describe the feature you'd like.

Create, in the gh-pages branch with the various keybindings and typing shortcuts and cute menu helpers in the GitHub Codespaces environment.

Describe alternatives you've considered.

I considered nothing.

Additional context.

@gonuke knows a ton of these tricks. Probably also anyone else who

How can this issue be closed?

Create a page in the gh-pages branch jekyll site.

[gonuke]

Popup currently valid grammar: "<"

[abachma2]

Creating a list of tips/tricks:

• Using some key stroke shortcuts that typically exist in VS Code are overwritten by browser keystrokes (e.g., Ctrl+n will give a new browser window instead of a new, blank file.
• Autocomplete: type < to see a list of options for XML tags at that level -- need the schema file text at the top of the input file for this to work. Otherwise it just gives you options of whatever tags you have already used.
• For autocomplete, putting in some of the lower-level tags will prompt a lightbulb that provides options to fill in all required or possible lower-level tags. Do not use for <facility>, as that will put in all lower-level tags for all of the possible facilities.
• Use Ctrl+` to toggle between the terminal and a file.

[munkm]

We probably want to limit our tricks to those in codespaces and separate out tricks that exist in VSCode but aren't in codespaces.

[dean-krueger]

On my Mac in safari I can do control-space to get the autocomplete window to pop up