Post Text:
I’m building an analytical platform using v0 (Vercel) and I’m running into structural issues when trying to unify multiple chats/modules into a single project.
Current setup:
-
I have 7 separate v0 chats, all front-end:
-
1 Platform Landing Page with 6 tiles (one per module)
-
6 separate module dashboards (each built in its own chat)
-
-
All chats are moved into the same project folder
-
Goal: clicking a tile on the landing page should navigate to the corresponding module dashboard
What I’m trying to achieve:
-
A single platform with:
-
Unified UI / design language
-
Proper routing (tile → module)
-
One shared data model
-
-
All modules hosted under one Vercel project, not as disconnected chats
Problem:
-
I’m unable to properly link these chats together into the same Vercel project
-
Navigation between landing page and modules isn’t working
-
When I tried creating a new chat and pasting all code from the 7 modules:
-
v0 does not interpret the existing components
-
It starts generating placeholders instead of the actual visuals/components
-
What I’ve already tried:
-
Moving chats into a single project folder
-
Copy-pasting all 7 zip extracts into a new chat to create new chat with everything with specific prompting (did not work well)
-
linking to vercel project is not allowed for enterprise users.
What I’m looking for help on:
-
Recommended architecture for a multi-module platform in v0
-
Best practice to:
-
Convert multiple chats into one cohesive app
-
Set up routing/navigation between modules
-
Avoid v0 re-generating placeholders when code already exists
-
-
Whether this should be handled via:
-
App Router / Pages Router patterns
-
One “master” v0 chat vs module-level chats
-
Manual restructuring outside v0 (then re-import)
-
If anyone has successfully built a multi-page / multi-module platform in v0, I’d really appreciate guidance on how you structured it and what not to do.