<!-- ## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes" If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000): ## Notes for the reviewer Anything important to call out? Be sure to also clarify these in your comments. ## How to test Unit tests, playground, etc. --> <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on updating the `QuickstartSection.client.tsx` and `page.tsx` files in the bridge section of the dashboard. It modifies features, links, and documentation references to align with the new bridge functionality. ### Detailed summary - Updated `setupTime` to `5` in `QuickstartSection.client.tsx`. - Changed `features` from `["Swap any token", "Cross-chain swaps"]` to `["Swap any token", "Cross-chain swap"]`. - Updated link `href` from `https://portal.thirdweb.com/payments/swap` to `https://portal.thirdweb.com/bridge/swap` and changed label to "Setup Swap". - Added new documentation link to `page.tsx`: `https://portal.thirdweb.com/bridge`. - Added new playground link to `page.tsx`: `https://playground.thirdweb.com/bridge/swap-widget`. - Removed old commented-out documentation links related to payments. - Removed several links under the footer sections for payments and replaced them with new links relevant to the bridge. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - New Features - Added a direct link to Bridge docs in the header for quicker access. - Added a Playground link in the header to enable easy testing of the Bridge swap widget. - Style - Removed footer sections from the Bridge page to streamline the layout and reduce clutter. - Chores - Updated the “Setup Swap” feature card and its link to point to the Bridge setup URL for improved navigation. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
thirdweb.com
This repo contains the full source for all of thirdweb.com and the thirdweb dashboard.
Starting a local dev server
Run from the root folder (thirdweb-dev/js):
cd <path/to/thirdweb-dev/js>
pnpm dashboard
Building for production
pnpm build
Environment Variables
Some env vars can be overridden that are required for some external services to work. You can find them in the .env.example file at the root level of the project including some descriptions of what they are used for.
To define env vars please create a .env file based on the .env.example template at the root level of the project. This file is ignored by git so you can safely add it to your local copy of the project.
Add your thirdweb clientID and secret key to build a basic functioning version of the site.
Code Structure and Style Guide
Components
- Components should go in a
componentsfolder next to the app page they are used in. - If a component is reused in multiple pages, it should go in the lowest level route folder it is used in. For example, if a chart component is used in all analytics subroutes
/analytics/..., it should go in the/analytics/componentsfolder. - All low-level components such as buttons, inputs, etc. should be shadcn components found in
@/ui. - All composed components reused across all page routes are
blocks, and should also go in the@/uifolder.
Data fetching
- Use RSC wherever possible.
- Write data fetching code in its own function in the same file as the component it is used in, not exported.
- If the same data fetching function is used in multiple components, place it in a file in an
apifolder at the lowest level possible (just like components). If you need to do this you probable aren't organizing your components properly.