<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Session 16: Markdown: Write notes that look like the web :: CoderDojo Python &amp; Pygame</title><link>https://python.coderdojohasselt.be/en/sessions/git/16-markdown/index.html</link><description>You might know HTML from the internet: &lt;h1>, &lt;p>, &lt;a>. But for notes and documentation HTML is far too much typing. That’s what Markdown is for.
Markdown is a mini-language you write in plain text. It looks readable without having to convert it first. And with one push of a button it becomes neat HTML: headings, lists, links, tables.
In this session you learn the whole basis of Markdown. At the end you write notes that look professional, on GitHub, in Obsidian, or in any other program that understands Markdown.</description><generator>Hugo</generator><language>en</language><atom:link href="https://python.coderdojohasselt.be/en/sessions/git/16-markdown/index.xml" rel="self" type="application/rss+xml"/><item><title>Session 16: Coach notes</title><link>https://python.coderdojohasselt.be/en/sessions/git/16-markdown/mentor-notes/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://python.coderdojohasselt.be/en/sessions/git/16-markdown/mentor-notes/index.html</guid><description>Goal of this session At the end of this session a ninja can:
Create a .md file and open it in an editor. Write headings, paragraphs, bold, italic and strikethrough text. Make numbered and unnumbered lists (including nested lists). Make external links and internal links. Build a table with columns and alignment. Use code blocks with syntax highlighting. Write a complete README.md that combines headings, lists, links and code. Preparation (30 min before the session) Editor with Markdown preview ready. VS Code is ideal (built-in preview with Ctrl+Shift+V). Obsidian works too. If nothing is available: use an online editor such as dillinger.io or stackedit.io. Make sure the preview is visible on the projector. Demo file ready. Make a demo.md with examples of every Markdown feature (heading, list, link, table, code block). Use it to show live what Markdown looks like as plain text and as preview. Thonny as fallback. If ninjas have nothing else: Thonny opens .md files as plain text. They can learn the syntax without a preview; the preview is nice but not essential. Schedule (3 hours) Time Activity 0:00 to 0:10 What is Markdown? Where do you come across it? (GitHub, notes, this site) 0:10 to 0:30 Projector: demo (showing every feature live and showing the preview) 0:30 to 1:00 Working on your own: headings, formatting, lists 1:00 to 1:15 Break 1:15 to 1:45 Projector: links, images, tables, code blocks 1:45 to 2:30 Working on your own: writing a complete README 2:30 to 2:45 Showcase: show your README (plain text + preview) 2:45 to 3:00 Wrap-up, take-home Common questions “Do I have to learn Markdown by heart?” No. Most editors have buttons for formatting (like Word). But knowing the syntax is handy: you type faster, and on platforms like GitHub you only have the plain text.</description></item></channel></rss>