Dev Blog Rendering Test

This is a test blog post to verify that the markdown renderer on the website works correctly. The goal is simple: throw different markdown elements at it and see what breaks.

1. Headings

H3 Heading

H4 Heading

H5 Heading

If your heading hierarchy looks weird, your CSS is probably wrong.

2. Text Formatting

• Bold text

• Italic text

• Bold + Italic

• Strikethrough

• Underline (HTML fallback)

Blockquote test:

This is a blockquote.
If this looks ugly, fix your typography.

3. Inline Code

Use console.log("Hello World") for quick debugging.

You can also reference variables like user.id or process.env.NODE_ENV inline.

4. Code Blocks

JavaScript Example

function greet(name) {
  return `Hello, ${name}!`;
}

console.log(greet("Developer"));

Go Example

package main

import "fmt"

func main() {
    fmt.Println("Hello from Go")
}

SQL Example

SELECT id, name, created_at
FROM users
WHERE active = 1
ORDER BY created_at DESC;

5. Lists

Unordered List

• Item One

• Item Two

  • Nested Item A

  • Nested Item B

• Item Three

Ordered List

1. First Step

2. Second Step

3. Third Step

Task List

• Set up project

• Add markdown parser

• Fix layout issues

• Ship to production

6. Tables

7. Horizontal Rule

Below this line:

If you don’t see a divider above, your markdown renderer is broken.

8. Images

Standard Markdown Image

Clickable Image

9. Links

• External Link: GitHub

• Internal Link: /about

10. Code + List Combo

1. Install dependencies:

npm install

2. Run development server:

npm run dev

3. Open http://localhost:3000

11. Details / Summary (Collapsible Section)

Hidden content lives here.

def add(a, b):
    return a + b

12. HTML Inside Markdown

13. Emoji Test

🚀 🔥 💻 🧠

14. Long Paragraph Test

Here’s a longer paragraph to test line height, spacing, readability, and container width. If this feels cramped, your max-width is too wide or your line-height is too small. Good typography matters more than fancy animations. If people can’t read comfortably, nothing else matters.

15. Final Check

If everything above renders correctly:

• Headings scale properly

• Code blocks are highlighted

• Lists indent correctly

• Tables align properly

• Images are responsive

• Blockquotes look intentional

Then your markdown setup is solid.

If not, fix it before adding real content.