01 / Main
Brand headquarters
High-level overview, proof, and product routing for the whole family.
Main site
One brand, one backend, four focused websites.
The main site is the front door for the family. It explains the product map, builds trust, and sends people to the site that matches what they actually need.
Main siteShared API4 Pages sites
Product lines
MainBrand headquarters and overview
SocialSocial media management
ContentContent, holidays, and daily posts
PhoneAI phone receptionist
02 / Social
Social media management
Dedicated site for scheduling, engagement, and channel consistency.
03 / Content
Content engine
Dedicated site for campaigns, holidays, daily posting, and recommendations.
04 / Phone
AI phone receptionist
Dedicated site for answering calls, routing requests, and booking handoffs.
Why split
Each audience gets a homepage that matches its intent
ClarityVisitors land on the right product without extra explanation.
ConversionEach homepage can use its own headline, proof, and CTA.
SpeedOne backend stays shared while the frontends stay focused.
ScaleNew products can get their own site later without a redesign.
Deployment
One shared API, four separate Pages sites
API Worker
1 shared backend
All four sites point to the same Worker, D1, R2, KV, and Queues.
Pages sites
4 frontends
Main, Social, Content, and Phone each get their own Pages project.
Environment
Per-site config
Each site can swap title, product key, and CTA text without forking the backend.
The main site should stay the broadest page in the family, with the strongest overview and the clearest routing.
Next step
Ready to split the family into four deployable homepages?
Next we can wire the Pages projects, set each domain, and keep the API shared underneath.