Parimal Mahindrakar
Posted on Edited on
I spent months building a markdown notes app and finally shipped it !
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (6)
The published-folder feature is the compelling part for me: notes become a navigable docs site without a separate publishing workflow. I would test the boundary between private and public hard, especially a wikilink from a published note into an unpublished note and backlinks/search indexes after unpublishing a folder. A reader should never learn a private note title from navigation or metadata.
Hey, thanks for the close look!
Checked everything you mentioned, the privacy boundaries are solid. Private notes stay private even if they're sitting next to public ones, and unpublishing works instantly with no leftovers.
The folder thing is actually by design, when you publish a folder, everything inside it goes public. Think of it like publishing a book: all the chapters come with it. If you want one chapter private, you take it out of the book first.
That book model makes sense. The one UX guard I'd consider is a preview before publishing a folder that lists exactly which note titles and child folders will become public, including any newly added since the last publish. It makes the all-or-nothing rule clear at the moment it matters, rather than relying on someone remembering it later. Good to hear unpublishing removes the public trail too.
That's a really good idea, a confirmation step showing exactly what's going public before the folder gets published. Will add it to the roadmap. Thank you!
If you get some time, feel free to signup and let me know if I am missing anything again !
Glad that helps. A clear list of what will go public should make the folder feature easier to trust. Thanks for taking the feedback seriously; I'll keep an eye on the project.
Cool !