Create a map of videos from Kottans Frontend 2019 course
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 357
- PR merge metrics
- No merged PRs in 30d
Description
Link videos from Kottans FE 2019 course on youtube that aren't linked yet (with e.g. #281) to relevant modules from ./tasks directory
Suggested approach
- Create
./tasks/video-map.md - List all videos from Kottans FE 2019 course on youtube in a table
Here is how it might look:
| Module name | Thumbnail | Video title |
|---|---|---|
| Weather App | ![]() |
Routing Intro - Christina Landvytovych |
more rows
Use Weather App module as a reference guide. Basically the contributor might take the relevant part from the file above and supplement it with (a) module name column and (b) rows for other videos from the youtube channel.
The map will give an idea of what videos remain non-referred to from the modules.
Some videos (intro to offline like course) will not have modules to bind with. These still have to be listed while Module name will be held empty.
It is also important to keep a proper order of videos.
- Link the map with Task listing
Use #281 and #276 as a reference guide.
Skills you will use, or improve, or gain
- Advanced markdown
- YouTube video thumbnail API
To do next
Add remaining videos to relevant modules.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tasks/weather-app.md and the Kottans FE 2019 YouTube playlist, then create tasks/video-map.md using the stated table format. List every video in course order, link each to its relevant module when one exists, leave the module blank otherwise, and link the new map from tasks/README.md.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100
