I notice that AppConfig.h is in the git repo - isn't this autogenerated when we resave the juce project?

There was a lot of proof reading / refinement of the pipeline involved and in total it took me about 4 weeks to complete the entire API doc surface, but now every method has proper documentation. The same is true for all modules, scriptnodes, UI components and preprocessors - they all will have a full reference on the new website.

It also takes in to account forum reports / real world projects and the existing docs that I bothered to write. All code examples are validated against a live HISE instance (if applicable) to ensure that the examples don't hallucinate stuff.

Note that the API browser is just one of the consumers and it doesn't show the full data - class readmes and code examples are website docs only - also some of the funky topology SVGs are not rendered in the popup... Also the MCP server gets a LLM authored version (more dense and technical) - no need to waste tokens with these verbose human facing explanations!