-
Notifications
You must be signed in to change notification settings - Fork 90
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
Create "Users" Component for /admin #91
Comments
Hey @ForrestLonganecker ! How's this issue going? Just wanted to check in quickly so we have a sense of the project status at the meeting tonight. If you're going to be there, you're welcome to ignore this comment and discuss with me/everyone verbally. |
I had started work on this and then realized that router implementation would help the additional pages grow. I will be coming back to this once I finish implementing the router and will also be at the meeting tonight! |
@ForrestLonganecker okay! Do you have existing work in progress on this? If you're not currently working on it, would it be feasible to open this up for someone else to work on? Again, can discuss tonight, those are the main things I'd want to know re: making sure everyone has something they're excited to work on. |
@maxkwallace I had started but didn't get far, if someone else wants to take over that's |
@maxkwallace to follow up I am now actively working on this ticket! |
Just to update the state of this issue, currently the Some of what still needs to be done:
|
As of #583 the user component is now fulfilling these requirements. |
This task is to create the Component that's comprised of the second-from-the-top card on the page with the title "Users", including transferring all the HTML from http://dev.huntermarcks.net/admin.
Wireframes for more context around the whole users flow:
Accessible validation technique: https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA19
We don't necessarily need to implement routes and/or URLs for the React app (it can be a "single page app", at least to start) but if there are routes, or you want to implement one, this Component should appear on the /admin route. I used "/admin" in the title of the issue only because it's a straightforward way to reference the mockup.
The actual functionality of interacting with the backend (responding to clicks on buttons) should be handled in a separate issue (create it if you want to work on it).
The Component should support displaying a variable-length list of Users, again matching the mockup, and you should use hardcoded data in Javascript to test this functionality if it's not yet possible to get live data from the backend.
This task is done when...
If you create a PR to address this issue you're welcome to send it to me @maxkwallace for review.
The text was updated successfully, but these errors were encountered: