(reference) VS Code Extension Dev

make sure you’re on pretty recent vs code
Extensibility points
- good overviews:
  - Visual components: https://code.visualstudio.com/api/extension-capabilities/extending-workbench
  - All contribution points: https://code.visualstudio.com/api/references/contribution-points
- commands (that come up with you hit ctrl+shift+p)
  - https://code.visualstudio.com/api/references/commands
- the activity bar (the thing on the far left - I think we end up with just the dark icon)
- the status bar (at the very bottom of the editor)
  - https://code.visualstudio.com/api/references/vscode-api#StatusBarItem
- tree view (the thing in my screenshot in codegen)
  - https://code.visualstudio.com/api/extension-guides/tree-view
- web views (custom html/css/js to display whatever we want)
  - docs: https://code.visualstudio.com/api/extension-guides/webview
  - vscode-webview-ui-toolkit
- context menus (what happens when you right click on something)
- custom editor (if we do allow clicking on a .dark file, this will allow us to have a custom editor)
  - https://code.visualstudio.com/api/extension-guides/custom-editors
- what should happen when the extension 'starts'? when it 'ends'? (this is called 'activation' and 'deactivation')
- walkthroughs
  - https://code.visualstudio.com/api/references/contribution-points#contributes.walkthroughs
- theming (not a priority, but theming the editor to 'feel like dark' is something I'd like)
  - https://code.visualstudio.com/api/extension-capabilities/theming
- extending the debugger experience
  - https://code.visualstudio.com/api/extension-guides/debugger-extension
deployment flow
general VS Code development
- https://code.visualstudio.com/api/extension-capabilities/common-capabilities
- executing environment
Unorganized
in-browser editing experience (may or may not be possible for us)
- https://vscode.dev/
- https://github.dev/github/dev
- "coder”

current state / hand-off notes