Dillinger VS GitHub Gist

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

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