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

Curriculum progress opening page #34236

Closed
DoviMaj opened this issue Nov 6, 2018 · 10 comments · Fixed by #35421
Closed

Curriculum progress opening page #34236

DoviMaj opened this issue Nov 6, 2018 · 10 comments · Fixed by #35421
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 type: feature request Threads classified to be feature requests. Implementation to be considered as a nice to have

Comments

@DoviMaj
Copy link
Contributor

DoviMaj commented Nov 6, 2018

the curriculum page always opens the basic html section of the curriculum. shouldn't it open my recent track or at least the section im in?

Also would like to request a feature for the curriculum page: that be added a progress bar regarding the full curriculum as well as the current track in progress. and better navigation

@DoviMaj
Copy link
Contributor Author

DoviMaj commented Dec 19, 2018

no one thinks this is important?

@coder077
Copy link

@raisedadead is it something that we should be concerned? If yes then I can take a look at it!

@hughforsyth
Copy link

@coder077 I would add that in 2015 when I last used FreeCodeCamp it did work how @DoviMaj is requesting, i.e., when you went to the curriculum page (or "Map" as it was then) it would expand the tree at the first incomplete lesson, so this is something that has broken/changed in the last few years.

I personally would like to see it working how it did in 2015 as I'm currently re-doing the certification based on the new curriculum and it was easier when FCC prompted you with what lesson you should do next, rather than showing you lessons you have already completed. I'm not suggesting it's worth investing 100s of man hours but it's probably worth a quick look as I suspect this is a simple bug rather than by design. It does remember where you are in the tree if you never refresh the page so perhaps there is a some sort of variable storing your place that is supposed to persist in a cookie or something.

@raisedadead raisedadead added 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 type: feature request Threads classified to be feature requests. Implementation to be considered as a nice to have labels Feb 25, 2019
@xolowapx
Copy link

@raisedadead Has anyone fixed it yet?

@raisedadead
Copy link
Member

raisedadead commented Jul 26, 2019

Nope this is available and open for implementation, if you are interested.

@ojeytonwilliams
Copy link
Contributor

I made some progress in #35421, but it's been a while since I looked at it. I'll take another look and see if that PR is any use.

@brianRey2017
Copy link

I would like to help if you need it @ojeytonwilliams @raisedadead

@ojeytonwilliams
Copy link
Contributor

Hey @brianRey2017, thanks for the offer! I think the PR is basically okay, but there's one change I'm looking to make (handling the completion of an entire section of the curriculum). I'll have a go at that this week and let you know if I run into difficulties.

@brianRey2017
Copy link

Ok. I'll be waiting here 😄

@dj-mc
Copy link

dj-mc commented Aug 27, 2019

This is an issue that keeps bugging me. Here is a screenshot of what's happening.

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 type: feature request Threads classified to be feature requests. Implementation to be considered as a nice to have
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants