HedgeDoc VS GitHub Gist

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

If you are learning things, you could also create github gists. That way your repos will only be coding related, while you can create tutorials / work exercises in gists. Source: over 1 year ago

I use Github, both for full repos and for short gists. Source: about 2 years ago

On the other hand, shared DartPads are just gists on GitHub so theoretically they can include code that works with different packages. Of course, such gists will not compile in DartPad and will be displayed as having errors :(. Source: over 2 years ago

Perhaps github gists? https://gist.github.com/discover. Source: over 2 years ago

I looked at Github gists, but they are focused in displaying the markdown sourcecode (so e.g. Hyperlinks won't be clickable [1] ). Options just don't seem to be focused on simply hosting PDFs/information with clickable references. Source: over 2 years ago