{"id":8659,"date":"2023-08-22T16:27:01","date_gmt":"2023-08-22T10:57:01","guid":{"rendered":"https:\/\/razorpay.com\/learn\/?p=8659"},"modified":"2023-08-22T16:27:01","modified_gmt":"2023-08-22T10:57:01","slug":"vs-code-as-a-documentation-tool","status":"publish","type":"post","link":"https:\/\/razorpay.com\/learn\/vs-code-as-a-documentation-tool\/","title":{"rendered":"VS Code as a Documentation Tool"},"content":{"rendered":"

VS Code as a Documentation tool? Sounds interesting? Unusual even\u2026<\/span><\/p>\n

As a technical writer myself, having spent over a decade in this field – I found it awkward when I first learnt from a colleague that Razorpay Documentation<\/a> uses VS Code for authoring. It was the second day at work, and I was still undergoing the Induction and Training sessions. My first thought was, \u201cDid I make the right decision? How did I miss asking about the authoring tool we use during my interviews?\u201d<\/span><\/p>\n

Perplexed and yet, curious about what was in store, I embarked on this journey. My very skilled colleague trained me on VS Code and how it can be used as an authoring tool. I was awed at both its simplicities as well as complexities at the same time.<\/span><\/p>\n

The \u2018Docs-as-code\u2019 approach<\/span><\/h3>\n

Before we talk about VS Code<\/a>, let us understand what \u2018Docs as Code\u2019 is.<\/span><\/p>\n

Documentation as Code or more popularly known as \u2018Docs as Code\u2019, refers to an ideology that you should treat documentation in the same way as you would treat coding, including using the same tools as code. Some examples include:<\/span><\/p>\n