Inspiration
All of us, the members of the team, were part of a learnership in 2019. Of the team 4 were without a stipend but we made an effort to make it to complete the learnership. We did because the reward of completing the learnership far outweighed any financial inconvenience. We know of people who are currently in a learnership. The challenge for them is not financial only but also that learnerships are closed. We have 2 members who have very close connections at MICTSETA as well as SETA. These people know that in the month and possible months to come learnerships will be on hold as unlike high schools there is no solutions made for them as a sector. So we created an LMS to manage that for those relatives of ours.
What it does
The LMS is an application that allows users to interact with classmates on the Ayoba platform while also being able to cover the theoretical component of their learnerships. The platform is accessed on the Ayoba platform and ensures that there is no blockages in terms of delivery. The other advantage of using the Ayoba platform is the secure environment that comes with the platform. Learners are able to access the learning content that is relevant to them. The singed in times that we extract from the application we are able to create a learner profle which shows how much of the content they are consuming. This is something that is potentially highly important to the employers and SETA directors and assessors to make a decision about competence. The send message application allows them to interact with other users such as assessors and fellow students.
How we built it
We started with making a mutlipage application in flask. The application would have assessments, edu games video content and downloadable content. We then had to figure out how to go from almost 6 pages to 1. No fun because we wanted to make a light application which meant cuts and cuts. We identified what we could sacrifice. Then cut. We let go of a login page. We also collapsed video content audio content and downloads into one page. Next and final cut was getting rid of the razor view because we were not in agreement about what the exact deffinition of SPA is. we ended up erring on the side of caution. Then we started a build, we built the assessment module and the quiz and the chatbot. and had to then cut them as cool as they were because they made the application much heaveir than we wanted. We kept the components in play just in case there was a request to integrate these. We then had to look at look and feel. Keep it clean and professional.
Challenges we ran into
We had to make so many cuts to the number of modules built into the app that we focused on making free application there is a premium version that has a full set of features. We also have a look that is not based on crazy feature engineering (bugs). Angular is a cool stack but I don't think anyone was ready to go back to angular from 5 straight to 9 and worst of all experience a change in bootstrap from 3 to 4. Plus we didn't have the ability to see each other.
Accomplishments that we're proud of
We got it done without losing our minds. for almost 4 days straight we have stayed awake and we are not in the best shape but we submitted. So Cool. I probably won't do it again because I miss seeing my team. But we got to drive our families insane with all hours coding to deliver an application that has a life outside of the hackathon.
What we learned
We don't like corona and the only thing I could hate more than that is completing code with the senior member of the team sharing your screen.
What's next for geleza by Nakitechnologies
We are going to try get SETA as well anyone who wants to roll out a digital soltion for the halted education process.
Log in or sign up for Devpost to join the conversation.