refactor: rename Developer Portal to Developer Dashboard#57
Merged
rickstaa merged 1 commit intofeat/studiofrom Apr 24, 2026
Merged
refactor: rename Developer Portal to Developer Dashboard#57rickstaa merged 1 commit intofeat/studiofrom
rickstaa merged 1 commit intofeat/studiofrom
Conversation
"Dashboard" is the de facto convention for signed-in developer surfaces — Vercel, GitHub, Cloudflare, Supabase, Railway, Stripe, and Netlify all use it consistently. "Portal" can read as enterprise IT (SharePoint, vendor portals), while developers have already settled on "Dashboard" as the term for this surface. This applies the same descriptive-not-aspirational logic that retired "Studio" to the newer "Portal" label. Routes move from /portal/* to /dashboard/*, the (portal) and (portal-auth) route groups become (dashboard) and (dashboard-auth), components/portal and lib/portal are renamed to /dashboard, and the Portal* component filenames and identifiers become Dashboard*. The header pill now reads "Developer Dashboard". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
|
If you merge this into |
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
2 participants
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.
Summary
Stacked on #11. Renames the signed-in developer surface from Developer Portal to Developer Dashboard.
"Dashboard" is the de facto convention for signed-in developer surfaces — Vercel, GitHub, Cloudflare, Supabase, Railway, Stripe, and Netlify all use it consistently. "Portal" can read as enterprise IT (SharePoint, vendor portals), while developers have already settled on "Dashboard" as the term for this surface. Same descriptive-not-aspirational logic that retired "Studio" to the newer "Portal" label.
What changed
/portal/*→/dashboard/*app/(portal)→app/(dashboard),app/(portal-auth)→app/(dashboard-auth)components/portal/→components/dashboard/,lib/portal/→lib/dashboard/,public/images/portal/→public/images/dashboard/PortalHeader,PortalFooter,PortalMobileDrawer,PortalSearch,PortalSectionSelect,PortalSubNav→Dashboard*portal-user→dashboard-user,livepeer-portal:starred-models→livepeer-dashboard:starred-models), DOM ids, commentsReact's built-in
createPortalreferences are unchanged. The externallivepeer.org/portal/quickstartURL is unchanged.Note on stacking
Opened against
feat/studiorather thanmainsince @steph already has visual-improvement work in flight on the portal branch. Either approach works:feat/studiofirst, then any in-flight work rebases on topmainfirst, then rebase this PR ontomainTest plan
npm run build— all 37 routes build,/dashboard/*routes appear where/portal/*used tonpm run lint— 0 warnings/dashboard,/dashboard/explore,/dashboard/stats,/dashboard/settings,/dashboard/login,/dashboard/models/[id]/dashboard🤖 Generated with Claude Code