Typical directory structure for a project with equally significant server- and client-side parts
You could use git-submodules so that server and client exist separate reports and in one repo that collates them together, but you reference separate repos for both server and client. From the git-submodules docs:
A common issue arises in these scenarios: you want to be able to treat the two projects as separate yet still be able to use one from within the other.
You could adopt a naming convention like so:
- project/client
- project/server
- project/project
Your directory structure that you have proposed would be maintained, but code would be split across multiple repos.