# Best practice to document non-API functions

**URL:** <https://discourse.julialang.org/t/best-practice-to-document-non-api-functions/108025>\
**Category:** General Usage\
**Tags:** documentation\
**Created:** [December 25, 2023, 5:18am UTC](https://discourse.julialang.org/t/best-practice-to-document-non-api-functions/108025 "2023-12-25T05:18:52Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [December 26, 2023, 9:21am UTC](https://discourse.julialang.org/t/best-practice-to-document-non-api-functions/108025/5 "2023-12-26T09:21:25Z")

</div>

I use this: [Documentation of internals](https://discourse.julialang.org/t/documentation-of-internals/72523)

As a workaround.

---

_[View the full topic](https://discourse.julialang.org/t/best-practice-to-document-non-api-functions/108025)._