My tech writing setup
In my previous post I covered my creative writing setup and the post proved quite popular, so I thank everyone who read and left comments for that. Next in this series of posts covering my various setups is my setup for technical writing. In this post I use the term “tech writing” to cover my documentation, blog post, and longer form technical writing work.
My technical writing setup is also far more defined and established, with less areas where I am “still deciding” what’s best for me. My setup is also often decided by established wider industry practices and company or client requirements, meaning I have less opinion and influence on tooling choices and process.
Planning
Much of my content planning depends on what my client or employer uses, be that GitHub, Jira, or something similar. Outside of those tools, I often turn to others to help flesh out ideas in my own head before diving into writing. Most of them overlap with the resources and discussion in my creative writing setup post.
Writing
This part of my process is where I have the most control and is probably of most interest to readers. I could probably almost have a separate post called “My VS Code setup”, as that’s mostly what this section is. I wrote something about the extensions I use for writing, but it was a long time ago and my…
