That looks wonderfull.

OK, I think I got everything right. Please take a look at:
https://enlightenment.github.io/www-content/gh-pages/api/csharp/api

Some public elements, unfortunately, are also for internal use only, and can be completely hidden from docs.
You probably have a track of those already. I would list:

• IWrapper and implementations of its properties NativeHandle and NativeClass, (both in EoWrapper and generated code),
• internal NativeMethods classes and their public method GetEoOps (both in EoWrapper and generated code).

Apparently, from protected elements only the constructor protected EoWrapper(ConstructingHandle ch) could be of interest to the user, and consequently the struct ConstructingHandle.
Every other protected element can be hidden.
There is also a generated version of this constructor for each class, like protected <ClassName>(ConstructingHandle ch).

OK, @lauromoura @vitor.sousa I am doing a (hopefully) last cleanup of internal classes and fields from the docs (via blacklist).

Well, making these constructors private would mean that we would have to add empty default constructors above in the inheritance tree, and these constructors wold have to be visible somehow. So, the current protected constructors with the remark of being only for internal use seems to be enough.

After D8550, Concrete classes constructors are private and regular classes intptrs constructors are protected.

After playing a bit with grep I found:

• 974 unique ingroups
• 484 unique defgroups
• 501 ingroups without matching defgroup (Full list here P284)

Awesome, thanks, I updated the list in the task description. This task is almost done!

In T7702#132911, @lauromoura wrote:

• _StructConversion classes: Do they need to be public?
  
  No, they can be hidden as private classes inside the structs. Also, the *_StructInternal could be changed to a nested struct .NativeRepr (or another name), avoiding the name to appear twice when typing something like new MyStruct. I'll create a task for it.

Right now these classes are hidden from DocFX via blacklist: 8fc4e948778f

Resolved in D8470

• _StructConversion classes: Do they need to be public?
  
  I'll create a task for it.

Thanks!

• _StructConversion classes: Do they need to be public?

@felipealmeida @lauromoura I updated the task description with a list of issues. Can you please comment on each of them so we can decide if they can be made private or internal, or I need to blacklist them in the doc generation?

Yes, there are a lot of these. @lauromoura and @felipealmeida were already looking at making these classes private or internal so they don't show up in the docs, right?