# Moving towards ScholarX v1.1 🚀

**URL:** <https://sef.discourse.group/t/moving-towards-scholarx-v1-1/239>\
**Category:** ScholarX\
**Created:** [March 21, 2021, 5:14am UTC](https://sef.discourse.group/t/moving-towards-scholarx-v1-1/239 "2021-03-21T05:14:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaye](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/jaye/32/810_2.png) [@jaye](https://sef.discourse.group/u/jaye)\
**Post date:** [March 21, 2021, 5:14am UTC](https://sef.discourse.group/t/moving-towards-scholarx-v1-1/239/1 "2021-03-21T05:14:30Z")

</div>

Hello there,

We need to come up with a plan for the next iteration of the scholarX platform development.  
I hope [@EngTeam](https://sef.discourse.group/groups/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](https://sef.discourse.group/groups/engteam)

---

<div class="post-metadata">

**Author:** ![anjisvj](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/anjisvj/32/9_2.png) [@anjisvj](https://sef.discourse.group/u/anjisvj)\
**Post date:** [March 21, 2021, 5:26am UTC](https://sef.discourse.group/t/moving-towards-scholarx-v1-1/239/2 "2021-03-21T05:26:56Z")

</div>

We are having a call 2021-03-20T18:30:00Z to discuss the plan. We’ll update the thread with our conclusion after the call. @jaye

---

<div class="post-metadata">

**Author:** ![jaye](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/jaye/32/810_2.png) [@jaye](https://sef.discourse.group/u/jaye)\
**Post date:** [March 21, 2021, 5:56am UTC](https://sef.discourse.group/t/moving-towards-scholarx-v1-1/239/3 "2021-03-21T05:56:52Z")

</div>

Cool. I’ll try to join

---

<div class="post-metadata">

**Author:** ![jaye](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/jaye/32/810_2.png) [@jaye](https://sef.discourse.group/u/jaye)\
**Post date:** [April 9, 2021, 7:18am UTC](https://sef.discourse.group/t/moving-towards-scholarx-v1-1/239/4 "2021-04-09T07:18:00Z")

</div>

Initiate a thread on emails: please collaborate.

> [@Sending email notifications from the SchoalrX platform](https://sef.discourse.group/t/sending-email-notifications-from-the-schoalrx-platform/247):
>
> Sending email notifications is a functional requirement of the ScholarX Platform. @YohanAvishke @Gravewalker @piumal1999 Do you already have any plan on implementation? I just went through some available Email APIs and came up with the following findings: Sendgrid Free quota: 100/day Java Library: Yes Mailgun Free quota: 5000/month but valid only for 3 months Java Library: Yes Fapimail Free quota: 100/day Java Library: No Please add alternatives if you find any.