# Documentation of code **URL:** \ **Category:** General Discussion\ **Tags:** vision\ **Created:** [December 1, 2022, 12:44pm UTC](https://forum.inductiveautomation.com/t/documentation-of-code/67130 "2022-12-01T12:44:29Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 1, 2022, 4:54pm UTC](https://forum.inductiveautomation.com/t/documentation-of-code/67130/7 "2022-12-01T16:54:11Z")
Some thoughts from an IA perspective here: > [@Project Resource Documentation Feature](https://forum.inductiveautomation.com/t/project-resource-documentation-feature/66010/2): > > We have some internal plans to improve the ability to document things - not just a markdown-ey resource file, but perhaps some ability to render those markdown files out into a static webpage to semi-automatically generate an entire reference manual for your project. I don't think you can do things at the level required from a third party module; it would have to be a first-party integration to hook in to these context menus everywhere. If I remember right, the Documentation tool works the way … This is a loose plan, so any ideas anyone has about how this should or could work are appreciated. --- _[View the full topic](https://forum.inductiveautomation.com/t/documentation-of-code/67130)._