WE ARE IN THE ENDGAME. Last week and a half, while we are very close to finishing we still have a couple issues to address
Crucial Issues
[x] Implementation of the following page
[ ] Search bar implementation
[x] Followers and following bar and implementation
[ ] Styling fixes
General Issues
[ ] Reactions for posts
[ ] Compatibility score based on music taste
Cool ideas to add
[ ] Generating a playlist or "ReaList"
Below I have some implementation ideas for each issue
Following Page
It seems that it will function similarly to the community page. We will just need to access each user Id that one follows and fetch their info.
We do need to change the button and the title. Which I made an issue for.
Search Bar implementation
We will need to fetch all the current users in the database and place them into an array. Given that we don't have the option for users to delete their account we could just load all users into an array (or some data structure) to prevent having to fetch multiple times. Of course, we will have to account for new user creation and whether we append that user to the array or some other implementation.
Then we will also have to implement the search part. My idea is when a user is going to type a username some suggestions already pop up below the search bar (like how google does it). I have an example that I worked on before. It requires only javascript and the map function.
Following and follower
Right now we have placeholders for both. On a user's profile page we have a button to follow as well. Both counts can be measured through some form of array or storage of user ids in the database, and we just have to count them.
Another thing that I would like to have is a popup window that shows a list of either followers or following when you click on the text in the profile page. i'll make an issue on it for anyone that wants to try.
Styling Fixes
The main part with this is to make sure all styles and animations are consistent, specifically with varying size windows and screens. I know the nav bar will need some fixing along with other components. The main fixes will have to do with changing component sizes based on screen size, which there are many resources to help with this. This should be saved as a final issue.
WE ARE IN THE ENDGAME. Last week and a half, while we are very close to finishing we still have a couple issues to address
Crucial Issues
General Issues
Cool ideas to add
Below I have some implementation ideas for each issue
Following Page
It seems that it will function similarly to the community page. We will just need to access each user Id that one follows and fetch their info.
We do need to change the button and the title. Which I made an issue for.
Search Bar implementation
We will need to fetch all the current users in the database and place them into an array. Given that we don't have the option for users to delete their account we could just load all users into an array (or some data structure) to prevent having to fetch multiple times. Of course, we will have to account for new user creation and whether we append that user to the array or some other implementation.
Then we will also have to implement the search part. My idea is when a user is going to type a username some suggestions already pop up below the search bar (like how google does it). I have an example that I worked on before. It requires only javascript and the map function.
Following and follower
Right now we have placeholders for both. On a user's profile page we have a button to follow as well. Both counts can be measured through some form of array or storage of user ids in the database, and we just have to count them.
Another thing that I would like to have is a popup window that shows a list of either followers or following when you click on the text in the profile page. i'll make an issue on it for anyone that wants to try.
Styling Fixes
The main part with this is to make sure all styles and animations are consistent, specifically with varying size windows and screens. I know the nav bar will need some fixing along with other components. The main fixes will have to do with changing component sizes based on screen size, which there are many resources to help with this. This should be saved as a final issue.