It supports the use of custom Markdown parsers. Marked 2 - Document viewer (Mac only): A first-rate Markdown renderer.Jekyll - Local blog preview: Since I publish with GHP (which uses Jekyll), I preview locally with Jekyll.GitHub Pages - Blog publishing: I moved to GHP after my dynamic web site was compromised, and I decided I wanted simple, secure blog hosting.Github Flavored Markdown: Rationalle explained above.Either ignore it, or give me some way to view/edit it. Tables (with some kind of table editor - not just source editing of pipes and spaces).For documents with lots of embedded images or documents where I need precise page layout, I don’t use Markdown. I mostly want WYSIWYG editing – a simple WordPad-like (or TextEdit-like) experience for rich text documents. Consequently, I’m less interested in side-by-side (source + rendered) tools than many Markdown fans. Other than my blogs, I am the chief consumer of my Markdown documents. So the question of which Markdown flavor to use is either:įor now, unless I encounter a compelling reason to use native kramdown, I’m using GFM because it is the default on GHP and on GitHub issues. Per GitHub: “GitHub Pages only supports kramdown as a Markdown processor” and “we’ve enabled kramdown’s GitHub-flavored Markdown support by default.” ![]() I’m using Jekyll and GitHub pages (GHP) for my blogs. I’d like to try and make sense of what I’m using and why. I’ve been using a hodgepodge of Markdown tools. ![]() Summary: GitHub Flavored Markdown, kramdown, Marked 2, Typora
0 Comments
Leave a Reply. |