Your Post Title Here
A one or two sentence summary of what this post is about. Shown in the blog listing.
Opening paragraph. This is the first thing readers see after the title. Keep it short — one to three sentences that set up the rest of the post.
Heading 2
Body copy under a second-level heading. Use ## headings to break the post into sections. The page title uses an <h1>, so start your section headings at ##.
Heading 3
Sub-sections can use ###. Don’t go deeper than that unless you genuinely need it.
Text formatting
Bold text is for emphasis. Italic text is for titles, terms, or light emphasis. Inline code is for anything that should be read literally — variable names, file paths, shell commands.
Strikethrough is available if you need it.
Blockquote. Good for callouts, notable quotes, or important warnings. Use sparingly.
Lists
Unordered list:
- First item
- Second item
- Nested item (indent with two spaces)
- Another nested item
- Third item
Ordered list:
- Step one
- Step two
- Step three
Code blocks
Inline: run npm install to get started.
Fenced code block with language hint for syntax highlighting:
function greet(name: string): string {
return `Hello, ${name}!`
}
console.log(greet('world'))
# Shell commands
cd my-project
npm run dev
{
"name": "example",
"version": "1.0.0"
}
Links and images
Link text — external links open in a new tab when the prose styles add target="_blank".
Reference-style links are also valid: [link text][ref], then define [ref]: https://example.com at the bottom of the file.
Images work the same as links with a leading !:
Tables
| Column A | Column B | Column C |
|---|---|---|
| Row 1 | data | data |
| Row 2 | data | data |
| Row 3 | data | data |
Horizontal rule
Three dashes on their own line produce a <hr> (you’ve seen several already in this file).
That’s the basic toolkit. Delete everything between the comment block at the top and here, then write your post.