Daryl J. White

Documentation as the Knowledgeable Colleague

Tue, 10 Mar 2026 00:00:00 +0000

There’s a specific feeling you get when documentation actually works.

It’s not relief, exactly. It’s more like the feeling of asking a question and getting a straight answer from someone who knows what they’re talking about. Someone who anticipated what you needed, skipped the parts you already knew, and told you what to do without talking down to you.

How I Integrated Claude Into a Documentation Workflow — and What It Actually Changed

Tue, 10 Mar 2026 00:00:00 +0000

Photo by Pixabay on Pexels.

AI tools are everywhere in documentation conversations right now, but most of the discussion stays abstract. This is a concrete account of how I integrated Claude into MinIO’s documentation workflow:

what I used it for.
how I structured that use.
what it measurably changed about how the team worked.

The Starting Point

Technical documentation for a product like MinIO lives close to the codebase. Keeping it accurate means tracking software releases, triaging GitHub issues, auditing existing content, and staying current with a fast-moving engineering team. All while writing new content and updating existing content. The surface area is large and the feedback loops are long.

The Spokes of the Wheel

Sat, 07 Mar 2026 00:00:00 +0000

Photo by Adam Dubec on Pexels.

If you look at a standard corporate org chart, you’ll see neat little boxes. Engineering is over here, Product is over there, Sales is on the other side of the building (or the virtual workspace), and Support is tucked away in the corner.

Engineering the "Golden Path"

Thu, 05 Mar 2026 00:00:00 +0000

Modernizing Documentation at Cloud Scale

In the world of high-performance distributed systems, documentation is more than just a manual. Instead, the docs serve as a critical component of the user’s infrastructure. During my tenure as a Senior Technical Writer at MinIO, I transitioned from being a content creator to a “Documentation Architect.”

My GitHub contributions reflect the level of work:

My GitHub metric contributions for the year leading up to February 2026.

Documentation is the ultimate QA test

Wed, 28 Jan 2026 00:00:00 +0000

Photo by olia danilevich on Pexels.

There is a persistent myth that technical writers sit around waiting for a developer to “finish” a feature so we can write the documentation. In this version of reality, we are the stenographers of the software world, recording what happened after the dust has settled.

Feature - Node Maintenance

Mon, 22 Dec 2025 00:00:00 +0000

MinIO introduced a new feature to AIStor for taking a node offline for maintenance. For this feature, I needed to explain how the feature works. As an AIStor feature applicable both in Kubernetes and non-Kubernetes environments, it was also important to distinguish it from the similar kubectl cordon functionality system administrators would also be familiar with.

Some notes:

The quote block text used a shortcode in the theme we used to create admonitions.
For the diagram, I used a skill another team member had created for Claude to use for creating SVG diagrams.
Links in the text here are intentionally broken, but would have cross-linked to other pages in the docs.

AIStor allows you to temporarily remove nodes from active service for planned maintenance operations. Removing nodes allows administrators to gracefully take nodes offline without disrupting cluster operations, similar to the cordon functionality in Kubernetes. A cordoned node finishes in-flight operations and marks itself as unavailable for any other operation. Use this to do hardware maintenance on a node, complete operating system updates, or perform troubleshooting.

Explanatory doc - MinIO Warp

Tue, 07 Oct 2025 00:00:00 +0000

MinIO Warp is an open-source tool for testing storage performance. It allows you to plan capacity and make sure the infrastructure meets requirements.

After MinIO’s migration to Hugo for documentation, I went about the task of adding documentation for Warp that previously only existed in the upstream code repositories.

This particular document covers two types of tests Warp provides. I put it together using some existing documentation and code examples in the repository combined with a deep dive analysis of the code using Claude, a review by a MinIO team member that uses the product regularly during support calls, and my own testing.

Choosing a docs tool

Mon, 20 Jan 2025 00:00:00 +0000

Photo by Brett Jordan at Pexels.

In the Write the Docs Slack community, folks often ask how to go about deciding what documentation tool or set of tools is the right one to use. I have taken to replying often with a series of questions, instead of answering.

Why the Socratic method? Because tooling for docs is a very, very circumstance-specific choice. No one answer is correct. As I have often said in Write the Docs and elsewhere, I firmly believe that a good technical writer can create great docs with pretty much any toolset. Yes, even Microsoft Word, though we might shudder while doing so.

What technical writing can do

Mon, 22 Jan 2024 00:00:00 +0000

Photo by Startup Stock Photos from Pexels.

Curious about what a technical writer can do for you?

Here are twenty-five things you might find a technical writer doing in their job on any given day:

Interviewing a subject matter expert to learn more about what they are writing about.

This might be a product manager, project lead, developer, customer, salesperson, developer advocate, end user, nearly anyone who might touch or use what we are a writing about.

Focus on me

Sat, 27 May 2023 00:00:00 +0000

Photo by Jonas_Fehre at Pixabay.

As a guy in my mid-40s, my health is something that has become increasingly “in my face”.

I’ve never been someone who worked out. After developing Crohn’s disease in 2016, I did an elimination diet and lost 50 pounds. That led me to my lowest adult weight of 165lbs.

But in the years since, I’ve settled into a desk job as a technical writer and did nothing to maintain anything active. And my diet returned to something that approximated a standard American diet, though with some adjustments for allergies and other problematic foods.

Bloom

Tue, 07 Mar 2023 00:00:00 +0000

Photo by Greta Hoffman at Pexels.

He’d always been told to bloom where he was planted. But there were two very acute problems with this:

He wasn’t a flower.
He wasn’t planted anywhere, either.

Trevor rubbed his temples. Ms. Perez needed milk and eggs. Mr. Grant had a bulb to change that he couldn’t reach. The new couple in 4B wanted to try their sofa on a different wall. And he owed Yizzy three games of jacks with some ice cream.

The Sun Still Sets

Sat, 25 Feb 2023 00:00:00 +0000

Photo by Marek Piwnicki at Pexels.

One star peeped out in the darkening sky. A wispy cloud shrouded the crescent moon. Wind meandered over the ground, interrupted here and there by the jut of a line or the tower of a boulder.

Life had crawled here, once. Broken out of the top bit of crust and tried to shape the exterior to its whims. For the briefest of time, that life had even seemed in control.

Scent of Life

Fri, 24 Feb 2023 00:00:00 +0000

Photo by Lisa Fotios at Pexels.

The smell wafted under the door and enveloped her bed. It roused her from her phone screen with its intensity.

Childhood.

Friendships.

Love, and love abandoned.

Grief. Deepest, heart wrenching grief.

Laughter.

The pressure of exams.

The intoxication of the work triumph.

It was all there. Around her. Over her. In her lungs. Breath after breath.

Ten Fingers

Fri, 17 Feb 2023 00:00:00 +0000

Photo by cottonbro studio at Pexels.

Ten fingers rested on a lap.

Just that morning, they had gripped hard the handle of the spoon they used to stir together a batch of cookies. Later, they held and moved the pen across a letter to a friend on the other side of the ocean. Recently, they touched flowers along the trail as they took their evening walk.

Good Decisions

Thu, 16 Feb 2023 00:00:00 +0000

Photo by Ketut Subiyanto at Pexels.

Dane smiled as he walked over his threshold and set his bag on the side table. It had been a good day. Only good decisions today.

He reflected on each of those decisions in turn, amazed at how they furthered the world toward a better future, small as each was.

But as he emptied his pockets to put the bad decisions in the collection box, there was a moment of worry.

Swirl of Wind

Thu, 16 Feb 2023 00:00:00 +0000

Photo by Mikhail Nilov at Pexels.

The wind swirled and ruffled the blanket spread on the well-groomed lawn of the quad. Glancing over, Jace watched the fabric slowly rise and fall back as the air took it and let it go.

They laid back again and stared up at the passing clouds, wishing that, like the blanket, the tasks before them would let go. Clouds passed. A rabbit. A leaf. The wind swirled more.

Tall One

Thu, 16 Feb 2023 00:00:00 +0000

Photo by Pixabay at Pexels.

The tall one, leaning against the wall, sighed. “What will become of us? We’ve waited in shadows and darkness for so long.”

Her friend, laying on the flat surface where they could rest before the morrow’s demands replied, “Hard to say. It could really be anything.”

—

The master picked up the newest pencil she had laid against the window the day before.

The Crack

Thu, 16 Feb 2023 00:00:00 +0000

Photo by Monstera at Pexels.

Liam stared at the crack, like he did virtually all of the time here. There was no way for him to know whether the cot had melded to his back, or his back to the cot. Either way, they were basically a single entity now.

His back, the cot, and that crack. Sometimes he imagined shrinking into the crack and exploring the other side. Sometimes he imagined the crack opening wide and engulfing his space instead.

GitHub Tips and Tricks

Wed, 25 Jan 2023 00:00:00 +0000

Photo credit: by Sara Kurfeß at Unsplash.

I started using Git and GitHub for docs in 2019. It’s been a slow build, but I’ve finally started to learn some helpful ways of going about things. So there are two GitHub specific tips I want to share with you that have helped me out in my day to day.

Choose where a repo’s notifications go

For the longest time, I just let all of my notifications go to whichever default email address I had defined. This meant that all of my GitHub notifications wound up going to my work email, because work had the majority of the notifications.

Life Challenge Level Upgrade

Mon, 23 Jan 2023 00:00:00 +0000

Photo by Kaique Rocha at Pexels.

In early 2016, I followed other members of my family in dealing with a quite awful stomach flu. It wasn’t a fun thing, but it passed on as those things do.

Until it didn’t.

Onset

See, while the symptoms at first subsided, things got weird not too long after I thought I’d recovered. What do I mean by “weird”? Well, for starters, I worried that I was having appendicitis.

Caring for knowledge

Sat, 29 Jan 2022 00:00:00 +0000

Photo by Pixabay at Pexels.

Why is good knowledge care critical?

Every business, small or large, has a body of knowledge around its existence.

The business has one or more products or services it sells. It has processes for how to obtain, create, or use the products or services. It has sales documents and collateral. There are accounting charts and customer lists. How to manuals and vendors. Hire onboarding and competitive analyses. The knowledge goes on and on.

Six characteristics of good docs

Fri, 05 Nov 2021 00:00:00 +0000

Photo by Samson Katt on Pexels.

Good docs have (at least) six key characteristics:

Findable

For documentation to be worth the time spent creating it, the user needs to be able to get to those docs when a problem or curiosity creates a need for information. The best docs do nobody any good if they can’t put their hands or eyes on them when they need them.

Leaving Well

Thu, 07 Oct 2021 00:00:00 +0000

Photo by Alexas Fotos from Pexels.

There are many flavors of technical writing. Mine is software.

One of the constants of any software team is the change that comes with employee churn. People find new opportunities by joining your team. People find new opportunities and leave your team for elsewhere.

Editing and Gathering Feedback

Thu, 23 Sep 2021 00:00:00 +0000

Photo by Moose Photos from Pexels.

I would like to thank the tech writers in the Write the Docs Slack’s #lone-writer channel for bringing these ideas to the top of my mind.

Everyone suffers from a bias of familiarity when looking at our docs. Once you read something once, the next time you read it the mind can anticipate and insert what it remembers and expects to be there. This happens whether the expected word or phrase or punctuation is there or not.

What good are docs?

Sun, 05 Sep 2021 00:00:00 +0000

Photo by Suzy Hazelwood on Pexels.

Are docs a good investment?

One of the challenges every documentarian faces is justifying the investment in docs.

Whether that investment is

salary
training and professional development
expanded doc team
tooling
dev help for site development

It can feel like we technical writers are always battling it out for the company’s money. And, often, the experience is that the money for conferences or books or a new team member goes to other teams instead. Teams that have a clearer line of sight from work to the bottom line of the company’s P&L statement.

Community

Mon, 30 Aug 2021 00:00:00 +0000

Photo by Startup Stock Photos from Pexels.

Technical writing can be an introvert’s dream. (I know, I am one!) That said, there are two communities that every tech writer needs to develop to thrive in our work.

Network of co-workers and subject matter experts
Other tech writers for support and professional development

Why are these communities vital? And how does a tech writer go about developing them?

Feature Plan (sample)

Sun, 22 Aug 2021 00:00:00 +0000

In planning out a new feature, the Product Manager wrote out an issue card in GitHub for developers to reference. The card included the PM’s notes from visits on site with customers.

I updated the card by:

Removing extraneous verbiage
Adding sections and rearranging content
Updating references to existing product features

Some portions of the issue make sense within the broader product portfolio. Those have been left without further explanation in the edited card, as such additional information is already known to the development team.

Are good enough docs really good enough?

Sat, 21 Aug 2021 00:00:00 +0000

Photo by Brett Jordan at Pexels.

What makes a good technical document?

A good technical article, document, or topic has a few key points that make it stand out:

It understands the user and has empathy for the situation that brought them here, now.

Don’t miss this point. It’s key.

A good technical article has to be inside the mind of the user that’s come to the article.

Assetly (Concept Sample)

Wed, 18 Aug 2021 00:00:00 +0000

About this sample

The information below is about a fictitious software product, “Assetly.” I based Assetly on a real product I documented, though many details have changed in this document.

I wrote the original product document in Madcap Flare in consultation with a number of subject matter experts, including:

Product Manager
Developers
Quality Assurance team
Sales team members who championed the product
Product Team Executives

This sample reimagines the original document, now written in Markdown for use in this blog.

Assetly Group Schedule (Task Sample)

Wed, 18 Aug 2021 00:00:00 +0000

About this sample

The information below is about a task a user would need to complete in a fictitious software product, “Assetly.” I based Assetly on a real product I documented, though many details have changed in this document.

I wrote the original document in Madcap Flare based on my own use of the software.

During my use of the real product, I occasionally uncovered bugs or more complicated problems. When discovered, I created issue cards in the development team’s issue tracking system.

Is your information architecture showing cracks?

Fri, 13 Aug 2021 00:00:00 +0000

Photo by Ron Lach from Pexels.

You can’t hang out with knowledge management platforms for long without realizing that their structure, or, should I say, “architecture,” gets dated.

It cracks. It goes stale.

Stale knowledge, a litany

Knowledge stops functioning the way it did at the beginning.

The roads go awry.

There are turnabouts everywhere.

Dead ends.

So many dead ends.

Business Requirements (sample)

Thu, 12 Aug 2021 00:00:00 +0000

About this sample

For a job application process, I was asked to revise a sample business requirements document. The provided example was a template purporting to be notes from several different meetings.

I left the headings from the template as they were, but edited and formatted the contents of each section.

While the original sample was done in Word, I have recreated it here with Markdown, published by my SSG, Hugo.

Converting to Flare

Thu, 12 Aug 2021 00:00:00 +0000

My first job at a software company landed me in a software training role. While I learned a great deal about adult learning and best practices for knowledge transfer, my proudest achievement while I was there involved project management.

Our department had a catalog of 160 course manuals. These manuals varied in length from 20 pages to several hundred pages. These were course guides for the various training classes taught by everyone in our department.

So you've decided to convert your docs

Mon, 02 Aug 2021 00:00:00 +0000

Photo by Mat Brown from Pexels.

So you’ve done the work and you are ready to convert your docs from one tool to another.

I, too, have done this. Actually, I am on my third time through doing such a massive undertaking. This time, as a lone writer having to maintain docs in both the old platform and the new.

Choosing a doc toolkit

Mon, 12 Jul 2021 00:00:00 +0000

Photo by Cottonbro Studios from Pexels.

I have spent the last year at my current job working on transitioning our docs from Madcap Flare to Antora.

First things, Madcap Flare is a great tool. This is the third place I have worked that has used Flare for some form of documentation, and it does its job well. However, there are several factors that impacted the decision to move away from Flare to another tool.

Building a Portfolio Site

Mon, 28 Jun 2021 00:00:00 +0000

Photo by Vojtech Okenka from Pexels.

TL;DR

Here’s what I did to create this site and give myself a (well, almost) free site to build out a portfolio.

Create an account with a Git service provider.
I used GitLab I already had, but GitHub also works.
Select a starter template from Forestry.io for the desired SSG (static site generator) and create it on Forestry. Forestry.io automatically adds a new repository and branch on your Git provider.
(I used the Hylia template for 11ty.)
Authenticate with your Git service provider and import the site to Forestry.
Publish the site to Netlify.
Add content using Forestry.io’s headless CMS WYSIWYG editor, and Netlify automatically finds the changes as you make them and updates your site in nearly real time.

Update

In anticipation of different responsibilities brought on by a job change, I modified how I create my site.

My Tech Writing Journey

Sun, 27 Jun 2021 00:00:00 +0000

My journey into tech writing started in 2013.

Reynolds and Reynolds

Software Training

I started out my journey into the world of talking and writing about technology and software as a customer trainer at Reynolds and Reynolds. A provider of software and other services for car dealerships, I taught dealership personnel and new ReyRey hires how to use the accounting and payroll portions of the software.

I taught mostly online, interactive webinars over Webex, making use of their Hands-on Lab feature. I also taught in-person, intensive classes for dealership controllers and office managers and as a deep-dive into my specialty for recent Reynolds and Reynolds hires.