Personal blog: https://neonvagabond.xyz/ (591,305 total words, written over 6 years; feel free to do whatever you want with it)
My personal github page: https://github.com/alexispurslane/ (I only recently switched to Zero-Clause BSD for my code, and haven't gotten around to re-licensing all my old stuff, but I give you permission to send a PR with a different license to any of them if you wanna use any of it)
There are 5 mini-tracks in the PRO version that let you practice more advanced and team based Git features. One of them let you do a full pull request workflow from making a fork to final merging.
Asuming that you have one of the editors installed already, you just install the extension and that's it. Technically, installing Git is also a part of the course, but most people also likely have it preinstalled.
All the versions—including the web version available through the gitbybit.com, as well the GitHub Codespaces version—all are compiled from the single source, which is a large React monorepo.
All the editors share the same VS Code internals and APIs, so once your extension works in VS Code, it'll likely work in other editors. The are different ways to distribute extensions for VS Code and clones, but that's a technical detail.
Design-wise, even if it's just VS Code, there are mutiple themes, dark modes, etc that may affect your content, so you have to keep reusing VS Code CSS styles and keep your own styling minimal so that the content look good on any crazy theme user might have installed. And on the web, you can carry VS Code theme variables to style things similarly to VS Code's base theme.
We were making game dev courses and needed videos with readable code snippets.
Since our output is React/SVG, text renders perfectly; it's actual text, not pixels. And if you spot a typo? Just edit the TSX. No re-prompting or re-rendering.
The best use case is for explainer videos with code, technical diagrams, or anything where clean text matters, though we have seen other use cases as well.
