ahh thanks I see it now
Nice! My progress came back! Thanks @QuincyLarson and all the team.
also when night mode will became available?
Soon. If you want, you can watch the pull requests on the FCC GitHub Repo to watch as changes are submitted for review.
Cool, I can now log in on the learn platform (I was previously stuck in a login loop, as many others), thanks for fixing the bug!
As you mentioned the challenges are optional, Is that mean I can take certification by doing projects only.
because when I try to get certification, I got this massage
Please complete the required challenges to claim the Responsive Web Design
@QuincyLarson When you say “future curriculum improvements will be released much faster now”, does that mean the curriculum and projects could be altered again? Because the reason I didn’t get started on the previous curriculum was cause I was waiting for the beta version to become official. Btw, thanks for doing this for the community. Much love
This is a bug. Only the projects are required, but the claim button isn’t working right now.
The curriculum will always be growing and improving as long as FCC is alive. Some lessons will turn out to be less helpful than hoped and need some changes, and there will always be the opportunity for new lessons and even new categories to be added. There are languages and frameworks. There are tools and techniques. There are technical skills and soft skills. There’s always more to learn.
Oh, I think I have a better understanding now. Of course, technology evolves every day and one needs to be up to date. Thanks for clearing me up.
I saw in one of the comments from Quincy about launching official next week after the UI is cleaned up?
I feel you on that. As I completed challenges in the old curriculum, I had this feeling that I wouldn’t remember all the features/commands tied to what they do, and should’ve been saving them. So, for big projects, like the Cap app, I saved a local copy, as sometimes I’d work on them on SublimeText locally. Which turned out to be a god-send. I wanted to do it especially, so I could comment on each feature, so it would ‘stick’ a little better in my memory. It’s hard to remember all the different ways to use a command/feature just having them used once.
Also, it’s frustrating, to have to go back but, not be able to find your own solutions that you’ve already worked on. I’d say, annoying as that sounds, start saving them from now on.
Thank you so much! This is a lot of commitment and effort. really APPRECIATE IT!!!
https://learn.freecodecamp.org/ showing some challenges as tick marked. These challenges are those which were completed already, right? Then why the ‘start curriculam’ starting it from the initial challenge? How to skip the challenges that are already finished?
Will you guys bring back the old JS console? I feel that it would be beneficial for everyone, just for debugging purposes.
Thanks for adding the section on accessibility.
Reviewing the tribute page, the majority had “click here” links.
Perhaps the most frequent design mistake I see.
what do you mean by debugging? is it a programming language too!!!
it is now working… how can i see my completed courses ?
Hey kudos for the improvements, liked the new curriculam but still the design element is not so 2018.
I would like to mention a bug if it counts or not, but while solving the problems when you click on the Curriculam menu from the navBar it gives a blank page or a dead page and i have to refresh it to see its content. @QuincyLarson i dont know if it’s just me , still have a look please. Thanks!
Looking at the repo quickly, at least some of the certificates have proposed fixes. As soon as the fixes are verified, they’ll go live.
‘Debugging’ is the process of finding and removing errors in your code - called “bugs”. We like to attribute this to the (probably) apocryphal story of Grace Hopper finding a moth in a relay of the Mark II.
Enjoy the new courses and keep your eyes out for UI improvements as soon as the critical bugs are addressed.
When you find a bug , please report it as a GitHub Issue after you’ve checked that someone hasn’t already reported it. This particular bug has definitely been reported (a few dozen times ).
But why I’ve lost all my progress?