Can we use DocC to compile Documentation for Apps?

I'm still using all business logic in Objective-C++ for easier use of our C++ code. Looks nicer than what I get from Doxygen

Hi there! I've been trying to play around with the DocC documentation (amazing addition, my favourite for sure this year). Sadly, I'm not able to build documentation for the project. I'm running macOS 11.4 and the Xcode 13 beta (13A5154h). I've tried this on a couple of existing projects and a new fresh one. When I click product -> build documentation it will do a build action and open the documentation for the page I had open last and show all Apple documentation, but I am unable to see any documentation for my project. I am able to add a documentation catalog. That creates the 'index' and a resources folder, which is empty. Is this a known issue, or an issue on my end?

As presented in the talks and documentation I’ve seen so far, DocC works for public and open Swift symbols. But how about stuff for internal use? We are developing a fairly complex mixed source SDK with several components, that would benefit greatly from direct integration of auxiliary content for diagrams and so on. But since many of these parts are for internal use only, they have module or below level visibility. Is there a way to build an internal documentation target that includes this information with DocC, and — if so — how?

Hi, I believe its pretty clear but to confirm, does DocC work with Objective-C based products, i.e static frameworks / libraries?