New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Design for /followers and /following routes #8270
Comments
Hey @cesswairimu I was thinking we can get new contributors to pick this up who have contributed here already and can take on a more experienced task. What do you think? Should we break this issue down into some parts to make it easier? Thanks ✌️ |
Hi @Tlazypanda.. that's a great idea..yeah let's do that. Thanks |
Hi @Tlazypanda @cesswairimu I can pick this up. I am one of the new contributors here and having experience in RoR. |
Sure thing @renugasaraswathy we would love your help ...let me try to break this down in the next few minutes then I will ping you to choose which of the issues you would like work on. Thanks |
@renugasaraswathy the issues are #8277 and #8278 |
@Tlazypanda do you think we should explore other designs for these two? @ebarry would like to hear your thoughts on this too |
Hey @cesswairimu definitely open to this 🎉 I just picked up from what @ebarry had suggested here #8115 (comment) 😅 |
Gotcha, thanks for linking me to that 👍 |
Closing this moved to #8277 and #8278 Thanks @cesswairimu ❤️ |
Please describe the desired behavior.
Currently the /followers and /following route doesn't have design consistent with the rest of the website. We need to implement a design with the same table as the "People who are following" table on the /contributors pages. Reference:- the farthest right hand table on https://publiclab.org/contributors/water-quality.
Additional context (optional)
https://publiclab.org/people/liz/followers
https://publiclab.org/people/liz/following
Reference for the table can be constructed
https://publiclab.org/contributors/water-quality
Broken into:
The text was updated successfully, but these errors were encountered: