This is a placeholder Post seeded by hand so the Blog list has something to
show, and — until the Notion Publish workflow lands — a proving ground for
every Markdown element the renderer must style. It exercises bold,
italic, struck-through text, inline code, and
a link in a single paragraph.
Heading one
Heading two
Heading three
Heading four
Heading five
Heading six
Lists
Unordered, with a nested level:
- Discovery call and account mapping
- Onboarding
- Kickoff and success plan
- Data import and first value
- Adoption and expansion
Ordered:
- Land the account
- Onboard the team
- Prove value early
- Renew and expand
A quote
Retention is not a metric you chase at renewal; it is the sum of every small promise you keep along the way.
Numbers worth tracking
Numeric cells render in Space Mono per the design system; text stays in Outfit. On a narrow screen this table scrolls inside its own container.
| Metric | Q1 | Q2 | Change |
|---|---|---|---|
| Net revenue retention | 108% | 114% | +6% |
| Logo churn | 2.1% | 1.4% | -0.7% |
| Accounts onboarded | 42 | 57 | +15 |
Code
Inline references like resolvePost(slug) read as machine output. Longer
samples get their own scrolling block:
export function healthScore(usage: number, sentiment: number): number {
// Long line kept deliberately wide to prove the block scrolls, not the page — aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
return Math.round(0.6 * usage + 0.4 * sentiment);
}
A mermaid fence renders through the stub branch as a labelled code block —
the diagram source, styled but not drawn:
graph TD;
Lead-->Onboarding;
Onboarding-->Adoption;
Adoption-->Renewal;
An image
Images lazy-load inside a card-like frame:
That covers every element the Post body knows how to style.