Technical audiences know documentation websites are the real product pages.  Users go here to learn the real story about what something really does. You have to nail these. Docs shouldn't be an afterthought but often we are too busy to take care of them the way they need to be taken care of.  They can't be dry or references and they benefit from examples and context.

Users must be able to learn a product quickly, understand it, and get the feeling that it will be easy to learn and live with - that it will be productive and even fun to use. Used strategically, a documentation website that readers return to can be a great way to make them aware of ongoing events, new features, or offerings.

Michael spent 40% of his time in his CTO days on documentation (yes, really) and it paid off, and we want you to be just as successful. 

Typical offering:

  1. High-bandwidth (i.e. video) discussions with possibly 2-4 members of the team to understand the product
  2. Getting up to speed with the technology and asking questions
  3. Building the an outline/skeleton of content to include
  4. Opportunity for discussion
  5. Building the draft version of the website (typically using docusaurus, Sphinx, etc), aiming to address learning needs for multiple learning styles and educational/technical backgrounds.
  6. More discussion!
  7. Refinement
  8. Handoff - including instructions for upkeep/maintenance

Typical projects last about a month.  Prices start around $10,000 for a up to 10-15 page documentation site from scratch and scale with depth and technical complexity and effort.  Pricing may scale up depending on product complexity.

Help should be made readily available for product questions.  

This project can include sketches of diagrams/graphics that are suggested, where relevant. Custom CSS/Theming or final graphic design is not included, but we'll use a good default theme/plugin for the chosen documentation system.