Not the fortnightly round-up — one launch, out today. The Mantine Next.js + Docs template reached 1.0.0: a starter for documentation sites with no docs framework in between, and the template our Mantine documentation sites are moving to. Below, why it exists, what it measures against our Nextra template, and the bug its new home page found in one of our own components.
Mantine Next.js + Docs template
A docs site with nothing between you and Next.js (1.0.0). Our Mantine documentation sites have run on Nextra for a long time, and it served them well — until a newer zod broke its build. From then on every site waited for a Nextra release before it could update a dependency, and the pace of our sites was set by a project we do not run. When I wrote down what Nextra actually did for us, most of the list was assembling libraries we could call ourselves.
So the template keeps only the glue. @next/mdx, the MDX loader Next.js maintains, compiles the pages. Shiki highlights code at build time, so no highlighter ships to the browser. Pagefind builds the search index, and search opens in a Mantine Spotlight with ⌘K. Every piece of the interface — the shell, the sidebar you can collapse with ⌘B, the table of contents, the code blocks — is a Mantine 9 component you own and can restyle. It builds for Vercel, or as a static export for GitHub Pages under a base path.
Bring your Nextra content as it is. It reads Nextra's layout unchanged: the content/ folder, the _meta files, and the same components with the same props — Callout, Cards, FileTree, Steps, Tabs. Moving a site is copying its pages, and the demo site has the guide.
Less than half the JavaScript. Production builds of both templates, measured with Lighthouse on the same machine: 732 KiB of JavaScript on the Nextra template, 301 KiB here; total transfer from about 860 to about 465 KiB; performance 98–99 against 96–98, SEO 100 on both.
A home page drawn like a blueprint. 1.0 also brings a new landing page — graph paper that fades into the page, registration marks, dimension lines, line drawings — shared with our Nextra and Fumadocs templates, each on its own paper: blue here, violet for Nextra, orange for Fumadocs. Both of them shipped it today too, as Nextra template 6.0.31 and Fumadocs template 1.0.25. Each template card shows its live GitHub stars and the extensions wall the npm downloads of the last month, fetched on the server and refreshed hourly. A number that cannot be fetched is left out rather than shown as zero.
The bug that hid the light. The thin light that runs round the hero window is our own BorderAnimate component, and with its in-view trigger it never appeared: the rule that hides an idle border outweighed the one that shows an active one. 1.0.0 shipped with a one-line workaround; BorderAnimate 3.0.13, released today, fixes it at the source, and the template's 1.0.1, a few hours later, drops the workaround.
And the Fumadocs demo moved. The Fumadocs template's live demo is now on Vercel. Its old GitHub Pages address redirects every path to the same page on the new site, so existing links keep working.
https://next-app-mantine-docs-template.vercel.app
https://github.com/gfazioli/next-app-mantine-docs-template
Undolog — open source studio. Every project in one place: gfazioli.github.io · this newsletter lives at undolog.com
FinderGit — a Git-aware file browser for macOS · findergit.app
Lancetta — a menu-bar monitor for the quotas of Codex and Claude Code · lancetta.app
Netfox — a network monitor for macOS · netfox.app
octoscope — a terminal dashboard for GitHub · gfazioli.github.io/octoscope
glancecard — daily SVG cards of your GitHub profile and repositories, for your READMEs · gfazioli.github.io/glancecard
WP Bones — a Laravel-style framework for WordPress plugins, with Bannerize and Scotty built on it · wpbones.com
Mantine extensions — 26 components on npm · mantine-extensions.vercel.app
Raycast extensions — for the Raycast launcher · raycast.com/Undolog


