Foundations: Evaluate additional resources

[mao-sz]

This issue is for tracking and audit trail, not for assignment. When the team agree on a plan of action for any lessons, sub-issues will be created for assignment.

---

Plan

1. Team will collectively look through all lessons in a section, focusing on its additional resources. If a lesson has ARs, each AR will be evaluated and a eventually a decision will be made as to which ARs get:
   • integrated into the main lesson content (or another lesson's main content) in some way
   • kept as ARs (with justification for not being able to integrate into main lesson content)
   • dropped
2. When a concrete plan is agreed on for a section, sub-issues will be made and assigned as appropriate, detailing exactly what work is to be done for each affected lesson.

This issue will be considered complete once all desired work for each section has been completed.

Sections

• Introduction
• Prerequisites
• Git Basics
• HTML Foundations
• CSS Foundations
• Flexbox
• JavaScript Basics
• Conclusion

[ZackHoang]

Just wondering: will this be issued taken up by multiple people and one person per lesson will see the usefulness of each additional resource in each lesson?

If this issue isn't maintaners-only, I'd love to take a look at one of the lessons and see how ARs could be removed/replaced.

[mao-sz]

@ZackHoang the evaluation will ultimately have to be done by maintainers, since it will eventually concern how we as a team want to deal with the Additional Resources section and the intent and design of our lessons.

When the team agree on what work needs to be done on whatever lessons, then we'll open issues as appropriate which may be open for contribution.

As per the issue details, this issue is only created for tracking and audit trail purposes, as it's part of a large-scale project.

[ZackHoang]

@ZackHoang the evaluation will ultimately have to be done by maintainers, since it will eventually concern how we as a team want to deal with the Additional Resources section and the intent and design of our lessons.

When the team agree on what work needs to be done on whatever lessons, then we'll open issues as appropriate which may be open for contribution.

As per the issue details, this issue is only created for tracking and audit trail purposes, as it's part of a large-scale project.

Ah okay gotcha, so this pretty much is just another issue for tracking how ARs will be dealt with specifically for the Foundations path. I'll be on the look out for anything that pops up then! Thanks!