Skip to content

Conversation

@joaquim-verges
Copy link
Member

@joaquim-verges joaquim-verges commented Jul 14, 2025

<!--

## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"

[Portal] Feature: Add 'Next Page' navigation button to footer

If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):

## Notes for the reviewer

- Implements a "Next" button in the footer of inner documentation pages, similar to developer docs sites.
- The core logic in `getNextPageFromSidebar.ts` flattens the sidebar structure to find the next sequential page.
- The button is automatically rendered by `AutoNextPageButton` and integrated into `PageFooter` and `DocLayout`.
- Handles nested sidebar links and excludes the home page.
- Styling is consistent with the existing "Edit this page" button.

## How to test

1. Navigate to any inner documentation page (e.g., `/nebula/overview`).
2. Verify a "Next: [Page Name]" button appears in the footer, alongside "Edit this page".
3. Click the "Next" button and confirm it navigates to the subsequent page in the sidebar.
4. Test on pages with nested sidebar structures (e.g., `/contracts/deploy/overview`).
5. Verify the button does *not* appear on the home page (`/`).
6. Verify the button does *not* appear on the last page of a section.

-->

Slack Thread

Summary by CodeRabbit

  • New Features
    • Added a "Next Page" button to the page footer, enabling users to navigate to the next document based on the sidebar structure.
  • Enhancements
    • Page footer now displays both the edit and next page buttons together for improved navigation.
  • Style
    • Updated layout for better visual organization of footer actions.

PR-Codex overview

This PR introduces a NextPageButton component for navigation and an AutoNextPageButton that dynamically shows the next page button based on the current path. It also updates the PageFooter to include the new button and modifies the layout and utility functions for sidebar links.

Detailed summary

  • Added NextPageButton component for navigation.
  • Created AutoNextPageButton to determine the next page based on current path.
  • Updated DocLayout to include sidebarLinks in PageFooter.
  • Modified PageFooter to conditionally render AutoNextPageButton.
  • Implemented utility functions in getNextPageFromSidebar.ts for sidebar link handling.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@joaquim-verges joaquim-verges requested review from a team as code owners July 14, 2025 07:29
@changeset-bot
Copy link

changeset-bot bot commented Jul 14, 2025

⚠️ No Changeset found

Latest commit: daa92dd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Jul 14, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 14, 2025 10:20pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
nebula ⬜️ Skipped (Inspect) Jul 14, 2025 10:20pm
thirdweb_playground ⬜️ Skipped (Inspect) Jul 14, 2025 10:20pm
thirdweb-www ⬜️ Skipped (Inspect) Jul 14, 2025 10:20pm
wallet-ui ⬜️ Skipped (Inspect) Jul 14, 2025 10:20pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 14, 2025

Walkthrough

A "Next Page" navigation feature was introduced to the document portal. This includes a utility to find the next page from sidebar links, a button component for navigation, and integration into the page footer. The layout and footer components were updated to support and display this new navigation button.

Changes

Files/Paths Change Summary
.../Document/AutoNextPageButton.tsx
.../Document/NextPageButton.tsx
Added new React components for "Next Page" button and auto-determining the next page.
.../Document/utils/getNextPageFromSidebar.ts Added utility function to flatten sidebar links and determine the next page based on current path.
.../Document/PageFooter.tsx Updated to accept optional sidebarLinks prop and render the new "Next Page" button if provided.
.../Layouts/DocLayout.tsx Updated to pass sidebarLinks to PageFooter and reformatted container className string.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DocLayout
    participant PageFooter
    participant AutoNextPageButton
    participant getNextPageFromSidebar
    participant NextPageButton

    User->>DocLayout: Navigates to a document page
    DocLayout->>PageFooter: Renders with sidebarLinks
    PageFooter->>AutoNextPageButton: Renders with sidebarLinks
    AutoNextPageButton->>getNextPageFromSidebar: Find next page (sidebarLinks, currentPath)
    getNextPageFromSidebar-->>AutoNextPageButton: Returns next page info or null
    alt Next page exists
        AutoNextPageButton->>NextPageButton: Render with next page href and name
        NextPageButton-->>User: User can click to navigate to next page
    else No next page
        AutoNextPageButton-->>PageFooter: Renders nothing
    end
Loading

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 45c7a00 and daa92dd.

📒 Files selected for processing (4)
  • apps/portal/src/components/Document/AutoNextPageButton.tsx (1 hunks)
  • apps/portal/src/components/Document/NextPageButton.tsx (1 hunks)
  • apps/portal/src/components/Document/PageFooter.tsx (1 hunks)
  • apps/portal/src/components/Document/utils/getNextPageFromSidebar.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (4)
  • apps/portal/src/components/Document/NextPageButton.tsx
  • apps/portal/src/components/Document/AutoNextPageButton.tsx
  • apps/portal/src/components/Document/utils/getNextPageFromSidebar.ts
  • apps/portal/src/components/Document/PageFooter.tsx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: Size
  • GitHub Check: Lint Packages
  • GitHub Check: Unit Tests
  • GitHub Check: Build Packages
  • GitHub Check: Analyze (javascript)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@graphite-app
Copy link
Contributor

graphite-app bot commented Jul 14, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@github-actions github-actions bot added the Portal Involves changes to the Portal (docs) codebase. label Jul 14, 2025
@codecov
Copy link

codecov bot commented Jul 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.44%. Comparing base (72f75ea) to head (daa92dd).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7605      +/-   ##
==========================================
- Coverage   56.45%   56.44%   -0.01%     
==========================================
  Files         906      906              
  Lines       58115    58126      +11     
  Branches     4226     4228       +2     
==========================================
+ Hits        32810    32811       +1     
- Misses      25195    25205      +10     
  Partials      110      110              
Flag Coverage Δ
packages 56.44% <ø> (-0.01%) ⬇️

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 14, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 63.25 KB (0%) 1.3 s (0%) 590 ms (+44.61% 🔺) 1.9 s
thirdweb (cjs) 353.31 KB (0%) 7.1 s (0%) 3 s (-0.69% 🔽) 10.1 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 211 ms (+795.03% 🔺) 325 ms
thirdweb/chains (tree-shaking) 526 B (0%) 11 ms (0%) 65 ms (+642.92% 🔺) 75 ms
thirdweb/react (minimal + tree-shaking) 19.59 KB (0%) 392 ms (0%) 98 ms (+83.3% 🔺) 490 ms

@vercel vercel bot temporarily deployed to Preview – wallet-ui July 14, 2025 22:12 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb-www July 14, 2025 22:12 Inactive
@vercel vercel bot temporarily deployed to Preview – thirdweb_playground July 14, 2025 22:12 Inactive
@vercel vercel bot temporarily deployed to Preview – nebula July 14, 2025 22:12 Inactive
@joaquim-verges joaquim-verges changed the title Add next button to inner page footers [Portal] Add next button to inner page footers Jul 14, 2025
@joaquim-verges joaquim-verges merged commit a7544f7 into main Jul 14, 2025
24 checks passed
@joaquim-verges joaquim-verges deleted the cursor/add-next-button-to-inner-page-footers-a0c0 branch July 14, 2025 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Portal Involves changes to the Portal (docs) codebase.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants