Repository navigation
Use Fumadocs' own layout for the docs shell - #1253
Open
sdserranog wants to merge 6 commits into
Open
sdserranog wants to merge 6 commits into
sdserranog wants to merge 6 commits into
Conversation
The navbar, sidebar, table of contents, breadcrumb and previous/next links were a copy of Nextra's theme. They are now Fumadocs' notebook layout and docs page, so the shell gets Fumadocs' mobile menu, theme switch, table-of-contents popover and page actions. - Search keeps the Algolia index. Its hits are shown in Fumadocs' search dialog, reshaped from DocSearch records. - Previous/next skip link-only entries (cross links, toolkit pages, external links), as before. Toolkit pages keep their own breadcrumb and tool panel; the page leaves room for the panel. - The crawler skips the previous/next cards and the "Last updated" line, which are inside the article. - The 404 page uses Fumadocs' home layout. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Closing for now: reviewing this locally first. |
Fumadocs' Algolia client expects its own record format, so hits from the DocSearch index came back as whole text blocks rendered as Markdown, and its dialog renders the Algolia credit outside the dialog, where it shows on every page. The dialog is now built from Fumadocs' search parts with a small DocSearch client: short snippets, the section path of each hit, and plain text with the matches highlighted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The highlight rule now targets the Fumadocs search dialog. The rules for the old InstantSearch classes are gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The footer band pushes the sticky sidebar up at the end of a page, and the sidebar (layer 20) slid over the navbar (layer 10). The navbar is now above it and opaque. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below xl the "On this page" bar sits under the navbar, so the anchor offset grows from 5rem to 7.5rem there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
There are 3 total unresolved issues (including 2 from previous reviews).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0313ba9. Configure here.
…fset - Toolkit pages: "Copy Markdown" and "View as Markdown" request the page with `?format=markdown`. Fumadocs' actions cannot send `Accept: text/markdown`, so they were getting the toolkit JSON. - Search: decode the HTML entities Algolia adds to highlighted text, so `&`, `<` and `>` show as themselves instead of `&`, `<` and `>`. - Phones: only leave room for the "On this page" bar on pages that have it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sdserranog
marked this pull request as ready for review
October 20, 2026 19:24
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What this is
This is the first of three follow-ups to #1250. The goal is to drop the Nextra copies and use Fumadocs' own UI with the Arcade style.
This PR replaces the page shell: the navbar, sidebar, table of contents, breadcrumb, previous/next links and the area under the page. These were a 2,100-line copy of Nextra's theme. They are now Fumadocs' notebook layout and docs page.
The content components (callouts, tabs, steps, code blocks) are not touched here. They come in the next PR, which is also when the page title and the headings get the same type scale.
Preview: https://docs-git-fumadocs-native-shell-arcade-ai.vercel.app
Before and after
Pink numbers mark what changed. The same number points at the same thing on both sides. Everything that isn't marked is unchanged.
A docs page
The end of a page
A toolkit page
Search
Same index, same results, in Fumadocs' dialog.
Video · Screenshot
Table of contents while scrolling
The new table of contents marks where the reader is.
Video
Phones
Fumadocs adds an "On this page" bar on phones. Production has no table of contents there.
Video · Screenshot
The menu opens from the side. Sign Up and Dashboard move into it.
Video · Screenshot
Light mode and the 404 page
Nothing marked: the content is the same, only the shell around it changed.
How it was done
app/en/layout.tsxuses Fumadocs'DocsLayout(notebook). The navbar options are inlib/layout.shared.tsx.app/en/[[...slug]]/page.tsxuses Fumadocs'DocsPage,DocsTitleand page actions.lib/page-neighbours.ts, with a test).components/algolia-search.tsx).components/chrome/and the shell CSS are deleted. The Nextra content CSS stays until the next PR.What we checked so nothing broke
The recordings caught four bugs, now fixed in this PR:
Bugbot's review caught three more, also fixed and checked in a browser:
?format=markdown.<token>andQ&A. They now show<token>andQ&A.Not in this PR
🤖 Generated with Claude Code