3 ms·

Hey, Leo from Deno here. We recently released a static HTML documentation generator via our `deno doc` subcommand. We also have a similar system for our regis

Hey, Leo from Deno here. We recently released a static HTML documentation generator via our `deno doc` subcommand. We also have a similar system for our registry (here an example: https://deno.land/std@0.209.0/http/mod.ts?s=Server https://deno.land/std@0.209.0/http/mod.ts?s=Server). But we have an outdated system for general use, which is similar to what you have built: https://doc.deno.land/ https://doc.deno.land/. Did you know about this, and did you want to built your own system regardless, or did you not know about it and would this have been something you would have used instead of creating your own system?

theultdev 3y ago
Cool, fwiw I didn't know about the general use and I use deno heavily, here's a comparison of Three.js: Deno Doc: https://doc.deno.land/https://esm.sh/v135/@types/three@0.159.0 https://doc.deno.land/https://esm.sh/v135/@types/three@0.159... TSDocs.dev: https://tsdocs.dev/docs/three/0.159.0/modules.html https://tsdocs.dev/docs/three/0.159.0/modules.html The search UX and documentation UI of TSDocs is better. The availability of Deno is better atm. Though TSDocs was speedier and a better flow when it was working.
- crowlKats 3y ago
  yes, the doc.deno.land is relatively outdated and uses an old system. our static generator via the doc subcommand and registry are the newer systems