Kenneth Lim

I would say only `custom_p5_build.md` and `supported_browsers.md` are archive documentation still around although both are not very relevant at this point. The rest are all superceded by the newer documentations...

@Bernice55231 This is pretty old and I'm not sure still relevant especially considering we have an FES system that can support translated messages as well.

Thanks @sikaili for answering here! @Tsourdox if you have further questions or need additional help with your code, feel free to join the community [Discord](https://discord.gg/SHQ8dH25r9) if you haven't already.

For the inline documentation, it is not great at inferring the right name and parent class/module with the code only so we may need to add additional hints around these,...

I'd like to test the documentation generation first to see how it works, will get to it when I have a bit more time, you can go ahead with next...

@holomorfo I can work on the build a bit later, for now we default to the older glMatrix implementation and keep the numjs class around.

Now that I think about it, I'm not sure the idea I had would work as in this case p5 would just detect itself as having already been defined as...

I think this would be nice to have, however I think one of the challenges would be in the dependency graph building, specifically in the case of a cyclic dependency....

It might be worth to try using the internal modules, which are all written with the addon syntax and sufficiently complex, to figure out the technical details.

After thinking a bit, I think in terms of API design, I would like it to be defined in the addon callback function instead of `p5.registerAddon()`, perhaps through a new...