Markdown was created by John Gruber in 2004 as a simple, readable text-to-HTML conversion syntax. Its design philosophy is that the source text should be readable as-is, without rendering -- a Markdown document with # Heading and **bold** text is understandable even in a plain text editor. This contrasts with HTML, where

Heading

GitHub-Flavored Markdown (GFM) extends the original Markdown specification with features requested by developers: fenced code blocks (`language), tables (| Column | Column |), task lists (- [x] done), strikethrough (~~text~~), and auto-linking URLs. GFM is the most widely used Markdown variant, supported by GitHub, GitLab, Bitbucket, Discord, Reddit, and many other platforms. Our editor renders GFM using the marked.js library, which is a fast, spec-compliant Markdown parser.

Writing in Markdown has several advantages over WYSIWYG editors (like Microsoft Word or Google Docs): the files are plain text (future-proof, version-control friendly, searchable), the formatting is semantic (you describe what things are, not how they look), and the source is portable (works in any text editor). The separation of content and presentation means the same Markdown file can be rendered as HTML, PDF, EPUB, or slides with different styling.

Use cabeçalhos estilo ATX (# para H1, ## para H2) com um espaço após a cerquilha. Cabeçalhos estilo Setext (sublinhados com = ou -) são suportados mas menos comuns. Sempre adicione uma linha em branco antes e depois dos cabeçalhos para legibilidade.erlining with === or ---) is deprecated in GFM. Leave a blank line before and after headings, lists, and code blocks -- many parsers require this for correct rendering. For emphasis, use **bold** and *italic* (asterisks) consistently. Avoid using _ for emphasis as it can conflict with variable names in technical documentation.

Para blocos de código, sempre especifique a linguagem para destaque de sintaxe: use três crases seguidas by the language name (javascript, python, bash). For inline code, use single backticks around the word. For links, use [text](url) format. For images, use . For tables, use the pipe syntax with a separator row: | Header | Header | / | --- | --- | / | Cell | Cell |. Tables must have a header row and a separator row -- cells in the body can be left empty but the structure must be maintained.