Here we learn our way around the deno documentation. When finding something turns out to be difficult, we save a link. When things seem pretty obvious, we rearrange to reflect our new understanding.
These modules do not have external dependencies and they are reviewed by the Deno core team. The intention is to have a standard set of high quality code that all Deno projects can use fearlessly. std 
Run a subprocess, get status, and use pipes. std
Plunder the file system, exists, etc. std