nextjs - 💡(How to fix) Fix Docs: Move Dark Mode Toggle from Footer to Header for Better UX [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#86002Fetched 2026-04-08 02:13:04
View on GitHub
Comments
3
Participants
3
Timeline
8
Reactions
0
Assignees
Timeline (top)
commented ×3assigned ×1issue_type_added ×1labeled ×1
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

The dark/light mode toggle on the Next.js documentation site is currently placed in the footer. While it works well functionally, its position makes it a bit difficult to find—especially for new visitors exploring the docs for the first time.

Suggestion: It might improve discoverability and overall usability if the theme toggle were moved to the header area. This is a more common layout in modern documentation sites (such as React, Vue, and MDN) and helps users easily notice and switch between themes without needing to scroll to the bottom of the page.

Is there any context that might help us understand?

Here’s a screenshot of the current footer where the dark/light mode toggle appears:

When viewing longer documentation pages (for example, Installation), users need to scroll all the way down to find the toggle. For newcomers visiting the documentation, this can be confusing — they may want to switch to dark mode immediately but can’t easily locate the control.

Placing the toggle in the header would make it immediately visible and provide a more intuitive, accessible experience for all users.

<img width="1866" height="897" alt="Image" src="https://github.com/user-attachments/assets/4e274cca-5628-4d74-ae50-dc3fae001df0" />

Does the docs page already exist? Please link to it.

No response

extent analysis

TL;DR

Moving the dark/light mode toggle from the footer to the header area of the Next.js documentation site is likely to improve discoverability and usability.

Guidance

  • Review the current layout and functionality of the theme toggle in the footer to understand the potential impact of moving it to the header.
  • Consider the common layouts used in other modern documentation sites, such as React, Vue, and MDN, where the theme toggle is often placed in the header for easier access.
  • Assess the trade-offs of moving the toggle, including potential effects on the site's design and user experience.
  • Evaluate the feasibility of implementing this change, including any necessary updates to the site's code or design.

Example

No specific code example is provided, as the issue focuses on the layout and design of the documentation site rather than a specific code implementation.

Notes

The success of this change depends on the specific design and implementation of the Next.js documentation site. It is essential to consider the site's overall user experience and design principles when making this change.

Recommendation

Apply workaround: Move the theme toggle to the header area, as this is a common and intuitive location for this control, making it easier for users to find and switch between themes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Docs: Move Dark Mode Toggle from Footer to Header for Better UX [3 comments, 3 participants]