Introduction
Welcome to Verto
Verto is a modern publishing platform that transforms plain Markdown into a premium reading experience. Named from the Latin vertō — meaning "to transform" — Verto bridges the gap between writing simplicity and publication-quality output.
Why Verto?
Most blog engines force a choice: write in a simple format and get a mediocre result, or wrestle with complex tooling for a polished output. Verto rejects that tradeoff entirely.
With Verto, you write in standard Markdown (or MDX) with a few optional extensions, and the engine handles the rest — structured navigation, rich block elements, syntax-highlighted code, inline author commentary, and a magazine-grade reading experience.
Verto fuses three design philosophies into one cohesive platform: Mintlify's structured documentation navigation, Notion's expressive block system, and the OpenAI Blog's typographic elegance.
Key Features
- Rich Block Elements — Callouts, toggles, task lists, bookmark cards, and figures, all authored in clean Markdown or JSX syntax
- Inline Comments — Author asides using
[^c-N]footnote syntax that render as contextual popups without interrupting the reading flow - Syntax Highlighting at Build Time — Code blocks rendered with Shiki at build time, shipping no client-side JavaScript for syntax highlighting
- Dark Mode — System-aware theme switching with CSS custom properties and
localStoragepersistence - Structured Navigation — Sidebar groups and table of contents generated from your content directory structure
Philosophy
Verto is built on three principles:
- Authors write in plain Markdown — no proprietary syntax, no lock-in. Your content is portable to any Markdown renderer.
- Readers get a premium experience — generous whitespace, clear typography, and thoughtful interactions that make content a pleasure to read.
- Developers get zero-config deployment — Configuration lives in
next.config.tsfor build settings andcontent/navigation.jsonfor sidebar structure. Deploy to Vercel or any Next.js-compatible host.
Verto uses standard Next.js conventions — no custom config file needed. Your content lives in content/, your components in components/, and the MDX pipeline is handled automatically by the build system.
Next Steps
Ready to get started? Head to the Installation guide to set up your first Verto project, explore Inline Comments to learn about Verto's most distinctive feature, or check out the Features section to learn about all available features.