D-Spirit learning management system designed
Design overview
Information Architecture (student user type)
When the Information Architecture was ready, we gladly realized that for every user type (admin, moderator, professor, student) many screens wouldn't differ that much. The only difference would be in some context and available actions, depending on the user rights within the system.
Before I got my hands on the internal part of the platform, I decided to design the sign-up/sign-in process as the first user flow. That allowed developers to also start working on the project.
Sign-up / Sign-in
When a student pays for any course, the school admin has to add his/her information into the system. After that, an invitation link to join the platform is sent to the student's email address.