Some General Docs Tasks

Some initial ideas

• rapids-js -> node-rapids throughout (#113)
• audit what is/is not included in ref guide
• images/vids in the demo READMEs
• link to demos from the docs
• copy/paste-able code snippets, examples, etc.
• expanded narrative docs, e.g explain groupby in general

cc @trxcllnt @AjayThorve

[trxcllnt]

also we should find-replace /s/rapids-js/node-rapids in any docstrings/markdown files.

[bryevdv]

@AjayThorve I think that looks fantastic and that snippets like that will be super helpful for users. Ideally, eventually we find some way to put examples under test so that that can’t go stale. I am not sure what would be involved with that in this situation. [1] (Only comment: FWIW I find col names like “a” and “b” easier to read than “ser_0” and “ser_1” but either way is good!)

[1] In both Azure for Python and Bokeh examples were in their own scripts that were run to check for errors on CI, and then the Sphinx could inject the script into the docs source code on docs build. But I am not sure what typedoc can do if anything in this vein.