Jul. 29, 2023
Four years in technical writing
This month marks four years since I began my first technical writing job.
This month marks four years since I began my first technical writing job.
Hello, it’s been a while.
Lately, I’ve been researching and learning more about changelogs because I’m collaborating on a changelog template with another member in the Community docs working group. We plan to start with a changelog template and then develop a release notes template in the future.
Yesterday, I found myself in a bit of a conundrum. I migrated the repository for this site from GitHub to GitLab because I’ve been using GitLab lately and like it. Because I’m using a new Git provider, I needed to set up a new site from Git using Netlify’s UI. But every time I tried to deploy my site, I kept getting a “Looks like something went wrong!” error that really didn’t explain what was wrong.
Several awesome things happened after I gave my talk at WTD 2021.
In this last part of my Vale series, you’ll create a .vale.ini file, customize it, and apply styles to some Markdown prose.
Welcome to part two! In this part, you’ll learn how to configure the Vale CLI for your documentation needs. Before you dive into the tutorial, you need to learn a thing or two about the file that makes linting with Vale possible: the .vale.ini file.
If you didn’t read part one of the Vale CLI series, do that first!
I’m writing a short series on how to install, configure, and run Vale to help your documentation stay consistent. In this first part, you’ll install the Vale CLI.