HedgeDoc VS Dillinger

Nice and simple. I feel the only lacking feature for a basic blog is having unlisted blog posts, which is very handy when you want to share it to proof-readers. This can be done on google doc/hedgedoc [0] for sure, but then when porting there are very often typos creeping in. [0] https://hedgedoc.org/. - Source: Hacker News / 8 months ago

Maybe Hedgedoc will fit these needs? You can use markdown to format. https://hedgedoc.org/. Source: 11 months ago

If self-hosting is an option for you I would recommend that you go with HedgeDoc. Completely open source, you get all the features you asked for including real time collaboration. Source: 11 months ago

You can give HedgeDoc (https://hedgedoc.org/) a try as a replacement for Google Docs. It is the one that works best for concurrent editing IMO (but it is markdown which can be a problem for some). - Source: Hacker News / about 1 year ago

I use one singular HedgeDoc document for that purpose. It's not exactly the same intent as Google Keep, but it's an awesome project I use anyway and fills the role perfectly for me personally. Source: about 1 year ago

I have used Markdown before (https://dillinger.io/) so wouldn't have a problem with using it again as long as on page SEO isn't any extra effort. I am not sure how I would use Markdown and then add the content to the blog to be deployed and if that is going to be much harder than a headless CMS, I would go for the headless. Source: 6 months ago

Useful rescources for this are: Markdown Cheatsheet and Markdown Editor. - Source: dev.to / 11 months ago

-put chatgpt output into dillinger.io and save as markdown file. Source: 12 months ago

Did you try pasting the response in a Markdown editor and check if it's working? Here's one online - https://dillinger.io/. Source: about 1 year ago

Which works at https://dillinger.io/, but not https://insiders.vscode.dev. Source: about 1 year ago