We have a GitHub user entity model that's currently used in Projects page only.
The idea is to create a standalone Users page that will be responsible for showing/searching users within GitHub OWASP organization. Each user entry will be clickable and should lead to another view showing a detailed user page (this is going to be covered in another issue).
The task involves both backend and frontend changes. Currently we don't have user index in Algolia. So as the first step for backend we need to index users (we have plenty of examples how to do that, e.g. issues, projects, chapters).
After creating the users index the data needs to be exposed via users search endpoint (it also needs to be implemented using existing examples, e.g. project).
The frontend part of the task is to create a component for user entry and use it for populating Users page. After the pagination component is ready it'll be added to the users page as well.
We have a GitHub user entity model that's currently used in Projects page only.
The idea is to create a standalone Users page that will be responsible for showing/searching users within GitHub OWASP organization. Each user entry will be clickable and should lead to another view showing a detailed user page (this is going to be covered in another issue).
The task involves both backend and frontend changes. Currently we don't have user index in Algolia. So as the first step for backend we need to index users (we have plenty of examples how to do that, e.g. issues, projects, chapters).
After creating the users index the data needs to be exposed via users search endpoint (it also needs to be implemented using existing examples, e.g. project).
The frontend part of the task is to create a component for user entry and use it for populating Users page. After the pagination component is ready it'll be added to the users page as well.