Gerrit Birkeland

This is infeasible to do in a generic way as TypeDoc generated sites can use the [router](https://typedoc.org/documents/Options.Output.html#router) option to customize how their sites are generated. Furthermore, it requires knowing *how*...

See https://typedoc.org/documents/Options.Package_Options.html That option also needs to be set in packageOptions so that it takes effect during conversion. The option is not set when converting with your current script.

I suspected this would happen at some point... I'm honestly kind of surprised the endpoint still exists. I suspect someone will have to build a custom feed at some point....

[Minimal repro](https://gist.github.com/Rich-Harris/88c5fc2ac6dc941b22e7996af05d70ff): ```ts // txt.d.ts declare module '*.txt' { const shader: 'string'; export default shader; } // index.ts /** @ignore */ export { default as first } from "test.txt" /**...

Ah, this is mostly behaving as intended... if you change the `@ignore` comment to just some text and convert, you'll see that the documentation includes a variable `first`, and a...

After thinking about this some more, I've decided to allow all comments on the export specifier *if* the source symbol does not have a documentation comment. This side-steps the function...

> This means it currently has at least 15 maintainers No, it means it is in a group so that if a current maintainer got hit by a bus, *someone*...

This is working as designed. Grouping/categorization is applied for a given reflection by looking for the `@category` and `@group` tags within that reflection's comments, but `MyClass3` in your example has...

The current rule is "follow regular comment inheritance" Comments are inherited if a member does not specify a comment, or that member uses the `@inheritDoc` tag

Adding support for `@sortOrder` seems like a good idea to me, it should be a block tag with whitespace/comma separated sort strategies, e.g. `@sortOrder static-first, source-order`