# What is essential content for a new community?

**URL:** <https://meta.discourse.org/t/what-is-essential-content-for-a-new-community/234171>\
**Category:** Community Building\
**Created:** [July 27, 2022, 5:38pm UTC](https://meta.discourse.org/t/what-is-essential-content-for-a-new-community/234171 "2022-07-27T17:38:33Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Tris20](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tris20/32/264639_2.png) [@Tris20](https://meta.discourse.org/u/Tris20)\
**Post date:** [July 29, 2022, 9:27am UTC](https://meta.discourse.org/t/what-is-essential-content-for-a-new-community/234171/10 "2022-07-29T09:27:33Z")

</div>

> [@maiki](#):
>
> Yeah, we might break that down into smaller docs, and have that topic serve as an index; then each sub-topic could be copied and pasted as needed… not the most straightforward process, but would be helpful to allow folks to generate their own doc(s) for their community.

This is what I’ve done for my community. It means when people search “How do I embed a video” for example, they get a topic which covers exactly that, and nothing more. If you don’t allow video on your site, then you can just omit such a topic. Additionallity they can just reply to this specific topic if they have an issue with it, documenting only issues which are related to that topic, instead of the mixture of topics a larger guide contains.

A second advantage of this, is that you can cross reference it in multiple larger guides, taking advantage of the oneboxing of other Discourse Topics.

Here’s an example of a Sailing Guide I have where the topics are broken down into separate topics but unified under a “main” guide. In this case, SBF SEE is s topic for one type of License. SBF Binnen is another topic(not seen here) which has exactly the same navigation information. So I maintain one Navigation topic, and link it into both Guides.

 ![image](https://global.discourse-cdn.com/meta/original/4X/a/f/c/afcb6d9c1e9e74e1e79dc94a79f98205ae59a5bb.png)

Sadly not everything renders well with the oneboxing, but it’s none the less a great way to combine topics, and create a single point of edit, that updates all topics which need to reference that same information.

> [@simon](#):
>
> In an ideal world, that kind of documentation would be available directly in the Discourse instance in a “help” sidebar. Similar to what Slack do. In the non-ideal real world, copying the docs to a topic on the site makes sense.

Completely agree. I find having a Discourse Category better than a sidebar(although it could be accessable with a sidebar) simply because it encourages users to raise issues with the setup of the community, and admins to modify topics to better match their community. For example, replacing default images, with images that relate specifically to their platform.

---

_[View the full topic](https://meta.discourse.org/t/what-is-essential-content-for-a-new-community/234171)._