Typically, documentation is the last mile of any data (science, engineering, visualization, etc.), engineering, or software-related project. This includes creating and editing documents such as…

Medium_JS is a curated collection of insights and tutorials on JavaScript development, designed to help developers stay informed and inspired in the ever-evolving world of web development. By featuring a selection of high-quality articles, tutorials, and expert opinions from the JavaScript community, Medium_JS offers  guidance on mastering JavaScript language features, exploring modern frameworks and libraries, and solving common development challenges. Whether you're a frontend developer, a full-stack engineer, or an aspiring JavaScript enthusiast, Medium_JS provides a  knowledge and resources to fuel your JavaScript journey.

Medium

This post reviews the author's favorite VScode extensions for documentation, including Quarto, Jupyter, and Markdown All in One.

VScode Extensions for Documentation

I prefer the excalidraw over <a href="http://draw.io" target="_blank" rel="noopener nofollow">draw.io</a> extension any day

I personally love <a href="https://marketplace.visualstudio.com/items?itemName=jebbs.plantuml" target="_blank" rel="noopener nofollow">plantUML</a> and the plantUML <a href="https://github.com/plantuml/plantuml-stdlib" target="_blank" rel="noopener nofollow">stdlib</a> together with the <a href="https://c4model.com/" target="_blank" rel="noopener nofollow">C4</a> model to document architecture.

I need to get that <a href="http://Draw.io" target="_blank" rel="noopener nofollow">Draw.io</a> VS Code extension! Great article.

While this may sound purely subjective since there are features (pragmatic capabilities) and cosmetics (visually appealing) involved, after evaluating pretty much all the common tools, I still get back to <a href="http://draw.io" target="_blank" rel="noopener nofollow">draw.io</a>, using it as a desktop app (not the Web UI, nor the VSCode extension).