> For the complete documentation index, see [llms.txt](https://docs.common.xyz/commonwealth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.common.xyz/commonwealth/community-overview/community-best-practices/organizing-topics-and-thresholds.md). # Organizing Topics & Thresholds Starting with less topics enables for an easier to navigate community for new members. The sidebar also has a limited amount of space so be careful of how many topics you pin to the sidebar. If you’re unsure which topics to start with, the three below are a good starting point: * General * Governance * Community Feedback Setting topic thresholds is dependent on how open you’d like your community to interact with specific topics. Generally, higher topic thresholds are for any governance related topic and lower thresholds (if any) are for general topics and feedback topics. {% embed url="" %} ### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.common.xyz/commonwealth/community-overview/community-best-practices/organizing-topics-and-thresholds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.