> For the complete documentation index, see [llms.txt](https://docs.joingather.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.joingather.org/gather-best-practies.md). # Gather Best Practies ### Best Practices Gather’s App Platform is an incredibly powerful tool—when leveraged intentionally. With care and consistency, your community hub becomes a space full of activity, opportunity, and joy. Without ongoing attention, it can feel like just another resource list. This guide walks through **five best practices** to help your digital home stay vibrant and alive. #### Onboard with Intention Onboarding—bringing someone onto the app for the first time—is crucial. When a new member downloads the app, it should feel like a core touchpoint for your organization. • The strongest outcomes come when app onboarding is integrated directly into organizational onboarding. • Communities that struggle with onboarding often struggle with retention and engagement. If the app is framed as optional or secondary, members will likely default to what they already know: calling or emailing providers for help. #### Have a Point Person Every thriving app has one clear owner. This person: • Oversees overall app health • Delegates content and chat management • Serves as the first point of contact for questions A dedicated point person builds consistency, reduces confusion, and keeps the whole team aligned on management practices. #### Activate Group Chats Our most successful communities have very active group chats. In these spaces, members: • Share experiences • Swap resources • Support each other But people can be shy! It helps to regularly prompt the chats with: • Conversation starters • Relevant questions • Event sign-ups • Timely reminders When done well, the community begins carrying the conversation on its own—and you get to watch the connections flourish. #### Block Time for Content Creation Your app won’t create content on its own—it needs you! Set aside a couple hours each week to: • Add new events • Update resources • Refresh outdated information When content stagnates, engagement does too. Think of your app as a garden: tend to it with care, and watch it bloom. #### Celebrate Wins Your community feels valued when you notice and celebrate their special moments: • Birthdays • Graduations • Milestones • Personal victories Paying attention in chats, noting things shared in-person, and revisiting onboarding answers helps people feel seen, remembered, and cared for. **These are just a few of the ways we’ve found success for our communities. As you engage with your app, let us know what works best for you! We learn the most from our partners about design, functionality, and utility.** --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.joingather.org/gather-best-practies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.