Our expanded curriculum is now live on beta.freecodecamp.com and we need your help QA'ing it

Our expanded curriculum is now live on beta.freecodecamp.com and we need your help QA'ing it
0
#289

We’re going to re-enable signups on beta before we push the new platform to production. The only thing you need to claim the certificates is completed projects, and you can build those without even authenticating.

2 Likes

#290

Any announcements on the release or a roadmap detailing the release?

0 Likes

#291

Just track this board:

There was an aggressive triage done recentl-ish, so the bug count is probably understated, but you can see what was deferred post-release.

1 Like

#292

@QuincyLarson’s post in twitter. Still on track for Christmas…

2 Likes

#293

I would love to do the new track and compare with the old one , just not sure if I can do it in a timely manner right now , atleast not until the spring of next year.

0 Likes

#294

We are getting closer to shipping, but unfortunately it won’t be Christmas 2017. Hopefully in the next week or two.

If you’re interested in helping us close the remaining 50 or so beta issues:

Thanks again for your patience and support.

3 Likes

News on the Beta Curriculum?
#295

Where can we look for the announcement of the new release when it happens?

3 Likes

#296

Quincy will undoubtedly post here in the forum as well as on his Twitter, FCC’s Medium publication, and everywhere else related to the community.

2 Likes

#297

Thanks for the info! Will certainly stay tuned in those locations!

0 Likes

#298

@QuincyLarson So which curriculum should I follow now? I am currently on the responsive design part of the current curriculum. Should I abandon it and start the beta instead?

0 Likes

#299

I think the Technical Documentation project is too specific and doesn’t allow for much personal choice.
I spent hours on copying content from Microsoft’s Power BI docs. Then I find out that one of the tests is that you have <code> blocks so I am forced to document a computer language.

And if so, the project’s challenge page should explain that the goal is to build a documentation page for a computer language (and not a device or piece of software).

2 Likes

#300

Would you be interested in opening an issue about this, describing your reasoning and proposing some alternate tests? Here’s the repository:

0 Likes

#301

I think my main issue is that there are no clear user-stories tellingl the user what’s expected of the project before the user actually runs the test, and that was already discussed at length in this issue. I should’ve looked at the test cases before picking a topic, Iguess.

1 Like

#303

I just went thru the Apis And Microservice > Basic Node and Express section this morning and I must say that I really liked it , it is much better than the learnyounode tutorial that we had to go thru in the current curriculum before starting the backend, better in the sense that it is more practical, or at least I can see where the things taught here are and can be directly applied to an application being developed, whereas learnyounode was more hypothetical, IMO.

1 Like

#304

So how much longer until the beta website is actually integrated with the original www.freecodecamp.org?

2 Likes

#305

I am not sure there is really a set timeline, it is more of “when it’s ready it’s ready”.

You can check out the progress here
Still doesn’t give a timeline, but it does give you an idea of what work is left at that moment.

1 Like

#306

Sounds great, thanks for the help!

0 Likes

#307

the message box has class=“message box”, but the challenge is passed by referring to getElementsByClassName(‘message’). That’s what is asked in the challenged even though clicking doesn’t do anything unless you refer to “message box” class.

0 Likes

#308

There’s a spelling mistake on this page, 4th paragraph:

““Values passed to console.log() in the text editor block run each set of tests as well as one more time for any function calls that you have in you code.””

Should be your.

0 Likes

#309

This was already fixed, just not deployed yet.

0 Likes