🤔 Curious about your way of using mk-notes !

[Myastr0]

I’m really curious to discover the different ways you’re using mk-notes 👀

Whether it’s for personal note-taking, team documentation, blogging, or something totally unexpected — every story helps me understand how mk-notes fits into real usage and how I can improve it ☝️

Feel free to drop your experience in the comments below 👇

If you’re not sure where to start, here’s a quick template you can follow :

## 👀 Curious minds want to know…
How did you first start using mk-notes?  
What problem were you trying to solve?

---

## 🛠️ Your setup
- Do you use it for personal notes, team docs, blogging, or something else?  
- Are you running it locally, in CI/CD, or somewhere automated?  
- Any cool tricks or shortcuts you’ve added?

---

## 💖 Favorite thing so far
What’s the best part of mk-notes for you?  
(Examples: staying in Markdown, Git integration, keeping Notion in sync, simplicity…)

---

## 🌱 What could grow
Is there something missing or that could be improved to make your way of using mk-notes even smoother?  

---

## 🎁 Extra credit
Got screenshots, repo links, or stories you’d like to share? Drop them here!

Thanks a lot in advance for sharing your thoughts —
And if you haven’t already, don’t hesitate to ⭐ the repo to support the project! 🙏

You can also join the community on the Discord server

[mmiranda]

My scenario is quite simple: I keep all the technical documentation of my platform in GitHub as a source of truth, but I still need to keep the same content in Notion for those who do not have a GitHub account, like C-Level, auditors, etc.

We run it via GitHub action whenever there's any change in our docs folder.

We've moved from Confluence to Notion early this year (we used to use lib kovetskiy/mark to sync there), but then got orphaned of the same lib for Notion until I found yours. Other libs seem to be a bit outdated and barely maintained.

[oliverkaiser]

We try to use it within a team of product and tech people, working on a shared github repository with various documents that we maintain like PRDs, tech designs etc. But we want to keep them in sync into our notion database.

The other part of the challenge will be syncing back changes from notion into github/markdown :)

[JFuhrerSR]

Similar to others above, I was looking for a nice way to build internal development documentation and leverage our org's already existing Notion plan. Found Mk Notes today and it seems like a great solution so far. I think the documentation of this project could be expanded to make the full capabilities more clear, such as the architecture/organization of a project and what the full formatting capabilities are. Other than that, working great thus far. Love being able to simply work with Markdown and keep versioning of the documentation in git.