DevConf.CZ 2020

So now your project switched to modular documentation to let a downstream product reuse some content. How do you write the documentation now?

This is the story of the creation of an automated downstreaming for Eclipse Che, told to understand what makes a documentation reusable for real.

An efficient downstreaming is, of course, automated. Hopefully, few remains downstream: the downstreaming process itself, and downstream specific topics, like installation instructions or release notes.
Most importantly, the content of the upstream documentation should fit into the modular documentation format. You can translate and reshape most of the outline keeping upstream as it is. Same story for the substitution of group of words, like project name. Only for larger chunks of text, you may need to modify upstream.
Attendees can expect a presentation and discussion of ways to adapt upstream documentation to ease its reuse in downstream products.
Slides: https://themr0c.github.io/2020-01-efficient-downstreaming/