OSCSA MOOCs Platform

[sandygudie]

Problem Statement
Open Science Community would like to develop Massive Open Online Courses (MOOCs), which is a free online courses available for anyone to enroll in. We have developed our own materials and will also reuse materials from Open Life Sciences and Turing Way. In order to do that, we need to develop a platform where a participant can log in, and view videos and written materials as lessons. This will be similar to Udemy and other platforms for MOOCs.
Your task is to create a demo of the website using any backend technology. You don't have to create the next Udemy, only a demo and showing how you can implement functionality in the website.

Functionalities

• Users can log in and log out
• Users can access OSCSA videos
• Users can access lesson materials
• Arabic translations available
• (please suggest other suitable features)

Discussions/Planning

• The issue is open to suggestions on tools and technology suitable for this platform.
• Open to collaboration in Frontend Development, Design, and Backend Development.
• PLS ADD YOUR THOUGHTS: https://docs.google.com/document/d/1S31oJKEVf-ywlTEDUf4dHDiUVmCbYWVYE1QbPScLFis/edit

DEVELOPMENT PROCESS:

• DESIGN issue [13/10/2022]: Design Template -OSCSA MOOCs Platform #11
• FRONTEND DEVELOPMENT issue [13/10/2022]: FRONTEND DEVELOPMENT FOR OSCSA MOOCs PLATFORM #10
• BACKEND DEVELOPMENT issue [12/10/2022]: BACKEND DEVELOPMENT for OSCSA MOOCs platform #5

DEVELOPMENT PROGRESS

Design

• Landing page, Sign up, and login pages
  Issue [13/10/2022]: Design Template -OSCSA MOOCs Platform #11
  Figma link

Frontend Development

• Set up Project structure
  issue [14/10/2022]: Frontend Project Structure setup/dev_team2 branch #20
  PR Added frontend_project structure #21
• Landing-page
  issue : [15/10/2022]: Implement the landing page for MOOCs (dev_team2) #36
  PR [17/10/2022] Develop the landing Page #43
• Header
  issue [14-10-2022]: Develop Header and Footer for MOOC App #19
  PR [17/10/2022]Develop Header and Footer Section #37
• Footer
  issue [14-10-2022]: Develop Header and Footer for MOOC App #19
  PR [17/10/2022]Develop Header and Footer Section #37
• Login
  issue [14/10/2022]: Create a Login Page and Sign Up Page (dev_team2 branch) #24
  PR [14/10/2022]: add login-page , signup page , add routing and improve file structure #31
• Sign up page
  issue [14/10/2022]: Create a Login Page and Sign Up Page (dev_team2 branch) #24
  PR [14/10/2022]: add login-page , signup page , add routing and improve file structure #31

Backend Development

• Setup project structure
  issue [12/10/2022]: Backend API [feat] - Setup Project structure #13
  PR [12/10/2022]: Backend API [feat] - Project structure #14
• Database model for users and admin and passwords
  issue [15/10/2022]: Backend API [feat] - User and Admin Database Models #30
  PR [15/10/2022]: Backend API [feat] - users db model #32
• Asynchronous function wrappers -(abstracts try catch block)
  issue [15/10/2022]: Backend API [feat] - Async wrappers and Error handlers #33
  PR [15/10/2022]: Backend API [feat] - async function wrappers and error handlers #34
• Error handler middleware
  issue [15/10/2022]: Backend API [feat] - Async wrappers and Error handlers #33
  PR [15/10/2022]: Backend API [feat] - async function wrappers and error handlers #34
• Authentication middleware
  PR [17/10/2022]: Backend API [feat] - Authentication middleware #44
• Permissions router middleware
  issue [17/10/2022]: Backend API [feat] - Role based permissions router middleware  #45
  PR [17/10/2022]: Backend API [feat] - Role based Permissions handler #46
• Signup
  issue [13-10-2022]: Authentication feature for OSCSA MOOCs platform #7
  PR [16-10-2022] Authentication Routes Created(Signup & Login) #38
• Login
  issue [13-10-2022]: Authentication feature for OSCSA MOOCs platform #7
  PR [16-10-2022] Authentication Routes Created(Signup & Login) #38
• Social signin/signup with Google
  issue [18/10/2022]: Backend API [feat] - Social signin with Google #48
  PR [18/10/2022]: Backend API [feat] - Social signin with Google  #49

[sandygudie]

Suggestions

Frontend Development: ReactJS
Backend:

• Nodejs , Expressjs for APIs;
• Firebase for login authentication(Google) or
• MongoDB for Database(UserAPI, etc) ;
• Cloudinary can be used for storing videos and lesson materials

[ladyami]

but i am already on this task i have created issue

[BatoolMM]

@sandygudie and @ladyami both of you can create a proposal - we allow multiple submissions for this task.

[safa-ismail]

@sandygudie .. i have no knowledge of react js. Can I work on the html and css part ??

[Dhei-vid]

I have experience working with React JS and firebase. So how do you propose we go about it.

[Teslimsama]

I only have experience in html,css,PHP,js

[Teslimsama]

So what task should I handle because it won't be effective if we don't share the work, what do think

[Amidsts]

@sandygudie can we have access to the mongodb database and cloudinary, to be used for the project ?

[AminMusah]

hi @sandygudie I have experience with React and firebase. i am interested in contributing to this project.

[sandygudie]

Hello Team, thank you for the interest to collaborate on this tasks.

Tha project will be broken down into smaller tasks so that everyone can contribute.
Since it’s a demo project we will use a private account for tools needed (cloudinary, MongoDB etc)
Design- We will need a design template for this project.
Aside what I suggested ,feel free to highlight alternative approach to it.

Regrading collaboration, I will suggest a Slack workspaces, @BatoolMM this will also be helpful for long term collaboration/discussion in OSCSA , otherwise we continue here.

Thank you

[safa-ismail]

Hi team, i would like to take the initiative for designing and @BatoolMM May i know how many pages does the demo need? Login page, landing page. Do we need more ?

[sandygudie]

Hi team, i would like to take the initiative for designing and @BatoolMM May i know how many pages does the demo need? Login page, landing page. Do we need more ?

Thank you
Login page and Dashboard pages (users and admin dashboard)
We may not need a landing page for now

[okerekechinweotito]

@BatoolMM is it ok for us to collaborate and work together on this issue or must we make separate independent proposals ?

[okerekechinweotito]

@sandygudie Have you created the slack channel ?. Lets fix a meeting later today so we can decide on the features the site will carry. And then break down the task into multiple issues.

[Dhei-vid]

I agree with @okerekechinweotito, we should create either slack or discord channel so everyone is up to speed.

[ladyami]

@Dhei-vid slack is okay the project should be break down

[elijahndibe]

Pls I'll also like to collaborate on this have the slack channel been created

[Dhei-vid]

I will go ahead and create a slack channel, then post the link here.

[sandygudie]

Hello Team, I totally agree with the slack workspace, I am hoping we could have an official OSCSA Slack Workspace rather than a private workspace, @BatoolMM hoping to hear your suggestion on this .

[sandygudie]

I will go ahead and create a slack channel, then post the link here.

@Dhei-vid I already created one but let's hear from @BatoolMM

[Dhei-vid]

Heres the link for the slack channel - https://join.slack.com/t/slack-qni4624/shared_invite/zt-1hmp78eae-jkh8wKPB3M_A52IyBqWhDA

[okerekechinweotito]

@BatoolMM pls what do you think about the suggestions above

[Kemmie001]

@sandygudie I can work with ReactJs we can split different pages and features into issues so everyone can contribute and be up to speed

[Dhei-vid]

I do not mind handling the login component as we integrate it with firebase or MongoDB.

[Kemmie001]

This is a list of all the pages we will need then we can start breaking them into chunks and creating issues out of them and their features.

• Landing Page
• Login
• Signup
• User dashboard
• Course page
• Admin dashboard
• Upload Course Page
• Edit Course Page
• View Course Page

We can add more. We will need people to handle UI/UX, Frontend, Backend, and project management for all of these.

[oEbuka]

Users should also be able to register { creating a register page }in order to Log in. I would suggest we add this.
I would be working on this task, implementing REACT, Mongo DB , Node JS

[okerekechinweotito]

@Kemmie001 Lets wait to receive some clarifications from the Mentor then we can arrange a meeting and properly plan and outline this

[sandygudie]

Hello Team, While waiting on feedback from @BatoolMM
Please, Let's have a call by 5 PM WAT today( 9 AM PST)
https://meet.google.com/zth-eoem-nnx

[RealRichi3]

@sandygudie i have made the issue for collaboration on the backend API here's the link #5.
Please remember to make the necessary update

[Eshy10]

Hi everyone, I would like to contribute to this project. How do I join looking forward to hearing from you guys. I am skilled in HTML, CSS, JavaScript, React, Nextjs, Vuejs, Ruby on Rails, Typegraphql.

[yukiyuli]

Hello everyone, I'm an Outreachy applicant. I'm interested in this project. I have knowledge of HTML, CSS, JavaScript and vue.

[sandygudie]

Thank You Team for yesterday's meeting, The information shared was insightful. Feel free to visit the docs
We were able to break down tasks in different areas(Design, Frontend, Backend) so that everyone can contribute.
Looking forward to the exciting work ahead!👏

[mildrette]

@sandygudie please I will love to work on these tasks for the front-end

• Landing page
• Header
• Footer

[safa-ismail]

@sandygudie as per discussion will the issues be created for each areas today ??

[BatoolMM]

Thank you, all for your contributions! Several teams are working on this task, but there is one dev branch, let me know if you want me to create another dev branch for your group!

[RealRichi3]

Thanks @BatooIMM, if you will be available for the zoom sessions, we got some suggestions and questions concerning the branches for each proposal

[sandygudie]

#2 (comment)

Yes Please we hoping to discuss that with you tomorrow

[GuddyTech]

Hello @sandygudie can I join the team to collaboratively achieve some of these tasks? Thanks

[sandygudie]

Yes sure @GuddyTech

[ladyami]

@sandygudie is there a UI for this project?

[sandygudie]

@ladyami, UI is in development, some pages are pending Issue

[ladyami]

@sandygudie can I design the pending pages if so what pages are pending? and also in development what task is available?

[sandygudie]

@ladyami Yes sure, you can come up with a design template, please see the open issues for more information

[yukiyuli]

Is there anything I can contribute? I have knowledge of HTML, CSS, JavaScript, and Vue.

[ladyami]

@sandygudie Okay I will work on it thank you

[oEbuka]

@sandygudie Okay I will work on it thank you

Here is what @BatoolMM said : #2 (comment)
So for now it's only a course page that is left. Which is currently in works. You can work on it also.

[ladyami]

@oEbuka I don't need to make another design I thought you stop working on that is why I want to pick it up let's use yours
and can you include FAQ in the design?

[ladyami]

@oEbuka can you please send me the link to the Figma design because the one I see does not have a setting page admin dashboard and profile page

[GuddyTech]

@sandygudie can any task be assigned to me I know HTML, CSS and React. Can we also have a slack channel or discord to enable us interact more on the tasks and how to run them. A google meet would also be appreciated. Thanks in anticipation.

[Rubadel]

I also want to join with for this task, plz could you let me know about your working now?
I have a well plan and a good experience for technology for this task ..

[BatoolMM]

Thank you to everyone for their amazing work 🌷, @sandygudie can you update the main issue by adding more details about the progress by referencing PRs? Also, make sure you reference PRs and issues by their number, not as markdown syntax as I fixed the ones in the "DEVELOPMENT PROCESS". Let me know if this is not clear!

[Teslimsama]

het @BatoolMM i just want to confirm which branch are going to pull requests for

[sandygudie]

Thank you to everyone for their amazing work 🌷, @sandygudie can you update the main issue by adding more details about the progress by referencing PRs? Also, make sure you reference PRs and issues by their number, not as markdown syntax as I fixed the ones in the "DEVELOPMENT PROCESS". Let me know if this is not clear!

@BatoolMM Please review the main issue update, is it in line with what you have in mind?

[BatoolMM]

I love the update you added @sandygudie.
@Teslimsama I believe dev_team2 but it depends on what you will do, @sandygudie can guide you through it.