The separation between a knowledge base and a MOOC makes sense to me: We need one place where to drop our knowledge, and updating that as we learn more has to be comfortable and cheap. And then we can have various presentations items with parts of that knowledge, in more polished form, where the accepted trade-off is that it’s harder and more expensive to create and update this kind of content.
Part 1 is my thing (technical writing, I kinda love it …). Part 2 is not, not at all. My mind needs good structure but very little beautification to enjoy information … and adding additional beauty to it to me feels just … meaningless. Please keep that in mind when developing a concept note 
For the technical writing part I’d like to see some resources allocated to improve our tooling:
-
An extension to Discourse that creates a numbered table of contents in the output when just placing a BBCode-like tag such as
[toc]into the editor. -
A pipeline that can take a Discourse URL of one of our manuals (example), collect and embed linked content from the other manuals, and convert it all from Markdown to a proper, well-formatted e-book in standard EPUB and PDF forms, with table of contents and all.
I’d use the same tool for the green building conversion manual that is due to be created for The Reef 2.0 project, and may use some of the budget assigned to that task to contribute to development of this tool.