// the find
notionnext-org/NotionNext
Turn your Notion workspace into a fast, customizable website. Built with Next.js + Notion API, with multi-platform deployment and no self-hosted server required.
NotionNext turns a Notion workspace into a deployed website on Next.js — you keep writing in Notion and it handles routing, SEO, and rendering for a blog, portfolio, docs site, or product page via Vercel or Zeabur with no server to run. It's aimed at people who already use Notion daily and don't want to adopt a separate CMS or static-site generator just to publish. 26 bundled themes cover most personal and small-team site shapes without touching code.
It has an actual test suite — __tests__/ covers Notion data parsing, sitemap generation, cache file-locking, and per-theme component behavior, which is rare rigor for a project in this category. 26 themes are genuinely different layouts, not one skin with config flags, and there's a hosted live-preview site to compare them before committing. Zero infrastructure to manage: Notion stores the content, Vercel/Zeabur builds and serves it, so running cost for a personal site is close to nothing. The docs are a maintained VitePress site in the repo, not a stale wiki, down to a dedicated content-MCP doc for AI tooling integration.
Rendering goes through react-notion-x, which talks to Notion's undocumented internal API rather than Notion's official public one — a Notion-side change can break pages with no SLA or warning. The components/ directory vendors upwards of 10 comment systems (Twikoo, Giscus, Gitalk, Cusdis, Utterances, Valine, Waline, Artalk) and four chat/AI widgets (ChatBase, Coze, DifyChatbot, Webwhiz) straight into core instead of as opt-in plugins, so you're pulling in a lot of code paths you'll never use. The repo root is cluttered with internal process artifacts (_project-ai/, PROJECT_COMPLETION_REPORT.md, OPTIMIZATION_SUMMARY.md) from what looks like an AI-driven task pipeline, which is noise for anyone trying to read the actual codebase. Node 22 is a hard requirement because of an unrelated dependency (@ai-sdk/google), so the version floor is set by an optional AI feature, not anything core to generating a site.