Hello there,
We need to come up with a plan for the next iteration of the scholarX platform development.
I hope @EngTeam already discussed a plan on yesterday’s standup. If not consider the following as well.
-
To have an easy-to-set-up development environment.
Currently, we have a hacky setup created by lord @anjisvj
that mainly focused on deploying it on Heroku. We need to come up with a quick solution that helps developers to get things done while we focus on solid architecture. The key is the architecture development should not distract the feature development.
One possible solution is, making the both frontend and the backend running on two different ports. The backend will be a single app that has authentication along with the resources (We already have it). A challenging part would be getting the authentication work with two different ports. There was some cookie issue when we tried it last week, but it would be some fundamental issue that we could fix. -
Revising the flow by getting feedback from the ScholarX team.
-
Making the UI Self-Explanatory. (The current one has a lack of information. It confuses the user. )
Can someone please update the plan?
CC: @EngTeam