What is a good software manual?

    I wanted to tell so many things, write so many things that you get lost from contemplating horizons of those, thoughts, considerations.

    It would probably be worth talking about the company and its projects, but this can quickly lead the reader into sadness and longing. Therefore, the first thing we decided to start with is to ask for advice.

    With the growth of the WELLtime project, our development team faced several questions. The developing software product provided the basis for the reorganization of the line of proposals, the change of priorities between its modules and gave a lot of interesting ideas.

    But these were one of the main expected areas of activity.

    We didn’t think and wondered, and, directly, we didn’t expect that the product would expect us to coordinate updating the reference material.

    It’s not easy to make a product, but writing a competent manual for it is not easier.
    Many interesting ideas and rational suggestions came up, but I would like to ask habro-people what is an indicator of a good software manual for them?

    Also popular now: