We all know developers are bust, and documenting API is hard to do. Let's face it
reading somebody else's code is hard particularly if the API is anyting other than small and simple.
It is often harder to write documentation for a function than it is to write the function in the first place.
Most often the doctment barely enough to even understant the simple usage of the API. But ther is one saving
grace - developers love to tinker with som code that is known to work.
with code examples that can play with all in the browser. The real downside is that the jupyter environment has to be setup locally.
It takes substantial knowledge and effort to setup a Jupyter environment. Further, it takes yet more effort to setup everything required
to test a library.
!head --- to be a page this must be at the top of the page
<!-- add a title -->;
<!-- add some custon scripts, in this case the lodash library -->
<link rel="stylesheet" href="https://email@example.com/build/styles/solarized-light.min.css">
<!-- some in-line script -->
let words = ['sky', 'wood', 'forest', 'falcon',
'pear', 'ocean', 'universe'];
<!-- end of the inline script -->
## Simple API Project
## [Lodash Tutorial](./lodash.html)
<iframe width="560" height="315"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
@@include xxx.try --- this includes the body of the file 'xxx.tyy' here (a page fragment)
var x = 5; // var decl (full file scope)
let y = '10'; // scope of this code snippet
!end --- end of the file
... HTML ot add to the bottom of the page goes here...