-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
improve high impact sketch on intro page #62
Comments
To do:
|
Folks keep submitting more icons or redesigning the graphic. FYI, my understanding of this issue is that it doesn't render properly. For example on my desktop I see: If we do want to implement a totally new graphic, might be best to make a new issue. I'm really not in favor of new icons if they are not going to be used throughout the work. |
NOTE: simply replacing this graphic is insufficient. The icons have specific meanings that are used throughout the cookbook:
The lower quadrants refer to low impact work so they donβt receive the same focus. Read the cookbook and you will see the π and β icons next to high impact activities to focus on. A four quadrant prioritization matrix is common. So, Iβd prefer to reuse something in the public space and rather than create new content. |
I think of this. Any Sugesstions? |
I like the table idea best: #62 (comment) Itβs less redundant, reinforces the 4 quadrant prioritization matrix, and should resize and adapt to any screen, but I donβt love the stop sign and sleep emojis. Maybe reverse them?
|
I've updated the table according to your suggestions. The icons have been adjusted for clarityβreversed the stop sign and sleep icons as suggested, and replaced the low effort & low impact icon with a calendar ποΈ to represent scheduled chores. Let me know if this works or if you'd like any further changes! |
Please put low effort on the left and high effort on the right |
I have changed as per your suggestion. Let me know if this works or if you'd like any further changes! |
LGTM! Icymi @numfocus/disc-committee |
Thanks for the feedback! Should I proceed to create a pull request now, or wait for further input from the committee? |
IDK. It canβt hurt to open a PR. Maybe @aterrel has feedback? |
It solves issues numfocus#62
yes thanks for the PR. Much easier to see it in the book that way. |
fixed with #170 |
@melissawm suggested in #60 that this might render better:
The text was updated successfully, but these errors were encountered: