Corilla is a collaborative authoring and publishing tool for technical writers. Markdown, version control and publishing in one.
Replies
Best
Nice! We are currently documenting in markdown in a github repo. Collections and modules solve a huge pain for us.
The next one is how to handle images (and their source files). Also we're still figuring out a process how to notice when docs get outdated
@masone thanks for checking out Corilla. There's a lot of interesting discussion about how best to address the topic of content lifecycle, particularly in how it ages. In my experience the answer is usually "poorly", and most enterprise teams bike-shed around the issue as maintenance is poorly understood in terms of the economics.
I've tackled this on a few projects. The concept of "what you measure matters" applies here, so even if there's natural or cultural blockers against improving your company docs, you can gain some momentum simply by auditing what's out there. And then running analytics on what content is being consumed. And then bonus points for tracking user journeys, and a special prize if you correlate bounce rates against (the count and cost of) customer support.
Having said that, you can probably guess what our roadmap looks like here π. The long view is in automation of the techniques and skills that people like us develop in our careers. I spoke at a technical writing meetup recently about the machine learning experiments we've been doing to basically put the "M" into "CMS". We can talk off-list if that's interesting to you.
As for images, isn't it frustrating how bad the asset management is in the typical "CMS"? In terms of asset management we've got coverage of that at the moment, but the source file question is another thing entirely. Would love to have a wider conversation about that in the community (as there's the whole filesystem versus repo approach here).
@joshharcus Thanks Josh. It would be great to hear what you think both as a writer and also get some feedback given your experience on the sales and marketing side. As Corilla is just coming out of beta, we're naturally shifting our focus to improve the onboarding experience and reaching out beyond our community. Let me know any time if you would like a demo to run through the workflow and learn more about what you're working on.
A quick thank you to everyone for all your support, questions and feedback. This was our first Product Hunt launch and we're humbled by the experience. And also a little tired, as we've worked hard to keep up with the onboarding and even shipped a few updates based on feedback.
Now @nathan404 and I are packing to fly out of Brisbane, Australia, and head to Portland for Write The Docs, and then down to San Francisco. Drop us a line if you're in the hood (as it seems our hunted @stringstory will be).
And by the way... https://www.bonjoro.com/g/C7YiJq... ππππΌπ―
And here's a quick update: Thanks to Product Hunt feedback, we're building a new version of our documentation portal and knowledge base. And doing it... in the open. https://medium.com/corilla-blog/...
Report
only the landing page is available, App, Blog, Docs, ... not found
Replies
Corilla
A Closing Culture
Corilla
Corilla
Corilla