<!--
## 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 improving the project selection and token creation flow within the dashboard application. It includes the addition of new components, updates to existing ones, and enhancements to user notifications and alerts.
### Detailed summary
- Updated import paths for `project-selector` and `team-selector`.
- Added `TokenBanner` component for displaying token creation options.
- Enhanced `DismissibleAlert` to support conditional rendering based on visibility state.
- Introduced `GenericProjectSelector` for improved project selection.
- Modified `ExplorePage` layout and styling for better presentation.
- Added `TokensSection` component with links for launching tokens and NFTs.
- Updated `reportTokenUpsellClicked` function for event tracking.
- Improved UI elements for better user experience and responsiveness.
> ✨ 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**
* Introduced a "Tokens" section on the Explore page, showcasing options for creating ERC-20 tokens (Coins) and NFT Collections.
* Added a promotional token banner on deploy pages for select published token contracts.
* Launched a new project selection page within the team context, streamlining project navigation and selection.
* Added a generic project selector component to enhance project selection flexibility.
* Added tracking for clicks on token creation cards and token upsell banner interactions to improve analytics.
* **Improvements**
* Enhanced layout and styling of the Explore page for better readability and organization.
* Updated project and team selector components for more flexible descriptions and improved navigation.
* Updated team page alert to preserve dismissal state across sessions.
* **Chores**
* Refined import paths for improved code organization and maintainability.
* Refactored dismissible alert component to support optional state persistence.
<!-- 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.