-
Notifications
You must be signed in to change notification settings - Fork 4
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
short course: Move hackmd content to fac slides #8
Comments
Totally agreed, this would be amazing! Note that I did (hastily) make some of the changes from #6, by putting everything in a single hackmd and slightly changing the order of some content. I was in a rush though so it's not pretty at all! If you want a hand with that at all I'd be happy to contribute @charlielafosse 😄 |
I'm more than happy to get involved with this especially whilst the content is still fresh in my head! |
Sounds like a great idea @charlielafosse ! I'd love to flex my reveal.js muscles on this too. Are you happy to work on the slides for weeks 1 & 2? And I'll do the slides for week 3 (JavaScript). |
@bobbysebolao sounds good. I'll comment any changes or thoughts here as I go along 🚂 |
PR for new Week 1 slides here |
and PR #9 for new guidelines in |
Noticed last night with @matthewdking that because lots of the slides were made in my hackmd there are some issues with permissions, editing, slide mode etc.
I think it'd be good to move all that content out into FAC slides (as we did for the Codewars slides), and then put in facresources.com 🌻
It'd be cool to carry out some of the changes that @Oliversw suggested in #3 too. It'd also be great to make our own challenge for the Weeks 1 and 2 project (#2)... it could be similar to the tribute page but basically just cut out some of the confusing user stories.
@bobbysebolao let me know if you want to take it on, but I'm more than happy to go away and do some work on this and keep checking back in with you? Probably a good time to get some changes done as there's a two month break now before the next one (is that right @sofer @yvonne-liu ?)
The text was updated successfully, but these errors were encountered: