Use case
RankFlo for Developer Relations
Tutorials, changelogs, API docs, conference talk write-ups — all in one platform with great code blocks, syntax highlighting, and developer-friendly URLs.
Pain points DevRels face
- ✕Tutorials need beautiful code blocks (Mintlify-quality) — most CMSes are weak here
- ✕API reference, conceptual guides, and blog posts each need different layouts
- ✕Hard to keep code samples in sync with shipped product
- ✕Developers don't sign up via web forms — need different conversion patterns
How RankFlo helps
Syntax-highlighted code blocks
Shiki / Prism rendering with copy buttons, line numbers, line highlighting, language tabs.
Multi-project for content types
Separate projects for blog, docs, changelog. One organization, unified team.
MDX-style components in Tiptap
Embed live demos, callouts, tabs, accordions, GitHub Gist links.
Developer-friendly URLs
/blog/tutorial-name (no dates, no IDs, no /p/abc123). Clean, memorable, SEO-friendly.
API docs hosting
Use the same platform for /docs/api-reference style content. JSON-LD APIDocumentation schema.
A typical workflow
- 1Write tutorials with syntax-highlighted code blocks
- 2Publish changelog as a tagged content type
- 3Use webhooks to auto-publish from internal docs repo
- 4Track which tutorials drive signups via custom events
- 5Repurpose conference talks as blog write-ups
Metrics that matter
- Tutorials shipped per month
- Time-to-first-value for new developers
- GitHub stars driven by content
- Trial signups from tutorials
- Top tutorials by signup conversion
Built for devrels like you
Free plan forever. 14-day Pro trial. Self-host for free.