Last 12 weeks · 0 commits
2 of 6 standards met
Repository: denoland/docland. Description: The documentation generation website for Deno Stars: 127, Forks: 24. Primary language: TypeScript. Languages: TypeScript (99.8%), Dockerfile (0.2%). License: MIT. Homepage: https://doc.deno.land Open PRs: 0, open issues: 38. Last activity: 1y ago. Community health: 37%. Top contributors: kitsonk, denobot, bartlomieju, dsherret, crowlKats, lucacasonato, satyarohith, cjihrig, aslilac, kt3k and others.
TypeScript
The old doc site provided linkages to globally scoped symbols, the namespace linked to the documentation website otherwise it linked to MDN.
Ideally there would be a way to specify, perhaps in a URL parameter, an import map that goes along with the documented module. There could be UI to tweak the import map, which would update the parameter in the URL and regenerate the docs. For example, the docs for this module breaks due to the bare import specifier: https://doc.deno.land/https://unpkg.com/react-waterfall-render@4.0.0/waterfallRender.mjs That module works great in Deno projects with an import map that assigns a Preact ESM URL to the specifier. I would absolutely 😍 love 😍 to be able to just link to Deno docs in the readme for all my universal Node.js/Deno packages that rely on import maps, instead of maintaining complicated API docs markdown by hand. Hardcoded docs can have mistakes that get permanently published for that package version; whereas having docs generated on demand allows them to just get better and better over time as Deno docs improves, for all versions of the package.
This commit adds a special header to outbound fetch requests. Currently the user-agent header that upstream servers see is which is a common value across all requests made from deployments on Deno Deploy. Having a special user-agent in docland will help upstreams easily identify requests coming from docland.