You really should learn that skill because it's very important in most software companies, and mandatory for some fields like the healthcare industry. It is, like unit-tests or code coverage, a skill that makes a difference between a developer and a senior developer.
Also my pain point is when documentation is not written when it's so easy to use nowadays with files in a docs/ directory, wikis, or comments like Doxygen. We don't need more tools, we need discipline. I'm still trying to understand what your service could bring me, and why I would pay for this.
Last but not least, in the comparison page (https://documentationlab.com/blog/best-software-documentatio...), you describe Read the docs as a tool when it's only a web site to store user-generated content (from Sphinx or any other tool). That's why it's more confusing.
You really should learn that skill because it's very important in most software companies, and mandatory for some fields like the healthcare industry. It is, like unit-tests or code coverage, a skill that makes a difference between a developer and a senior developer.
Also my pain point is when documentation is not written when it's so easy to use nowadays with files in a docs/ directory, wikis, or comments like Doxygen. We don't need more tools, we need discipline. I'm still trying to understand what your service could bring me, and why I would pay for this.
Last but not least, in the comparison page (https://documentationlab.com/blog/best-software-documentatio...), you describe Read the docs as a tool when it's only a web site to store user-generated content (from Sphinx or any other tool). That's why it's more confusing.