If you're not including an llms.txt file for your docs, you need to. Optimize for AEO early and get the most from AI searches. It's already stealing tons of traffic from traditional search, and that trend is only going to continue upwards. Make sure that answer engines can see your docs!

Context really is king when working with AI. Pair that with the premise "what you put in is what you get out," and it's clear why some people think AI is useless and others praise it for its effectiveness. How well you can instruct a model to perform a task matters, and that comes from experience.

LLM traffic is projected to jump from 0.25% of search in 2024 to 10% by end of 2025. Insane growth. Structuring your docs for this wave of AI use will separate the useful from the ignored. Humans come first, but bots are reading, and they’re shaping what people find.

Organize! Protest! Make your voices heard!

America IS worth fighting for! Don't give in to despair and hopelessness! Don't wait 4 years to vote again. Take action now!

It's not optional.

Accessibility in documentation isn't just about headings and alt text, it's about making sure that anyone can use your site. Using high contrast color pallets and incorporating assistive tools like screen readers, AIRA labels, and keyboard-only nav helps make sure anyone can engage with your docs!

The rise of visually engaging content is reshaping technical writing. Nowadays, docs are all about interactive charts, tutorials, and visualizations.

How can you learn a topic if you aren't engaging with it? These don't just make docs look pretty, they increase their effectiveness!

Many people trying to break into Tech Writing aren't sure where to start. My advice? Learn Git and build a public portfolio by contributing to open source projects. Many projects are looking for docs and labeled as beginner friendly. github.com/search?q=is%...

When you really need that review

Docs are an essential part of UX. When learning something new or encountering a problem, the first place users turn is the docs. In that moment, your documentation becomes the working face of your company. Clear, concise, and accurate product documentation builds trust and drives adoption.

Tech writers are like modern-day Hemingways. His iceberg theory fits us perfectly: show the essential, hide the rest. Write for your audience—give them what they need, nothing more, nothing less. Our job is to distill the complex into something clear, concise, and actionable.

Brevity in technical writing isn’t about saying less—it’s about saying exactly what's needed to guide and inform users without causing frustration. In a world increasingly shaped by short-form content that trains us to skim and swipe, clarity and purpose in writing are more important than ever.

Too many companies out there today treat their documentation like an obligation instead of the opportunity that they are. You can turn your documentation into a data goldmine with the right tools. Why wouldn't you want to know how your docs are performing, or what your users struggle with?

Treat your docs like a product! Prioritize user needs, iterate based on feedback, and treat it as a core part of the experience. Good docs lower support costs, improve adoption, and build trust. When docs are clear, helpful, and accessible, they become a competitive advantage, not an afterthought.