| |
|
|
|
|
|
|
|
|
1. |
Record Nr. |
UNINA9910502623803321 |
|
|
Autore |
Bhatti Jared |
|
|
Titolo |
Docs for Developers : An Engineer’s Field Guide to Technical Writing / / by Jared Bhatti, Sarah Corleissen, Jen Lambourne, David Nunez, Heidi Waterhouse |
|
|
|
|
|
|
|
Pubbl/distr/stampa |
|
|
Berkeley, CA : , : Apress : , : Imprint : Apress, , 2021 |
|
|
|
|
|
|
|
ISBN |
|
|
|
|
|
|
|
|
Edizione |
[1st ed. 2021.] |
|
|
|
|
|
Descrizione fisica |
|
1 online resource (241 pages) |
|
|
|
|
|
|
Disciplina |
|
|
|
|
|
|
Soggetti |
|
Internet programming |
Open source software |
Web Development |
Open Source |
|
|
|
|
|
|
|
|
Lingua di pubblicazione |
|
|
|
|
|
|
Formato |
Materiale a stampa |
|
|
|
|
|
Livello bibliografico |
Monografia |
|
|
|
|
|
Nota di bibliografia |
|
Includes bibliographical references and index. |
|
|
|
|
|
|
Nota di contenuto |
|
1. Getting Started -- 2. Researching Documentation -- 3. Designing Documentation -- 4. Drafting Documentation -- 5. Structuring Sets of Documentation -- 6. Integrating Code Samples and Visual Content -- 7. Measuring Documentation Success -- 8. Working With Contributors -- 9. Maintaining Documentation -- 10. Wrapping Up. |
|
|
|
|
|
|
|
|
Sommario/riassunto |
|
Learn to integrate programming with good documentation. This book teaches you the craft of documentation for each step in the software development lifecycle, from understanding your users’ needs to publishing, measuring, and maintaining useful developer documentation. Well-documented projects save time for both developers on the project and users of the software. Projects without adequate documentation suffer from poor developer productivity, project scalability, user adoption, and accessibility. In short: bad documentation kills projects. Docs for Developers demystifies the process of creating great developer documentation, following a team of software developers as they work to launch a new product. At each step along the way, you learn through examples, templates, and principles how to create, measure, and maintain documentation—tools you can |
|
|
|
|
|
|
|
|
|
|
adapt to the needs of your own organization. You will: Create friction logs and perform user research to understand your users’ frustrations Research, draft, and write different kinds of documentation, including READMEs, API documentation, tutorials, conceptual content, and release notes Publish and maintain documentation alongside regular code releases Measure the success of the content you create through analytics and user feedback Organize larger sets of documentation to help users find the right information at the right time. |
|
|
|
|
|
| |