Monorepo for Product and Marketing?

[cobalt jetty]

Should we separate our marketing site from our product repo in the age of AI coding?

Traditionally, we'd split these:
Product repo: Connected to engineering team
Marketing site: Separate repo (think headless WordPress or landing page builder) managed by marketing

But with AI assistants like Cursor and Claude Code, I'm wondering if keeping everything in one repo might actually be better. The AI could understand both the product and marketing context together.
We're building a B2B app for a few hundred users. What's everyone else doing? Separate repos or monorepo?

Monorepo for Product and Marketing?

[frank nexus]

Personally, I prefer to separate things since they have different contexts. We can use a Workspace as the root for two repos. For example, I’m cloning Lee Rob's repo to learn how to build an image compressor, but I'm using a different approach for my own. By using a single workspace, I keep both repos separate and avoid conflicts. Hope this gives you some insight!