Experience with Git and Docs-as-code
Contents
Git I’ve about three years of experience using Git and its command line. With ten+ years of experience using Unix and Linux shell scripts, I don’t have any problem using Git and its command-line. In contrast, they allow me to work more efficiently. I use Git to store my projects, host my websites, and collaborate with others.
Docs as code Docs as Code refers to the concept that technical writers write docs with the same tool-chain as developers, using issue trackers, version control, plain text markup, code review, and automated tests, integrating the documentation process with the development workflow. It also allows developers to contribute their first draft to the new product conveniently. Its tool-chain mainly includes a version control system, plain or markup text editor, static website generators, etc. The outcome is continuous integration and delivery, making the software production more effective and technical writing and publishing more efficient.
I have extensive work experience with Git, VS Code, Atom, static website generators, and Restful API documentation. Even when I put the HTML page on WordPress, I often use the Code editor instead of the Visual editor, as using Code mode is faster and more convenient. I always use VS Code and Git when creating online documentation. I can quickly integrate with your documentation workflow that treats docs as code.
Static Website Generator I have working experience with static site generators; my GitHub portfolio site was generated using Hugo.
Author Susan
LastMod 2022-01-27