About the Site Feedback category

Site Feedback
1

Help us improve the community! :hammer_and_wrench:
Share suggestions, report friction, and propose changes to docs, categories, or workflows. The goal: clear, actionable feedback we can address quickly.

What to post

  • :light_bulb: Ideas and proposals (features, tags, templates, categories)

  • :compass: UX issues (navigation, search, notifications)

  • :receipt: Documentation improvements (clarity, conflicts, missing info)

  • :lady_beetle: Forum bugs or odd behavior (with steps to reproduce)

Post checklist

  • :memo: Clear title (problem or proposal in a sentence)

  • :magnifying_glass_tilted_left: Context: where you noticed it and why it matters

  • :link: Links/screenshots (examples, affected pages)

  • :white_check_mark: Suggested fix or options (even rough ideas help)

  • :label: Tags: feedback + type (idea, bug, docs, UX)

Good to know

  • :raising_hands: Be respectful and constructive (see Code of Conduct)

  • :locked: Public forum: search‑indexed; don’t share secrets or internal data

  • :toolbox: Vendor‑agnostic: neutral, reproducible technical content—no promo

Response process

  • :three_o_clock: We triage posts, ask clarifying questions, and label status (planned/in‑progress/done)

  • :megaphone: We’ll post outcomes or link to changes when implemented

3

Btw, so if the structure is nested, then I’d keep:

  1. this topic as a guideline, how to post feedback, pin it; maybe without the possibility of a comment.
  2. to make people talk one level above, https://dt-open-community.discourse.group/c/site-feedback/2