Skip to content
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

Make "Learn how FCC Works" challenge easier to navigate (UX) #10056

Closed
oalhait opened this issue Aug 3, 2016 · 15 comments
Closed

Make "Learn how FCC Works" challenge easier to navigate (UX) #10056

oalhait opened this issue Aug 3, 2016 · 15 comments
Labels
help wanted Open for all. You do not need permission to work on these. scope: UI Threads for addressing UX changes and improvements to user interface

Comments

@oalhait
Copy link
Contributor

oalhait commented Aug 3, 2016

Challenge Name

Learn how Free Code Camp Works

Issue Description

Going through the 12 slide slideshow is a bit tedious, as you have to keep pressing "Go to my next step" (as opposed to pressing arrow keys to navigate between slides). The image sizes are also not relative to the screen height, so if your window is small you'll have to scroll down every time to read the text/switch between slides.

Screenshot

screen shot 2016-08-02 at 4 49 39 pm

screen shot 2016-08-02 at 4 49 28 pm

screen shot 2016-08-02 at 4 46 15 pm

@ghost ghost added status: discussing Under discussion threads. Closed as stale after 60 days of inactivity. scope: UI Threads for addressing UX changes and improvements to user interface labels Aug 3, 2016
@ghost
Copy link

ghost commented Aug 3, 2016

I also think that this challenge could do with some UX improvements. To start, I think all of these challenges should be able to be navigated via the arrow keys. The issue with scrolling is annoying also. The images could probably be made smaller.

cc / @FreeCodeCamp/issue-moderators

@QuincyLarson
Copy link
Contributor

@atjonathan @oalhait yes - we plan to significantly reduce the length of these. If we used a fixed height for the images and their text, we could eliminate a lot of the variability in height.

I think the most immediate improvement would be to go to the next challenge with the left and right arrows.

@ghost ghost added help wanted Open for all. You do not need permission to work on these. and removed status: discussing Under discussion threads. Closed as stale after 60 days of inactivity. labels Aug 3, 2016
@oalhait
Copy link
Contributor Author

oalhait commented Aug 3, 2016

I'll take on the left/right arrow issue! One question though: where do I find the html/css/js of the specific challenge?

@raisedadead
Copy link
Member

Hi @oalhait thanks for helping out on the UX.

The challenges are now on react infrastructure, most of the views/controllers are in the /common/app, challenges are json files that are in the /seed directory.

The views are all JSX, styles are LESS

Do look a the Guidelines for Contributing., happy fixing!

And reach out to the Contributors Chat room. for assistance.

@viditmaniyar
Copy link
Contributor

viditmaniyar commented Aug 3, 2016

@oalhait - BTW - The link in your issue description of the issues points to localhost ;)

@oalhait
Copy link
Contributor Author

oalhait commented Aug 4, 2016

@raisedadead thanks for the tips, I'm on it now!
and @IamRudra HAHAHA oops, was viewing on my local instance

@sachinmour
Copy link
Contributor

sachinmour commented Aug 8, 2016

arrow
suggestions needed for -

  • what to do when at the end of the challenge.. go to next challenge
  • what to do when we want user to open a link before proceeding to next challenge
  • what to do for the text which shows numbering of the steps...ie..(4/12)
    @QuincyLarson @atjonathan

@QuincyLarson
Copy link
Contributor

QuincyLarson commented Aug 9, 2016

@sachinmour Oh - when I said arrow keys I meant on the keyboard - not adding additional UI elements.

Rather than add additional buttons, I think it would be better to ensure that the next step button and previous step buttons are always in the same place (by constraining the height of images/text) so you could just click them repeatedly.

But we do want to add some hotkeys. The hotkeys are located in main.js

As for your question about what should happen if they encounter a step where they must open a link before proceeding, well, clicking the arrow key simply wouldn't advance them and would instead make the "open link in new tab" button move somehow to draw attention to it and notify the user that they can't advance until they click it.

@sachinmour
Copy link
Contributor

@QuincyLarson got it..

@sachinmour
Copy link
Contributor

10056
@QuincyLarson

@anushreddy
Copy link

Is the challenge solved ?

@ktajpuri
Copy link
Contributor

ktajpuri commented Oct 7, 2016

This doesn't work yet?? Does it require some help?

@ghost
Copy link

ghost commented Nov 2, 2016

This issue is open as help wanted @ktajpuri, @anush6533

@BerkeleyTrue BerkeleyTrue added the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label Jan 25, 2017
@QuincyLarson QuincyLarson removed the status: on the roadmap Long term plans and features. label Sep 2, 2017
@systimotic systimotic removed their assignment Sep 2, 2017
@raisedadead
Copy link
Member

We have transitioned to a smaller set of navigation on the beta, I guess we could close this @QuincyLarson ?

@QuincyLarson
Copy link
Contributor

@raisedadead Yes - I don't think it's worth improving at this point. We only use a few of these slide challenges, and they're short - I think the longest one is like 4 slides.

@QuincyLarson QuincyLarson removed the status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. label Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Open for all. You do not need permission to work on these. scope: UI Threads for addressing UX changes and improvements to user interface
Projects
None yet
Development

No branches or pull requests

9 participants