Here I would like to discuss the next steps for the codelab.
I'd like to focus on 2 things here:
Making the codelab self-paced, to allow learning angular outside of the classroom.
Simplify the process of creating new exercises. This would be a great format to learn not just more advanced angular, but also rxjs, TypeScript and many more things, and it should be really easy to create a codelab for those.
High priority
Inlining learning materials #57
Currently we're using google slides, that works well but has some drawbacks:
Hard to translate in other languages, translators don't get notified on change, which means the slides will stay out of sync
User has to jump between slides and the codelab manually which can be confusing
Not flexible enough - it's not possible to have interactive examples in the slides.
Come up with a good and easy way to create new exercises. #58
The biggest challenge here is the progressive evolution of file content throughout the exercises.
e.g. if I fix a type in main.ts in exercise 1, it has to propagate through every exercise up to exercises 18.
Curently I'm using a home-grown diff markup language, but I would be curious to see what are better ways to do the same.
Here I would like to discuss the next steps for the codelab. I'd like to focus on 2 things here:
High priority
Inlining learning materials #57
Currently we're using google slides, that works well but has some drawbacks:
Come up with a good and easy way to create new exercises. #58
The biggest challenge here is the progressive evolution of file content throughout the exercises. e.g. if I fix a type in
main.tsin exercise 1, it has to propagate through every exercise up to exercises 18.Curently I'm using a home-grown diff markup language, but I would be curious to see what are better ways to do the same.
Medium priority