# Comparison

> Side-by-side technical comparisons with other docs tools.

Side-by-side technical comparisons between htmlpress and the major docs tools. Each page covers stack, content surface, feature parity, and output model — no recommendations or "pick X if" guidance. Draw your own conclusions.

## Tools

### [Docusaurus vs Htmlpress](/comparison/docusaurus/)

React + MDX docs framework from Meta, Webpack-based.

### [VitePress vs Htmlpress](/comparison/vitepress/)

Vite-native, Markdown-first, Vue-based docs framework.

### [Mintlify vs Htmlpress](/comparison/mintlify/)

Commercial hosted SaaS with MDX content and built-in AI.

### [Starlight vs Htmlpress](/comparison/starlight/)

Astro-based docs theme with islands architecture and MDX.

### [Fumadocs vs Htmlpress](/comparison/fumadocs/)

Next.js App Router docs framework with modular core + UI packages.

### [Nextra vs Htmlpress](/comparison/nextra/)

Next.js docs framework with theme packages and MDX content.

### [MkDocs vs Htmlpress](/comparison/mkdocs/)

Python-based docs generator; Material is the de-facto theme.

### [Hugo vs Htmlpress](/comparison/hugo/)

Go single-binary general-purpose static site generator.

### [Docsify vs Htmlpress](/comparison/docsify/)

No-build docs tool that fetches and renders Markdown in the browser at runtime.

### [GitBook vs Htmlpress](/comparison/gitbook/)

Hosted SaaS with a block editor, Git Sync mirror, and built-in API reference.

## What every comparison covers

- **At a glance** — language, framework, build tool, content format, license, output model.
- **Architecture** — how each tool is built and what it depends on.
- **Content surface** — page format, metadata, components, includes.
- **Feature matrix** — versioning, i18n, search, themes, plugins, sitemap, RSS, custom routes.
- **Output & deployment** — what each emits and where it can run.