Producation
Educational platform for psychologists
Educational platform for psychologists
Educational platform for psychologists
Educational platform for psychologists
Public Part
Layouts of pages were made according to approved prototypes for the public part. Previously developed interface prototypes, color palette, and typography were used.
Course Catalog
Implemented navigation by categories, search by name, filtering, and sorting in the catalog. Course cards now include category, author, rating, cost, and the ability to add to favorites.
Course Page
The page structure in the format of a landing page answers the questions: what we offer, what you will get as a result, under what conditions, and what needs to be done to purchase the course.
User Registration
When a course is paid for, the user "along the way" creates an account. All teachers must attach supporting documents and undergo manual moderation.
Personal Account
The personal account is designed for regular use, taking into account the familiar user behavior patterns and the familiar placement of elements for intuitive perception.
Course Management
Tables are a convenient representation for the list of courses, users, and lessons in the library. Each element has a contextual menu for operations: edit, delete, archive. Search, filtering, and navigation across pages are provided for the tables.
Lesson Builder
In the builder, an unlimited number of lessons and modules can be added, their positions changed, renamed, and deleted.
Study Groups
Educational groups were included in the architecture to launch training simultaneously in multiple groups for a single course. The groups may have a limited number of participants and a specific start date for training, depending on the settings.
Interface States
The design includes the basic states of elements, pages, modal windows, pages with successful and unsuccessful statuses - leaving no questions for development about how the interface should behave in one or another case.
Logic and Flowcharts
We started by defining a list of user roles. For each role, a list of functionality was determined. User scenarios were coordinated on flowcharts for each role. Thus, we established the general boundaries of the project.
Interface Prototypes
When there was a common understanding of the platform's logic and user functionality, rough interface prototypes were created. Prototypes were made for each role: guest, listener, teacher, admin, content manager. We also created prototypes for mobile versions.
ACL Policies
To lay the correct application architecture, during the requirements coordination process, access division rules for different user roles were set out in an illustrative table. The development team will use ACL in the project design.
Color Palette
We created a project color palette considering contrast and defined a set of shades for color consistency in the project.
UI Component States
Necessary states of basic UI elements were provided to prevent frontend developers from having questions about how the user interface should behave in one or another situation.
UI Kit
We systematically approach design, so we create necessary UI components in all projects, which are reused during project refinement and scaling. The use of components and variations also speeds up the development team.
Typography
We identified a suitable font pair for headings and established typography rules for different screen sizes, considering adaptability.
Email Design Notifications
We worked on texts, provided system errors, notifications, and email templates.
Educational Certificates
We designed a certificate for course completion, which is generated upon achieving 100% course completion.
Public Part
Layouts of pages were made according to approved prototypes for the public part. Previously developed interface prototypes, color palette, and typography were used.
Course Catalog
Implemented navigation by categories, search by name, filtering, and sorting in the catalog. Course cards now include category, author, rating, cost, and the ability to add to favorites.
Course Page
The page structure in the format of a landing page answers the questions: what we offer, what you will get as a result, under what conditions, and what needs to be done to purchase the course.
User Registration
When a course is paid for, the user "along the way" creates an account. All teachers must attach supporting documents and undergo manual moderation.
Personal Account
The personal account is designed for regular use, taking into account the familiar user behavior patterns and the familiar placement of elements for intuitive perception.
Course Management
Tables are a convenient representation for the list of courses, users, and lessons in the library. Each element has a contextual menu for operations: edit, delete, archive. Search, filtering, and navigation across pages are provided for the tables.
Lesson Builder
In the builder, an unlimited number of lessons and modules can be added, their positions changed, renamed, and deleted.
Study Groups
Educational groups were included in the architecture to launch training simultaneously in multiple groups for a single course. The groups may have a limited number of participants and a specific start date for training, depending on the settings.
Interface States
The design includes the basic states of elements, pages, modal windows, pages with successful and unsuccessful statuses - leaving no questions for development about how the interface should behave in one or another case.
Logic and Flowcharts
We started by defining a list of user roles. For each role, a list of functionality was determined. User scenarios were coordinated on flowcharts for each role. Thus, we established the general boundaries of the project.
Interface Prototypes
When there was a common understanding of the platform's logic and user functionality, rough interface prototypes were created. Prototypes were made for each role: guest, listener, teacher, admin, content manager. We also created prototypes for mobile versions.
ACL Policies
To lay the correct application architecture, during the requirements coordination process, access division rules for different user roles were set out in an illustrative table. The development team will use ACL in the project design.
Color Palette
We created a project color palette considering contrast and defined a set of shades for color consistency in the project.
UI Component States
Necessary states of basic UI elements were provided to prevent frontend developers from having questions about how the user interface should behave in one or another situation.
UI Kit
We systematically approach design, so we create necessary UI components in all projects, which are reused during project refinement and scaling. The use of components and variations also speeds up the development team.
Typography
We identified a suitable font pair for headings and established typography rules for different screen sizes, considering adaptability.
Email Design Notifications
We worked on texts, provided system errors, notifications, and email templates.
Educational Certificates
We designed a certificate for course completion, which is generated upon achieving 100% course completion.
Public Part
Layouts of pages were made according to approved prototypes for the public part. Previously developed interface prototypes, color palette, and typography were used.
Course Catalog
Implemented navigation by categories, search by name, filtering, and sorting in the catalog. Course cards now include category, author, rating, cost, and the ability to add to favorites.
Course Page
The page structure in the format of a landing page answers the questions: what we offer, what you will get as a result, under what conditions, and what needs to be done to purchase the course.
User Registration
When a course is paid for, the user "along the way" creates an account. All teachers must attach supporting documents and undergo manual moderation.
Personal Account
The personal account is designed for regular use, taking into account the familiar user behavior patterns and the familiar placement of elements for intuitive perception.
Course Management
Tables are a convenient representation for the list of courses, users, and lessons in the library. Each element has a contextual menu for operations: edit, delete, archive. Search, filtering, and navigation across pages are provided for the tables.
Lesson Builder
In the builder, an unlimited number of lessons and modules can be added, their positions changed, renamed, and deleted.
Study Groups
Educational groups were included in the architecture to launch training simultaneously in multiple groups for a single course. The groups may have a limited number of participants and a specific start date for training, depending on the settings.
Interface States
The design includes the basic states of elements, pages, modal windows, pages with successful and unsuccessful statuses - leaving no questions for development about how the interface should behave in one or another case.
Logic and Flowcharts
We started by defining a list of user roles. For each role, a list of functionality was determined. User scenarios were coordinated on flowcharts for each role. Thus, we established the general boundaries of the project.
Interface Prototypes
When there was a common understanding of the platform's logic and user functionality, rough interface prototypes were created. Prototypes were made for each role: guest, listener, teacher, admin, content manager. We also created prototypes for mobile versions.
ACL Policies
To lay the correct application architecture, during the requirements coordination process, access division rules for different user roles were set out in an illustrative table. The development team will use ACL in the project design.
Color Palette
We created a project color palette considering contrast and defined a set of shades for color consistency in the project.
UI Component States
Necessary states of basic UI elements were provided to prevent frontend developers from having questions about how the user interface should behave in one or another situation.
UI Kit
We systematically approach design, so we create necessary UI components in all projects, which are reused during project refinement and scaling. The use of components and variations also speeds up the development team.
Typography
We identified a suitable font pair for headings and established typography rules for different screen sizes, considering adaptability.
Email Design Notifications
We worked on texts, provided system errors, notifications, and email templates.
Educational Certificates
We designed a certificate for course completion, which is generated upon achieving 100% course completion.
Public Part
Layouts of pages were made according to approved prototypes for the public part. Previously developed interface prototypes, color palette, and typography were used.
Course Catalog
Implemented navigation by categories, search by name, filtering, and sorting in the catalog. Course cards now include category, author, rating, cost, and the ability to add to favorites.
Course Page
The page structure in the format of a landing page answers the questions: what we offer, what you will get as a result, under what conditions, and what needs to be done to purchase the course.
User Registration
When a course is paid for, the user "along the way" creates an account. All teachers must attach supporting documents and undergo manual moderation.
Personal Account
The personal account is designed for regular use, taking into account the familiar user behavior patterns and the familiar placement of elements for intuitive perception.
Course Management
Tables are a convenient representation for the list of courses, users, and lessons in the library. Each element has a contextual menu for operations: edit, delete, archive. Search, filtering, and navigation across pages are provided for the tables.
Lesson Builder
In the builder, an unlimited number of lessons and modules can be added, their positions changed, renamed, and deleted.
Study Groups
Educational groups were included in the architecture to launch training simultaneously in multiple groups for a single course. The groups may have a limited number of participants and a specific start date for training, depending on the settings.
Interface States
The design includes the basic states of elements, pages, modal windows, pages with successful and unsuccessful statuses - leaving no questions for development about how the interface should behave in one or another case.
Logic and Flowcharts
We started by defining a list of user roles. For each role, a list of functionality was determined. User scenarios were coordinated on flowcharts for each role. Thus, we established the general boundaries of the project.
Interface Prototypes
When there was a common understanding of the platform's logic and user functionality, rough interface prototypes were created. Prototypes were made for each role: guest, listener, teacher, admin, content manager. We also created prototypes for mobile versions.
ACL Policies
To lay the correct application architecture, during the requirements coordination process, access division rules for different user roles were set out in an illustrative table. The development team will use ACL in the project design.
Color Palette
We created a project color palette considering contrast and defined a set of shades for color consistency in the project.
UI Component States
Necessary states of basic UI elements were provided to prevent frontend developers from having questions about how the user interface should behave in one or another situation.
UI Kit
We systematically approach design, so we create necessary UI components in all projects, which are reused during project refinement and scaling. The use of components and variations also speeds up the development team.
Typography
We identified a suitable font pair for headings and established typography rules for different screen sizes, considering adaptability.
Email Design Notifications
We worked on texts, provided system errors, notifications, and email templates.
Educational Certificates
We designed a certificate for course completion, which is generated upon achieving 100% course completion.
