JavaScript: 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
• Organizing Your JavaScript Code
• JavaScript in the Real World
• Asynchronous JavaScript and APIs
• Testing JavaScript
• A Bit of Computer Science
• Intermediate Git
• Finishing Up with JavaScript

Important

Decisions to remove any additional resources does not necessarily mean we think they are bad/should be avoided; our lessons are not meant to be compendiums of every related resource possible, no matter how interesting or personally helpful they may be.

We need to take into account the entire lesson contents. A resource could be very good but if we believe the lesson already covers and assigns enough, and the resource doesn't warrant replacing anything, we'll drop it since we don't need to give it a special mention.

Learners are always encouraged to research independently anyway, and 10 different people might click better with 10 different resources, and we definitely don't need to try and link every one just in case.