63,75 €*
Versandkostenfrei per Post / DHL
Lieferzeit 1-2 Wochen
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.
What You'll Learn
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
Who This Book Is For
Ideal for software developers who need to create documentation alongside code, or for technical writers, developer advocates, product managers, and other technical roles that create and contribute to documentation for their products and services.
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.
What You'll Learn
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
Who This Book Is For
Ideal for software developers who need to create documentation alongside code, or for technical writers, developer advocates, product managers, and other technical roles that create and contribute to documentation for their products and services.
Jared Bhatti
David Nunez
Aligns the craft of writing with the craft of programming
Contains easy-to-follow processes, templates, and best practices for creating, organizing, and maintaining documentation
Written by experienced writers and developers from Google, The Linux Foundation, Stripe, LaunchDarkly, and Monzo,
Getting Started
- Researching documentation
Understanding your users
Cultivating empathy
- Understanding user desires, user needs, and company needs
Recruiting users for research
Research methods
- Reading code comments
Trying it out
Running diverse and inclusive focus groups and interviews
User journey mapping
- Identifying and working with stakeholders
Finding your experts
Collaborative documentation development
- Learning from existing content
The value of design documents
Finding examples in industry
- Designing documentation
Defining your initial set of content
Deciding your minimum viable documentation
- Drafting test and acceptance criteria
Understanding content types
Concepts, tutorials and reference documentation
- Code comments
API specifications
Guides
Release notes
- Drafting documentation
Setting yourself up for writing success
Who is this for? Personas, requirements, content types
- Definition of done
How to iterate
Understanding your needs
Choosing your writing tools (handwriting, text-only, productivity/measurement writing tools)
- "Hacks" to get started drafting content
Mechanics
Headings
- Paragraphs
Lists
Conclusions/tests
Using templates to form drafts
- Purpose of a template
How to derive a template from existing docs
Gathering initial feedback
Feedback methods
- Integrating feedback
Getting feedback from difficult contributors
Determine destination
Editing tools (Grammarly, linters, etc)
- Declaring good enough
Recap, strategies, and reassurance
Where content types live
Concepts, tutorials and reference documentation
- Code comments
API specifications
Guides
Release notes
- Designing your information architecture
Content information architecture styles
Designing for search
- Creating clear, well-lit paths through content
User testing and maintenance
Planning for document automation
- Integrating code samples and visual content
Integrating code samples
When and why to use code samples
- Creating concise, usable, maintainable samples
Standardising your samples
Using visual content: Screenshots, diagrams, and videos
- When your documentation may need visual content
Making your visual content accessible
Integrating screenshots, diagrams
- Videos
Measuring documentation success
How documentation succeeds
- Measuring different types of documentation quality
Structural Quality
Functional Quality
- Process Quality
Measuring what you want to change
Working with contributors
Defining how decisions are made
- Deciding on a governance structure
Writing an effective Code of Conduct
Choosing a content licence
- Code licenses
Content licences
Editing submitted content and giving feedback
Setting acceptability criteria
- Editing for accessibility and inclusion
Editing for internationalization and translation
Giving actionable feedback
- Planning and running a document sprint
Maintaining documentation
Creating a content review processes
- Assigning document owners
Performing freshness checks on content
Separating documentation issues from product issues
Responding to users
- Automating document maintenance
Automating API and reference content
Using doc linters
- Deleting and archiving content
Wrapping up
Friction logs
READMEs
Tools and tips for writing rough drafts
Notes and warnings
How to take templates into text
Editing content for publication
Structuring sets of documentation
READMEs
Drawing conclusions from document metrics
Building and enforcing a style guide
Responding to documentation issues
Erscheinungsjahr: | 2021 |
---|---|
Genre: | Informatik |
Rubrik: | Naturwissenschaften & Technik |
Medium: | Taschenbuch |
Seiten: | 252 |
Inhalt: |
xxv
225 S. 31 s/w Illustr. 225 p. 31 illus. |
ISBN-13: | 9781484272169 |
ISBN-10: | 1484272161 |
Sprache: | Englisch |
Ausstattung / Beilage: | Paperback |
Einband: | Kartoniert / Broschiert |
Autor: |
Bhatti, Jared
Corleissen, Sarah Waterhouse, Heidi Nunez, David Lambourne, Jen |
Auflage: | 1st ed. |
Besonderheit: | Unsere Aufsteiger |
Hersteller: |
Apress
Apress L.P. |
Maße: | 235 x 155 x 14 mm |
Von/Mit: | Jared Bhatti (u. a.) |
Erscheinungsdatum: | 01.10.2021 |
Gewicht: | 0,388 kg |
Jared Bhatti
David Nunez
Aligns the craft of writing with the craft of programming
Contains easy-to-follow processes, templates, and best practices for creating, organizing, and maintaining documentation
Written by experienced writers and developers from Google, The Linux Foundation, Stripe, LaunchDarkly, and Monzo,
Getting Started
- Researching documentation
Understanding your users
Cultivating empathy
- Understanding user desires, user needs, and company needs
Recruiting users for research
Research methods
- Reading code comments
Trying it out
Running diverse and inclusive focus groups and interviews
User journey mapping
- Identifying and working with stakeholders
Finding your experts
Collaborative documentation development
- Learning from existing content
The value of design documents
Finding examples in industry
- Designing documentation
Defining your initial set of content
Deciding your minimum viable documentation
- Drafting test and acceptance criteria
Understanding content types
Concepts, tutorials and reference documentation
- Code comments
API specifications
Guides
Release notes
- Drafting documentation
Setting yourself up for writing success
Who is this for? Personas, requirements, content types
- Definition of done
How to iterate
Understanding your needs
Choosing your writing tools (handwriting, text-only, productivity/measurement writing tools)
- "Hacks" to get started drafting content
Mechanics
Headings
- Paragraphs
Lists
Conclusions/tests
Using templates to form drafts
- Purpose of a template
How to derive a template from existing docs
Gathering initial feedback
Feedback methods
- Integrating feedback
Getting feedback from difficult contributors
Determine destination
Editing tools (Grammarly, linters, etc)
- Declaring good enough
Recap, strategies, and reassurance
Where content types live
Concepts, tutorials and reference documentation
- Code comments
API specifications
Guides
Release notes
- Designing your information architecture
Content information architecture styles
Designing for search
- Creating clear, well-lit paths through content
User testing and maintenance
Planning for document automation
- Integrating code samples and visual content
Integrating code samples
When and why to use code samples
- Creating concise, usable, maintainable samples
Standardising your samples
Using visual content: Screenshots, diagrams, and videos
- When your documentation may need visual content
Making your visual content accessible
Integrating screenshots, diagrams
- Videos
Measuring documentation success
How documentation succeeds
- Measuring different types of documentation quality
Structural Quality
Functional Quality
- Process Quality
Measuring what you want to change
Working with contributors
Defining how decisions are made
- Deciding on a governance structure
Writing an effective Code of Conduct
Choosing a content licence
- Code licenses
Content licences
Editing submitted content and giving feedback
Setting acceptability criteria
- Editing for accessibility and inclusion
Editing for internationalization and translation
Giving actionable feedback
- Planning and running a document sprint
Maintaining documentation
Creating a content review processes
- Assigning document owners
Performing freshness checks on content
Separating documentation issues from product issues
Responding to users
- Automating document maintenance
Automating API and reference content
Using doc linters
- Deleting and archiving content
Wrapping up
Friction logs
READMEs
Tools and tips for writing rough drafts
Notes and warnings
How to take templates into text
Editing content for publication
Structuring sets of documentation
READMEs
Drawing conclusions from document metrics
Building and enforcing a style guide
Responding to documentation issues
Erscheinungsjahr: | 2021 |
---|---|
Genre: | Informatik |
Rubrik: | Naturwissenschaften & Technik |
Medium: | Taschenbuch |
Seiten: | 252 |
Inhalt: |
xxv
225 S. 31 s/w Illustr. 225 p. 31 illus. |
ISBN-13: | 9781484272169 |
ISBN-10: | 1484272161 |
Sprache: | Englisch |
Ausstattung / Beilage: | Paperback |
Einband: | Kartoniert / Broschiert |
Autor: |
Bhatti, Jared
Corleissen, Sarah Waterhouse, Heidi Nunez, David Lambourne, Jen |
Auflage: | 1st ed. |
Besonderheit: | Unsere Aufsteiger |
Hersteller: |
Apress
Apress L.P. |
Maße: | 235 x 155 x 14 mm |
Von/Mit: | Jared Bhatti (u. a.) |
Erscheinungsdatum: | 01.10.2021 |
Gewicht: | 0,388 kg |