Markdown
A simple way to format text using symbols like # for headings and * for bold. What most blog posts are written in.
Markdown is a plain-text formatting language created by John Gruber in 2004 that lets you write formatted content using simple symbols: # for headings, ** for bold, - for bullet points, and so on. The text you write gets automatically converted into properly structured HTML, which is what browsers actually render. It’s become the standard for writing documentation, blog posts, and content across platforms like GitHub, Notion, and most modern website builders.
The Simple Version
Markdown is a shorthand for formatting text. Instead of clicking a “Bold” button like in Word, you wrap a word in asterisks: **bold** becomes bold. A # at the start of a line makes it a heading. A - makes a bullet point.
It’s like texting, but with a few extra symbols that turn plain text into nicely formatted documents.
Why It Matters
Markdown is everywhere in the tech world. GitHub uses it. Notion uses it. Slack uses a version of it. Most blogs (including this one) are written in Markdown. Once you learn a handful of symbols, you can format text anywhere without touching a toolbar.
It’s also future-proof. Markdown files are just plain text. They’ll open on any computer, in any app, forever. No “.docx compatibility issues” to worry about.
How It’s Used on This Site
Every blog post and glossary entry on this site is written in Markdown. The files sit in a folder, each one containing the text content plus a small header with metadata (title, date, tags). Astro reads those files and turns them into the styled pages you see now.
Related Articles
How I fixed a broken visual identity using ChatGPT for logo design and brand tokens, then handed a structured markdown file to Claude Code to execute the CSS migration and replace a static hero with an AI-generated animation.
How a 30-minute voice conversation with an AI turned zero knowledge of TikTok commerce into a full operating plan: business model, setup sequence, ad strategy, and key metrics.
How a glossary of technical terms for non-technical readers grew out of the same AI workflow that builds the site itself. Content collections, structured data, and Claude Code doing the heavy lifting.
How two plain-text files turned an AI coding assistant into a persistent, self-improving build system. The architecture behind scottkrukowski.com, explained for non-engineers.
A non-developer's walkthrough of building a professional website using Claude Code, Astro, and AI-assisted development. From rapid scaffold to production deployment.
Browse the Full Dictionary