When you brain storm your product you modularize it. Why is your documentation still a linear pdf file.
Does each team of your product come up with different structure for your documentation? Are you spending time mearging all the different documentation
Are you going though long pdf files or a document structure trying to find the relevant information? Modular documentation helps your identify the correct section really fast. Plus the common stucture for the tech documentation makes it easy for the team to find the relevant information
As a startup you are hiring interns. They are coming and doing amazing work. But when they leave are you ending up calling them up every now and then asking for information?
Want to pause your project for a year and come back later? Frustrated that you dont remember critical details for your project? Our structure of tech documentation makes it possible to save non-technical information in the documentation without making it overwhelming
When you go from version 1 of your project to v2 of your product, only some of your modules change. Does that mean that you have to write a seperate documentation? No you dont. Just update the modules that changed, documentation tree for your new version of product is auto generated, saving you massive amounts of time.
Firefly unicycle is an open source personal transportation device. We love building products. It is an attempt to build a kickass hardware community in India. Would you not like to meet other kickass hardware developers just like you?