Level 88
I would make two different projects. If your site is going to use stuff from the application you might want to start looking at build API's.
2 likes
Dec 10, 2015
4
Level 2
Is it wise to separate your marketing site codebase from your app codebase?
TLDR; As per title
I'm thinking of putting my marketing site into a separate repo from the app code as I'm thinking they will have different dependencies and theirs merit in separating the concerns.
It could make scaling up easier as you would add additional resources to either the app or the marketing site depending on what's needs it along with not having to deploy both when only has changed.
Am I overthinking this and/or would this be considered poor/best practice?
(I've also thought of just doing a static site generator or WordPress for the marketing site)
Level 2
@bobbybouwmann Ehm build API's? Meaning using an API to power the site or something else?
Level 88
Well I'm not sure what kind of app you are building but let's say you make a todo app. You might want a mobile and a desktop version. So you then have one API and both website (desktop version) and mobile app will communicate with that API. This way you only have to maintain one server!
I also noticed that I wasn't reading correct. You are talking about a marketing site. That's completely different than what I am talking about :P
1 like
Level 80
@Baadier Can’t hurt. I’ve known people to build apps, and then use something like Jekyll for the marketing site so that if the app suddenly gets a heavy load and crashes the marketing site isn’t taken down as well, and vice versa.
Please or to participate in this conversation.