# Project Resource Documentation Feature

**URL:** <https://forum.inductiveautomation.com/t/project-resource-documentation-feature/66010>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 2, 2022, 5:13pm UTC](https://forum.inductiveautomation.com/t/project-resource-documentation-feature/66010 "2022-11-02T17:13:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [November 2, 2022, 5:22pm UTC](https://forum.inductiveautomation.com/t/project-resource-documentation-feature/66010/2 "2022-11-02T17:22:21Z")

</div>

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 it currently does as a stopgap; adding a `readme.md` to every resource might require adjusting the logic for how each workspace saves & loads resources, which made it a bit of a harder sell at that time.

---

_[View the full topic](https://forum.inductiveautomation.com/t/project-resource-documentation-feature/66010)._
