@pebrc :

Differences to the manually migrated files: API reference tool creates a single file not a file per group, we could however adjust that if needed.

I believe that's totally up to you to decide.

In the asciidoc system (here) they appear to be separate documents, that's why our automatic migration created different markdown files for each item.

If you think it's better to show all the content in the same page (like k8s api docs) I'm almost sure that's totally fine.

@pebrc :

Differences to the manually migrated files: API reference tool creates a single file not a file per group, we could however adjust that if needed.

I believe that's totally up to you to decide.

In the asciidoc system (here) they appear to be separate documents, that's why our automatic migration created different markdown files for each item.

If you think it's better to show all the content in the same page (like k8s api docs) I'm almost sure that's totally fine.

I spent a bit more time on breaking up the single file. The tooling we have makes it hard to generate the grouping into files the way the migration has created them. I think I stick with a single file if that's OK for now. If we have more time to optimise this later we can think about breaking it up into single files per API kind.