Thanks for the feedback w3clan. I like the approach you're going with tutorials although I struggle with the usability. This is an issue that plagues the develo

Thanks for the feedback w3clan. I like the approach you're going with tutorials although I struggle with the usability. This is an issue that plagues the developer community and something we faced building PressGang CCMS at Red Hat prior. We took over 2/3 of Red Hat's global software documentation with our internal "just for us" tool in the first year of prototyping it. But ultimately we needed to learn a lot about the increasing focus on UX. Plus we learned that, surprise to nobody but us, writers just want to write. You can see this trend with Dropbox acquiring Hackpad. Collaboration with attention to design workflow is very important. The ability for teams to create content easily is of utmost importance. As LEw Platt famously said: > "If only HP knew what HP knows, we would be three times more productive." Corilla's "Collections" module is like nothing else, and that's the real power of the product. Once you try it, there's no going back to "notes" or "documents"... and why would you? The ability to create content, and then grab it as a dynamic group as and if needed - plus push it to a private or publish HTML build in literally seconds? You can see why we've grown so fast. Looping back around - I would caution investing too much time in tutorials without attention to UX and the design experience for the reader. Our buddy Eric over at Read The Docs is the default host for open source docs, where design matters less, and services like Udemy have raised the bar on LMS and tutorial experiences. Those to me are both extremes, and there's more LMS swarming every day. IMHO the focus is on overall experience of managing information as a team, and I'd encourage others to join us in tackling this. That is, after all, where both the greatest problems and greatest budget are being directed.