A technical communicator's travel blog about the impressive land of developer experience and the deep waters of API usability
MkDocs—“make documentation”. 🤖 The static site generator MkDocs builds HTML output (a website) from Markdown source files, which you edit in the text editor of your choice, like Notepad++, Atom, Sublime or others. The very convenient thing about MkDocs is: it renders the output while you edit. That is, whenever you hit “Save” for the… Continue reading MkDocs: Write in Markdown, get a website
It's time for the Git cheat sheet for writers! Read why General command structure: command -o --option argument "another argument, containing blank spaces" Note that Git commands always start with the prefix git whereas Unix commands do not carry a prefix. Unix commandDescriptionpwdPrint working directory = tell me which folder I am inlsList all items… Continue reading Git & Unix cheat sheet
Part 1: Why you need to learn Git for Docs as Code Docs as Code. What? In the software industry, technical writers work close to developers, especially when writing developer documentation, that is, documents that have other developers as target users. The idea of Docs as Code is to employ the same workflows for the… Continue reading How I learned Git, forgot it, and re-learned it
API docs and me 