# Basic Product Documentation

**URL:** <https://meta.discourse.org/t/basic-product-documentation/35719>\
**Category:** Feature\
**Created:** [November 17, 2015, 9:40pm UTC](https://meta.discourse.org/t/basic-product-documentation/35719 "2015-11-17T21:40:23Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Remah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/remah/32/70590_2.png) [@Remah](https://meta.discourse.org/u/Remah)\
**Post date:** [November 8, 2019, 1:12pm UTC](https://meta.discourse.org/t/basic-product-documentation/35719/9 "2019-11-08T13:12:17Z")

</div>

I can’t speak for [discourse.org](http://discourse.org) but I don’t think so because [https://docs.discourse.org](https://docs.discourse.org) is the Discourse API Documentation for developers. Those links are for other interests.

By the way, using those links without a useful label is rather unhelpful behaviour.

The documentation could be improved but it is a massive job for a constantly changing open-source product.

If you look at the #howto category you will see a diversity of interests which cannot be catered for in one document anyway:

- #howto:devs
- #howto:sysadmin
- #howto:admins
- #howto:cmgrs (community managers)
- #howto:faq, #howto:tips-and-tricks for everyone

There’s also an awful lot of crossover in topics and that is very obvious in other categories that impact the UX:

- #Customization > Theme
- #Customization > Plugin

---

_[View the full topic](https://meta.discourse.org/t/basic-product-documentation/35719)._