TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Has anyone had experience with creating javadoc? How much effort does
this take? What are the pros and cons of javadoc versus the traditional
hardcopy/pdf/html documentation? The developers on my project team are
requesting the next release of documentation be done in javadoc. Any
words of wisdom out there?