talk on Plone documentation, Plone Open Garden 2014. Sorry for no/bad layout, it was using hovercraft (prezi-style) before and this is printed via mozilla...

1. Documentation:
the new deal

2. Current
developer.plone.org
organic collection of different docs
plone.org/documentation
a potpourri of all kind of docs
mostly out of date

3. There's more!
plone user manual
good, but not many people know it
add-ons
some have nice docs, eg. PFG
others are well, crap

4. It is time for a change
So we started to prepare
and drink coco-loco !

7. Make it happen

8. Stroopwafel Sprint

9. Cake-driven documentation
identified gaps in the documentation
a plan for versioning.
plan: consolidate all documentation
the mindmap to rule all mindmaps

10. Cake is good
infrastructure for multilingual
select a correct license
disabled knowledge base on plone.org

12. Cathedral Sprint
time to take the gloves off
get on people's nerves
(aka, tell developers to write docs)

14. DocSprint Munich
Thanks again Max and Alexander !

16. testing docs on humans (animal testing is bad, mmmkay)
asking professional writers for help, thanks again @LMU
create structure
copy docs to the right place in the new setup.

17. fix broken links
start pulling external docs
(git sparse is cool...)
new docs theme
PDF creation via LaTeX

18. Fixed around 368 warning and bugs
discussed writing guidelines
cleaning up tickets from the current
developer.documentation

20. Beer and Wine Sprint

22. more fixing of links, typos and so on
start add missing parts ('new collections')
writing guidelines for add-on writers

23. First important
change

24. License
moving docs from collective to plone
change license from gpl to creative
commons
CC 4.0 BY. kthxbye!
people have to sign contributor
agreement

25. docs.plone.org
basic features
one landing page for all docs
including end users, site admins,
deployers, developers, core devs

26. fancy stuff
different plone versions
different languages
transifex integration
screen shot integration

27. collecting more
docs
include docs for add-ons
working pdf creation
at the moment, we have around
2000 pages of a4 pdf

28. How it works
two repositories

29. repository one
[documentation]
just the plain rst files
a branch for every version
per language directories

30. repository
two [papyrus]
Is where the magic
happens
transifex
pull in external docs
robot screenshots

31. Quality
insurance
No direct commits to
master or branches
we only do pull
requests with reviews
if someone commits
without a pull request
we will revert!!
LaTeX is a harsh critic...

32. Guidelines
for writing
add-on
documentation
NO MORE PEP8
syntactic linebreaks;
think of the
translators
documentation is
not "look at the
code"
yes, we've tested on
real devs

33. Helper
tools
mr gutenberg
sublime text
search
firefox search
add-on
working on a
better online
editor

34. Future
plans
hook docs into
jenkins
test
PDF/Epub/HTML
generation
want PLIPs?
Write docs!

35. More
plans
have more
themes,
fitting with
the version
have
site-specific
docs, with
screenshots
to match
robotize all
the things

36. Go
forth
and document