Which one is the right way to maintain the UI and back-end code for an open-source project?

I have been working on an open-source project for almost a year now and since the beginning I have been maintaining the front-end and the back-end codebase as two separate repos on github.

This is because the front-end is based on React JS and the server code is based on golang. So I assume that if I coupled both into a single repo, then it could overwhelm the contributors. I have a github action which binds the UI and back-end during the build stage, and pushes each commit to a unified repo, which can be used for building the application from source.

I have taken a look at a few similar projects on github and all have a single unified repo, with both the front-end and back-end under a single tree.

Is my 2-repo approach right or do I need to maintain it as a single repo with a clean documentation to guide the contributors. Please share your thoughts.

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.