241–250 of 272 posts
[1] https://github.com/Zettlr/Zettlr
[2] https://docs.zettlr.com/en/reference/markdown-basics/#zettlr...
Also on Azure DevOps too https://docs.microsoft.com/en-us/azure/devops/project/wiki/w...
What a time to be alive! :-)
Very happy that 1.5 years later they are again being rendered.
This is pretty cool, something that I'd actually use if there was a simple SaaS option for it.
This is pretty cool, something that I'd actually use if there was a simple SaaS option for it.
Earlier quoted context omitted.
> readable-as-text goals of markdown. Markdown was meant to be rendered, not left as plaintext (for viewing, at least as a primary use-case). It's name is a punny joke, but it's a lightweight mark up language that was meant to be a lightweight way to write formatted text that would be rendered as formatted HTML. GFM seems in keeping with this for the most part.
> Markdown was meant to be rendered, not left as plaintext Now it’s not. Markdown was intend to be legible in plain text but visually emulate rendered text. The rendering stuff came later but even then it still had an emphasis on plain text readability. There is a reason it was chosen for README, INSTALL etc documents in project repositories that are (or, at least until relatively recently in computing history, were…
> The rendering stuff came later
Here is the original announcement I was able to track down:
http://www.aaronsw.com/weblog/001189
> For months I’ve been working with John Gruber on a new project. The idea was to make writing simple web pages, and especially weblog entries, as easy as writing an email, by allowing you to use much the same syntax and converting it automatically into HTML.
Seems that HTML rendering was there from day 1.
Cooool, this is used on github https://github.blog/2022-02-14-include-diagrams-markdown-fil... Also on Azure DevOps too https://docs.microsoft.com/en-us/azure/devops/project/wiki/w... What a time to be alive! :-)
https://about.gitlab.com/releases/2017/12/22/gitlab-10-3-rel...