# Documentation strategy

**URL:** <https://discuss.openedx.org/t/documentation-strategy/1367>\
**Category:** Build-Test-Release\
**Created:** [February 7, 2020, 7:36pm UTC](https://discuss.openedx.org/t/documentation-strategy/1367 "2020-02-07T19:36:18Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![nedbat](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/nedbat/32/3317_2.png) [@nedbat](https://discuss.openedx.org/u/nedbat)\
**Post date:** [February 18, 2020, 11:30am UTC](https://discuss.openedx.org/t/documentation-strategy/1367/7 "2020-02-18T11:30:27Z")

</div>

One of the ideas I enumerated in my [documentation minifesto](https://discuss.openedx.org/t/documentation-minifesto/1417) was to write words near the code, and then use tooling to publish the words where it was better for readers to find them.

There’s a lot to do to make that happen, including just deciding on the best approaches. [OEP-19 Developer Documentation](https://open-edx-proposals.readthedocs.io/en/latest/oep-0019-bp-developer-documentation.html) covers some of this, but it might need revisiting.

---

_[View the full topic](https://discuss.openedx.org/t/documentation-strategy/1367)._