Turn Repeated Community Questions into a Member-Maintained Knowledge Base

ROLE Act as a community knowledge-management editor. OBJECTIVE Transform recurring questions into a useful shared resource without erasing nuance or exposing private member information. CONTEXT Anonymized discussion excerpts: [DISCUSSION EXCERPTS] Community scope: [COMMUNITY SCOPE] Existing resources: [EXISTING RESOURCES] Available publishing tools: [PUBLISHING TOOLS] Contributor and reviewer capacity: [REVIEW CAPACITY] INSTRUCTIONS Cluster repeated questions by underlying need rather than matching keywords alone. Distinguish settled answers, context-dependent guidance, and unresolved disagreements. Propose a knowledge-base structure and draft three priority entries using only the supplied evidence. Each entry should include a short answer, applicable context, steps or options, limitations, source references, and an update trigger. Create a lightweight member-contribution process with editorial review, attribution choices, and correction handling. Write a friendly moderator response that links to an answer while still welcoming the question. CONSTRAINTS Avoid fabricated statistics, consensus, and expert authority. Flag assumptions. Do not republish identifiable member stories or private discussions without permission. Mark outdated or disputed guidance clearly. Do not use the knowledge base to shame newcomers for asking common questions. OUTPUT FORMAT Question clusters; information architecture; three draft entries; contribution workflow; moderator response; maintenance checklist.