Skip to content
wojciech.io
All insights
Operator Playbooks internal reference

MDX components showcase

Living reference for rich MDX components available in insights articles.

Wojciech Łuszczyński

Wojciech Łuszczyński

GTM Architect & Growth Operator · Now · 19 May 2026

TL;DR · Key insights

  • Stat and StatRow give numbers their own weight
  • DoDont replaces wishy-washy advice with two columns of opinion
  • Steps, PullQuote, TechStack and TOC cover the second MDX component batch
  • Drop-in site UI components work in MDX now

The TL;DR above is auto-rendered from frontmatter. Below: every rich component, in one place.

Stat + StatRow

Use for proof-led storytelling. Tabular nums, big lime numbers.

47%

Pipeline lift

Quarter over quarter

3 wks

From idea to shipped

€0

Tooling cost

Cloudflare + Astro stack

DoDont

Sadowski-style. No hedging.

Do
  • Hire an operator who already shipped this
  • Wire CRM, SEO and paid into one system
  • Measure pipeline, not impressions
Don't
  • Hire an agency to 'do growth'
  • Buy six tools that don't talk to each other
  • Optimize for vanity metrics

Steps

Use for process sections where the order matters more than paragraph rhythm.

Migration loop

  1. 01 / scope Freeze the source of truth

    Decide which repo and route own the canonical page before touching copy.

  2. 02 / build Move one layer at a time

    Routes, content, components and deploy rules should each have a clear verification point.

  3. 03 / verify Ship with a rollback path

    The migration is done only when production, redirects and analytics agree.

PullQuote

A site rebuild is not a design exercise. It is a decision about who owns the system after launch.

wojciech.io migration note operator principle

TechStack

Publishing stack

The article layer is deliberately boring: files, components, build output, deploy checks.

Content

Astro routes MDX articles Content collections schema

Delivery

Cloudflare Pages static deploy GitHub source Sentry runtime signal

Callout (existing)

Drop-in site components

Now usable in MDX. Inline <Badge>AI-native</Badge> works in text flow.

See the work

Reference

Use anywhere

Can I use Badge inline?

Yes: wrap any text with <Badge>label</Badge>.

Do these respect dark mode?

All use design tokens, so themes follow automatically.

Next step

Want this stack?

The whole site runs on Astro + Cloudflare Pages + MDX. Open source-ish.

Diagrams: Box + Arrow + Stack

Declarative primitives. No Mermaid, no SVG editor: just nested components.

Linear flow (most common):

Browser
HTTPS
CF edge cache hit
miss
Origin
Request flow through Cloudflare edge

Branching (fan-out via Stack):

Request
Worker middleware
KV sessions
D1 users
Email OTP
Auth gate → multiple downstream services

Layered architecture (vertical):

Layer 4: Action CRM sync, sequences
Layer 3: Decision scoring, routing
Layer 2: Enrichment firmographic, signal
Layer 1: Source forms, intent, ICP list
Four-layer GTM AI architecture

Interactive components

Tabs

Accordion

What is MCP?

How does the agent stack work?

What does it cost to run?

CodeBlock

toml
Cloudflare Pages project configuration

NumberTicker

0% Pipeline growth

EmbedDeck

Audit current state: pipeline, CRM, attribution, stack. Find where signal breaks.

Design the system: what connects, what measures, what automates, what ships first.

Sequences, dashboards, CRM model, tools. Build it or work with the team.

When the right tool does not exist, build it: agents, apps, workflows, clean automation.

About the author

Wojciech Łuszczyński

Wojciech Łuszczyński

GTM Architect and Growth Operator building AI-native revenue systems for B2B SaaS and technology companies. I connect positioning, SEO, content, paid acquisition, CRM, automation, analytics and AI workflows into practical growth infrastructure.

Newsletter

Get the next one first.

When I publish a new article on AI systems, GTM architecture, or growth operating models, you'll be the first to know.

Subscribe