Comments (7)
from lenape-timetree.
@rlskoeser @jhimpele Please review the logic I've proposed here on figma on the sequence and logic of interactions with the leaf info and the project intro panels on desktop and mobile. I have numbered the sequence and included descriptions next to each.
-
Please look at what's in scope for this issue at top, in the issue description.
-
One question for you: do you think it's intuitive that the user will have to close a leaf panel to view the project intro again on desktop? Is this logic intuitive? I think we'd discussed this before and seems to be simple and fine, but want to make sure I bring up the intuitiveness of it as we're deciding.
-
Note: I'm also proposing that when the project intro is displayed the “i” icon is disabled at the top – (30% opacity), once a leaf info is displayed the “i” is abled again to let the user select it to view the project intro again
-
@rlskoeser the two buttons are from phosphor icons – the icons are smaller than 40px but I made sure there is enough padding around them to make them a total of 48px tap target for accessibility.
They icons would have been too large on the screen if I made them 40-48px. If you have trouble inspecting their sizes let me know.
from lenape-timetree.
@gissoo everything makes sense here and matches how I was thinking about it. The icons and spacing look good.
I'm not sure how obvious it is that closing a leaf panel will show the intro on desktop — but I'm not sure how much it is needed to show the intro after the beginning, and I think users will find it. (They could also reload the page to see it, fwiw.)
I wonder if it will be confusing that the info icon is disabled when the page is first loaded on mobile, but I think that it will probably be clear enough in actual use.
from lenape-timetree.
My two cents: I don't think it needs to be obvious that closing a leaf panel will return to the intro panel. Mainly because I'm not sure viewers will want to do that. On the other hand, this behavior will be obvious in actual use once the first time a user closes the panel. For that reason, I don't think the ext "I" icon is needed.
Also, where is the Home root leading too?
from lenape-timetree.
@jhimpele I think the home root/footer button should behave the same way as refreshing the homepage/tree page. (We can call this page anything that makes sense to us)
@rlskoeser @jhimpele thank you for the comments! they're super helpful. @rlskoeser I think the disabled button will make sense in actual use as you said.
@jhimpele , the "i" is only on mobile since there is no way back to the intro unless the user refreshes the page/clicks on the home button in the footer. I think UX-wise it's better to account for it than not, I understand it may not seem crucial but it's better practice to account for ways to undo something that's done, or vice versa on the interface other than relying on refreshing the page.
from lenape-timetree.
This issue seems to be resolved. I have adjusted the "i" icon so it's 24px, it seemed to be too large.
from lenape-timetree.
Thanks @gissoo. Do we have an implementation issue or need to create one?
from lenape-timetree.
Related Issues (20)
- As a user, I want the option of zooming in on the timetree on desktop and with buttons, so that the content and functionality is accessible in a variety of modes. HOT 4
- Add shadow styles for Safari HOT 1
- tags that include slashes are not being handled properly HOT 1
- As a user, I want to see an indicator when a link takes me to another site or a PDF, so I know what to expect if I click on it. HOT 1
- when zooming in on a leaf on mobile, sometimes it displays below the panel HOT 2
- when browser resize crosses mobile/desktop threshold, should update svg and reposition the tree HOT 1
- optimize javascript / leaf layout HOT 2
- As a user who finds a leaf detail page from search, I should be prompted to view that leaf in the context of the timetree so that I can experience the project as intended. HOT 2
- zoom in on dedication on mobile HOT 1
- As a content editor, I want the option of marking a leaf as a draft so that I can unpublish content that isn't ready for inclusion in the timetree. HOT 1
- non scrolling HOT 3
- Trunk lines disconnected HOT 8
- VizE Lab logo not appearing HOT 1
- add citation CFF file and include code DOI in the project readme HOT 1
- focus state needs more contrast for low vision users
- page title needs to change when the timetree changes HOT 1
- disabled leaves & labels are not sufficiently visually disabled HOT 2
- disabled leaves are clickable when the tree is zoomed in HOT 1
- split out repository to separate code from content; make theme installable as a hugo module HOT 1
- add collaborator logos to site footer HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lenape-timetree.