-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring in the UI into one repo #54
Comments
I'm contemplating this. The only thing that holds me back is the experience frontend devs have when they want to make a PR. Having a pure frontend repo might feel home turf, while a big repo could be intimidating. |
Unless it has a really great fake api or json files, it is much easier to make new features that way. So that you don't have to say, this feature branch here belongs to this branch over there. |
I'm almost convinced. I have another project with the setup you are proposing.. I think I will bring in the UI in the coming weeks. |
In my other project this proved to be a really good setup. Working on it. |
They have to be deployed together and would seem easier to manage 馃槃
The text was updated successfully, but these errors were encountered: