Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Congrats on this - It looks really good. We’ve been evaluating documentation tooling for our company. We’re in a weird regulatory environment where the documentation is created by someone else, but reviewed and approved by another person.

I bring this up because a feature that could set you apart from others is the concept of a “merge request” for documentation. Where someone can make a document, another can modify it and submit changes for review.

GitBook has this but it lacks in some other key ways for us.



I’ve also always wanted this, but what I’ve realized after noodling on it a while is I’d really just prefer a way to use git, and push markdown documents to the Notes System.

I dont want a different system handling edits reviews and merges.

I just want CD to send my docs from git to a system that can properly host / give me the Doc-related features I need.


If this could co-exist in the backend with an easy to use browser interface for the many who write text more than markdown, would be amazing.

Being markdown centric would be great. Makes this tool a great destination for so much markdown content already existing.


> I just want CD to send my docs from git to a system that can properly host / give me the Doc-related features I need.

Material for Mkdocs does exactly this.

https://squidfunk.github.io/mkdocs-material/


This would be a great feature. We have a similar problem whereby there are official versions of documents which have been through a review process and the only way to work on the next version on Confluence is to have a separate working copy of the page which pollutes the search and gets messy very quickly.


Confluence 100% supports the situation you’ve described. The way I’m reading this is that you need to have a publishing workflow, or a document approval workflow, which Confluence can do. At one of my jobs, we wrote it with CQL.


Curious what other features you need where merge requests for documentation is the primary requirement but Git (or some other VCS) isn't sufficient?


How would you manage a Confluence document via git?


a repository of markdown files with a custom viewing software that supports the syntax and renders it for readability or acts as a wysiwyg editor would work well: I do this personally, with Obsidian.md, where my vault directory is a git repository. a hosted web interface should be able to do something similar.


This would indeed be nice to have.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: