21
Writing the docs Mikko Ohtamaa PLOG / 2013 Sorrento, Italy Friday, April 5, 13

Writing the docs

Embed Size (px)

DESCRIPTION

This presentation was held in PLOG2013, Sorrento, Italy. It's about good software development documentation culture, writing documentation for Python packages and maintaining up-to-date developer documentation in Plone ecosystem.

Citation preview

Page 1: Writing the docs

Writing the docsMikko Ohtamaa PLOG / 2013

Sorrento, Italy

Friday, April 5, 13

Page 2: Writing the docs

Agenda

The culture of good documentation

Documenting Python code

Documentation tools in Plone

Friday, April 5, 13

Page 3: Writing the docs

Mikko Ohtamaa

Looking

for work

opensourcehacker.com

Open Source Hacker

103323677227728078543

moo9000

Friday, April 5, 13

Page 4: Writing the docs

Am I a bad person If I don’t write

documentation?

Friday, April 5, 13

Page 5: Writing the docs

YES.

Friday, April 5, 13

Page 6: Writing the docs

Peer-driven culture vs. product-driven culture

Friday, April 5, 13

Page 7: Writing the docs

http://blog.gerv.net/2013/03/why-the-smart-people-leav/Friday, April 5, 13

Page 8: Writing the docs

Arch of Doom

Story begins with happy peers

Outsourcingcompanies start

using your product“German breakfast time”Populari

ty &

happiness

Time

Friday, April 5, 13

Page 9: Writing the docs

“No gaps, no questions needed”

documentation is necessary for the project to scale

Friday, April 5, 13

Page 10: Writing the docs

Don’t worry ☠Friday, April 5, 13

Page 11: Writing the docs

How to doc Python

README.rst (PyPi, Github, .egg)

Sphinx

Autodoc

readthedocs.org, pythonhosted.org

Well-commented unit tests

Friday, April 5, 13

Page 12: Writing the docs

developer.plone.org

( like stateful readthedocs.org with buildout )

( like a boss )

Friday, April 5, 13

Page 13: Writing the docs

Consumers of Plone the project are

developersFriday, April 5, 13

Page 14: Writing the docs

d.p.org ingredients

Body of knowledge

Tutorials

External package documentation

Graveyard of old documentation

Discover

ability

Friday, April 5, 13

Page 15: Writing the docs

[ developer.plone.org demo ]

Friday, April 5, 13

Page 16: Writing the docs

Write code

Write tests

Write docs

Write code ~ write docs

Write tests

Fix your workflow

Friday, April 5, 13

Page 17: Writing the docs

Low-hanging fruits

For every blog post you write link it

For every stackoverflow.com question you make link it

For every IRC answer you receive write it down

d.p.org

Informat

ion must

exist ou

tside

your hea

d

Friday, April 5, 13

Page 18: Writing the docs

[ Github inline edit demo ]

Friday, April 5, 13

Page 19: Writing the docs

Share your slides

slideshare.net

Link in developer.plone.org

Friday, April 5, 13

Page 20: Writing the docs

Top-of-the-shelf bottles

Theming tutorial

Development friendliness out of the box

Making Plone itself more dev friendly

Friday, April 5, 13

Page 21: Writing the docs

Kiitos

opensourcehacker.com

Open Source Hacker

103323677227728078543

moo9000

Friday, April 5, 13