Markdown syntax and rendering
Markdown converts plain-text markup, asterisks, hashes, brackets, into HTML, but the "Markdown" most tools actually process is a variant, GFM (GitHub Flavored Markdown), which adds tables, task lists and autolinks on top of John Gruber original 2004 spec.
Reading time uses the practical convention of 200 words per minute, rounded up with a 1-minute floor, even for a text just a few lines long.
The `| --- | --- |` row defines column alignment and never appears in the rendered table; tables are a GFM extension, Gruber original Markdown has no table syntax at all.
The `onerror` attribute is stripped by the sanitizer because it triggers a script in the browser; the `<img>` tag itself survives, only the dangerous attribute is cut.
Yes. You write Markdown in the editor and see the rendered, sanitized HTML update in real time beside it. You can copy the Markdown, copy the generated HTML or download a complete .html file, and also track statistics such as heading, link and image counts and reading time.
Because the Markdown spec treats a lone line break as whitespace inside the same paragraph; to force a visual break, leave a blank line between the pieces or end the line with 2 trailing spaces.
GFM is GitHub Flavored Markdown, the variant that adds tables, strikethrough, task lists and URL autolinking on top of John Gruber original Markdown (2004); most modern viewers process GFM, not the original bare spec.
Because a safe viewer sanitizes the resulting HTML before rendering it, stripping tags and attributes capable of running a script (like `<script>` or `onclick`); it is XSS protection, not a syntax bug.
Because everything between the opening and closing sets of 3 backticks is treated as literal text, and it never runs through the Markdown syntax interpreter; that is how a code block shows `**bold**` as plain text instead of rendering it bold.
A clean Markdown preview for J-Kit.
const safe = true;
Markdown and rendered HTML stay in your browser. The preview is sanitized with DOMPurify.