Markdown Style Guide

A kitchen sink of all prose elements to verify typography and styling.

Heading 2 — Section Title

This is a standard paragraph. Body text should be comfortable to read at length, with good line-height and a muted color that provides contrast without harshness. Here's some bold text and some italic text and a link to somewhere.

Heading 3 — Subsection Title

Subsection headings should be clearly smaller than H2s but still stand out from body text. They create hierarchy within a section.

Blockquotes

Used for challenge statements, callouts, and highlighted quotes:

How might we help new users understand and leverage complex capabilities without compromising power and flexibility?

Lists

Unordered List

  • Making the data model intuitively browsable through clear categories
  • Providing structured ways to build queries that taught the language
  • Creating a natural progression from guided to advanced usage

Ordered List

  1. A pre-sales discovery experience
  2. An enhanced setup process with our sales team
  3. A post-onboarding feedback loop

List with Bold Labels

  • Who: Product team pod (designer, product manager, tech lead, 3-4 engineers)
  • How Long: ~3 months (initial discovery to production)
  • What Tools: Figma for UI design. Code-based prototyping.

Images

Images should have rounded corners, a subtle border, and vertical spacing:

Example project thumbnail

Inline Code and Code Blocks

Use inline code for referencing variables, filenames like CLAUDE.md, or short technical terms.

// Code block example
const theme = localStorage.getItem("theme");
if (theme === "dark") {
  document.documentElement.classList.add("dark");
}

Horizontal Rules

Used to separate major sections:

Content continues after the rule.

Bold and Emphasis Combinations

  • Detection Templates: Pre-configured detections identified common bot patterns like web scrapers, vulnerability scanners, and aggressive crawlers.
  • Automated Response System: Flexible rules & alerts engine enabled teams to block suspicious traffic, rate limit aggressive bots, and trigger incident response workflows.
  • Monitoring Dashboards: Ready-to-use views helped teams track bot activity patterns and measure mitigation effectiveness over time.

Links

Links should use the accent color with an underline offset: Presentation Slides, Prototype, UI Screens, and Design System.

Nested Content

A paragraph before the blockquote.

Impact: Unified product teams around a shared vision driven by customer insights

A paragraph after the blockquote, continuing the narrative with additional context and detail about what happened next.