This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Notula
Read, edit and comment on the Markdown in your git repo
Your team's documentation lives as Markdown files in GitHub, GitLab or any git repo, and there is still no good way to work with it. Notula opens those files like Google Docs: a tree of documents, editing with no Markdown syntax on screen, comments on any passage with replies and resolve. Every file stays plain Markdown in your own repo, committed and synced in the background. Free, for macOS and Windows.
Your documentation moved into the repo. The tools to work with it did not.
If your team keeps docs as .md files in GitHub, GitLab or a self-hosted repo, everyone who is not comfortable in a code editor is locked out. They read raw Markdown on a web page, or you export to Google Docs and nobody merges it back. The editors that exist are built for one person and a local folder - the repo, the review and the other people are somebody else's problem.
Notula points at a repository and shows the Markdown, nothing else: a tree of documents, no source files, however big the repo is. The editor hides the syntax completely, including on the line the cursor is on. Comments anchor to a quoted passage, with replies and resolve, and live in an append-only log, so two people commenting at once cannot produce a merge conflict.
Git happens in the background. It commits and syncs, and every command carries an explicit pathspec, so only doc files move. It never stages your worktree, never stashes, never rewrites history, never creates or switches a branch. It speaks git and nothing else, so it works with GitHub, GitLab, Bitbucket, self-hosted, or no remote at all.
The file on disk stays ordinary Markdown. Opening and saving it without editing produces a byte-identical file - that is a test, not a promise.
Three things up front. It is free, always: no account and no server. It is closed source; your files, your git and your remote stay yours, and the app keeps nothing of its own. And the builds are not signed: on macOS, Gatekeeper says the app is damaged, and the download page gives you the one Terminal command that clears it; on Windows, SmartScreen hides Run anyway behind More info.
I am here all day - tell me where it breaks.
About Notula on Product Hunt
“Read, edit and comment on the Markdown in your git repo”
Notula was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #148 on the daily leaderboard. Your team's documentation lives as Markdown files in GitHub, GitLab or any git repo, and there is still no good way to work with it. Notula opens those files like Google Docs: a tree of documents, editing with no Markdown syntax on screen, comments on any passage with replies and resolve. Every file stays plain Markdown in your own repo, committed and synced in the background. Free, for macOS and Windows.
On the analytics side, Notula competes within Productivity, Writing and Developer Tools — topics that collectively have 1.2M followers on Product Hunt. The dashboard above tracks how Notula performed against the three products that launched closest to it on the same day.
Who hunted Notula?
Notula was hunted by Aleksandr Netrebskii. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Notula including community comment highlights and product details, visit the product overview.
Aleksandr Netrebskii
Your documentation moved into the repo. The tools to work with it did not.
If your team keeps docs as .md files in GitHub, GitLab or a self-hosted repo, everyone who is not comfortable in a code editor is locked out. They read raw Markdown on a web page, or you export to Google Docs and nobody merges it back. The editors that exist are built for one person and a local folder - the repo, the review and the other people are somebody else's problem.
Notula points at a repository and shows the Markdown, nothing else: a tree of documents, no source files, however big the repo is. The editor hides the syntax completely, including on the line the cursor is on. Comments anchor to a quoted passage, with replies and resolve, and live in an append-only log, so two people commenting at once cannot produce a merge conflict.
Git happens in the background. It commits and syncs, and every command carries an explicit pathspec, so only doc files move. It never stages your worktree, never stashes, never rewrites history, never creates or switches a branch. It speaks git and nothing else, so it works with GitHub, GitLab, Bitbucket, self-hosted, or no remote at all.
The file on disk stays ordinary Markdown. Opening and saving it without editing produces a byte-identical file - that is a test, not a promise.
Three things up front. It is free, always: no account and no server. It is closed source; your files, your git and your remote stay yours, and the app keeps nothing of its own. And the builds are not signed: on macOS, Gatekeeper says the app is damaged, and the download page gives you the one Terminal command that clears it; on Windows, SmartScreen hides Run anyway behind More info.
I am here all day - tell me where it breaks.