I have a new blog post up on the Twilio Engineering Blog about best practices for your company's documentation. The three main points:
Users are busy/lazy - you can't expect that they'll actually read anything, and you can't expect them to have any context, so make sure your code samples contain everything necessary to run the code.
Users are coming from Google - so you need to SEO all of your documentation content.
You are busy - so write the documentation first, when you're still excited about it.
The entire post is here - please take a look!
On a related note, I feel like I've been writing as much as I do usually, but sadly not all of it is visible to the public.
Liked what you read? I am available for hire.