And given that we have the dropdown on docs for various systems, I think that keeping deno.json in documentation is reasonable, and if other config files are compatible with jsr's schema, then they could be added, but ie package.json is not compatible with the schema.

JSR itself doesn't have special handling for deno.json. The only reference of deno.json is in documentation and it being the default value for a database insertion which always has a value set.

we will make him show up, it's just a matter of time!

the landing page, if its blank, i assume you have an set entrypoint. in that case, the content of the page are derived from the module doc for the entrypoint file (so a top-level jsdoc comment with a @module tag)

Categories currently are only supported when you are using a single .d.ts file, so its likely to not be of much use to you. However if it does, here is an example: github.com/denoland/doc... is the file we use for docs.deno.com/api/deno

Hey, Leo here from the Deno team; feel free to ask me anything related to it