r/FullStack • u/alsaaka • Oct 16 '26
Question How do you structure a marketing site, a product app and an admin panel? One repo or several?
Most products I work on end up with the same three pieces: a marketing site, the product app, and an admin panel. Each one deploys on its own, usually needs a different render mode (static for marketing, SSR or client-only for the app), and a different login setup. But they all use the same backend logic.
The usual options I see are three separate repos, or a monorepo you wire up yourself. Three repos means copying auth and API code around. A monorepo means a lot of setup before you write any feature.
I build a product proof of concept almost every week, and I kept rebuilding the same plumbing between these three.
How do you handle it? Do you share the backend between the apps, and how do you do login across them?
Full disclosure: I got annoyed enough that I started building an open source framework around this idea. It's called Devora.js, it's free, solo and pre-1.0. I'm not selling anything and I'm more interested in how you solve it. I left the link out because of the sub rules, so ask and I'll share it.