# Packaging good Discourse guides

**URL:** <https://meta.discourse.org/t/packaging-good-discourse-guides/76029>\
**Category:** Site feedback\
**Created:** [12월 14, 2017, 12:24오후 UTC](https://meta.discourse.org/t/packaging-good-discourse-guides/76029 "2017-12-14T12:24:37Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [12월 14, 2017, 10:38오후 UTC](https://meta.discourse.org/t/packaging-good-discourse-guides/76029/9 "2017-12-14T22:38:11Z")

</div>

I have mixed feelings about polls as an example, since 95% of it is “click the poll builder button and use the UI to build the poll”. You may recall that we added poll builder UI to address this a while ago.

I am very _VERY_ anti speculative “hey someone, somewhere might want to know..” type of documentation. It’s a waste of time. However, **if you can make a credible case that people are actually asking a certain “how do I..” question over and over** , that is a valid case for doing this. But I need to see the data proving it, first.

But even better than _documentation_ or _guides_, is to improve the UI / software so people don’t need to ask those questions in the first place.

Just sayin’

 ![just sayin'](https://global.discourse-cdn.com/meta/original/2X/5/54d8c54e91cf88a07fc18e7afbee864d5f365a8e.jpg)

---

_[View the full topic](https://meta.discourse.org/t/packaging-good-discourse-guides/76029)._