-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
[FEv2]: Evaluate template for missing components #2965
Comments
This issue has been inactive for 262 hours (10.92 days) and will be automatically unassigned after 98 more hours (4.08 days). |
@meg-gutshall do you think this could be a good thing to work on in RfG coming up? |
This issue has been inactive for 250 hours (10.42 days) and will be automatically unassigned after 110 more hours (4.58 days). |
This issue has been inactive for 370 hours (15.42 days) and is past the limit of 360 hours (15.00 days) so is being unassigned. |
Hey @meg-gutshall, does this one still require discussion before someone can work on it (still has the |
There's one TODO that I left in there but I think I'm going to take it out and open up this issue for work today to avoid scope creep on the issue. |
This issue has been inactive for 240 hours (10.00 days) and will be automatically unassigned after 120 more hours (5.00 days). |
This issue has been inactive for 360 hours (15.00 days) and is past the limit of 360 hours (15.00 days) so is being unassigned. |
Note: Removing |
Hey @meg-gutshall and everyone else watching this issue. I'm thinking about this and moving it forward in terms of Hacktoberfest since we tend to get a lot folks coming around wanting to contribute and help. I'm wonder if we want to keep it as a meta issue as I imagine that by the time we'd finish it that October will be over and we'll lose all the folks who could do the implementation :)
|
Hey @seanmarcia ! I'm going to work on this over the weekend to break down the meta issue into smaller ones. Yes, it will be comparing the current site with the new template site to see if it can be reproduced using the template alone. I have an issue template for those pages that cannot be reproduced using the template alone that the contributor will open. After I clean this up and break out the issues, it will hopefully be an easier-to-follow workflow. |
Closing this issue as per the ADR regarding not going with TailwindCSS - #3217. I know not everyone was on that call so please ask any questions in the slack channel about why this choice was made. |
Summary
This issue is part of the front-end redesign of the Human Essentials app.
We've chosen to implement the admin dashboard template Mosaic for the redesign. First, we must go through all the current pages in our app and ensure all the components we need are included in Mosaic. If not, that's okay! We have a wonderful designer who has volunteered to create any components that are missing, however, we need to identify what exactly these are.
Steps
The goal of this meta issue is to break up the work amongst several people to make this front-end redesign go as smoothly as possible. You'll need to access the app on the staging environment for this issue.
Access the Staging Environment
Navigate to: https://staging.humanessentials.app/
Login as a Sample User
To login to the web application, use these default credentials:
Super Users
Bank Users
Partner Users
Pick a View
This meta issue consists of multiple checkboxes, listing different pages. Choose an item from the View/Partial Listings section below and navigate to a page that contains that view/partial. Compare the elements on the page in our current app against the Mosaic Demo admin dashboard template.
If Mosaic's admin dashboard template can reproduce all components in the view/partial...
Great! Mark the checkbox next to the view/partial so everyone knows it's been assessed, then move on to the next one.
If the view/partial contains components not included in Mosaic's admin dashboard template...
Now it's time to open a new issue, a process we've made incredibly easy for this project. Just navigate to the New Issue Form: Missing Components for Redesign to get started. Change the title of the issue to reflect the current view/partial you're assessing. From there, you'll give the following information:
View/Partial Listings
Follow the documentation in the links above and check off the boxes below. If you have questions on something, leave a comment on this issue and tag @meg-gutshall.
Account Request Mailer
Account Requests
Active Storage
Blobs
Adjustments
Admin
Account Requests
Barcode Items
Base Items
Organizations
Partners
Questions
Users
Audits
Barcode Items
Base Items
Consolidated Logins
Dashboard
Distribution Mailer
Distributions
Donation Sites
Donations
Errors
Forecasting
Distributions
Donations
Purchases
Help
Item Categories
Items
Kaminari
Kits
Layouts
Action Text
Contents
Navigation
Partners
Navigation
Line Items
Manufacturers
Organization Mailer
Organizations
Partner Groups
Partner Mailer
Partners
Authorized Family Members
Children
Dashboards
Distributions
Families
Family Requests
Helps
Individual Requests
Profiles
Edit
Show
Requests
Users
Product Drive Participants
Product Drives
Profiles
Purchases
Reminder Deadline Mailer
Reports
Annual Reports
Request Mailer
Requests
Cancellation
Requests Confirmation Mailer
Shared
Static
Storage Locations
Transfers
Users
Confirmations
Invitations
Mailer
Passwords
Registrations
Sessions
Shared
Unlocks
Vendors
Resources
The text was updated successfully, but these errors were encountered: