Skip to content

Building and spreading community#

Helpbuttons is designed for people committed to their community. The technical platform is only one part — the success of a Network depends on the people who champion it, explain it, and use it consistently.

This page offers practical strategies for getting a community to adopt a new Helpbuttons Network, and for spreading the platform to other communities that could benefit.

Starting a new Network#

The first days matter most#

A new, empty network is discouraging. Before you announce it publicly, seed it with real content: post a few buttons yourself representing actual needs and offers in your community. An active-looking network invites participation; an empty one does not.

Trust is the real prerequisite#

People adopt digital tools when they trust the people behind them, not just the tool itself. Your first job is not to explain features — it's to be recognizable and trusted in your community. If your community already knows and trusts you offline, they are much more likely to try the tool you recommend.

Practical actions for spreading your Network#

Physical presence#

  • Print and post signs with your network's URL and a QR code. Place them where your community already gathers: community centers, schools, markets, notice boards, local shops.
  • Hand out cards at community events with the network address and a one-sentence explanation of what it's for.
  • If you have a phone number for support, include it — it builds trust.

Live sessions#

  • Organize in-person sessions: meet, talk, and demonstrate the app together. A short live demo is worth ten written explanations.
  • Trust is established face-to-face. Even a brief gathering around a laptop or phone makes the tool feel real.

Online sessions#

  • Host online demos for members who can't attend in person. Record them for people who couldn't make the session.
  • Short video walkthroughs (2–5 minutes) shared via existing community channels (WhatsApp groups, email lists, Telegram channels) lower the barrier to first use.

Lead by example#

  • Use the tool yourself. Post real buttons. Respond to others. If you believe in the principles, embody them — it shows others what participation looks like and why it matters.
  • Coordinators who are active participants create much more active networks than coordinators who only configure and moderate.

Distribute responsibility#

  • Add more coordinators early. Shared responsibility reduces burnout and increases the number of people who feel ownership of the network.
  • Each new coordinator you bring in also brings their own social network and trust relationships.
  • Co-moderation also signals to members that the community isn't dependent on a single person.

Connect to existing networks#

  • Announce your Network in channels where your target community already exists: neighborhood groups, association newsletters, local social media, community radio.
  • Ask partner organizations or groups to share the link with their members.

Growing across communities#

Federation as a growth strategy#

When two communities have overlapping interests or geography, consider federating their networks. Federation allows users to move between instances and for buttons to be shared across networks — without either community losing its autonomy.

This is how Helpbuttons can grow without centralizing: each new community starts its own instance, and instances connect through federation rather than merging into one.

Supporting other communities to start#

If you have experience running a Helpbuttons network, your biggest contribution to spreading the platform is helping others start theirs:

  • Offer to help with setup (it takes less than an hour with Docker)
  • Share what worked and what didn't in your community
  • Introduce them to the Telegram community where they can ask questions

Contributing to the platform#

Communities that find Helpbuttons useful and want it to improve can contribute:

  • Code: fix bugs, add features, improve performance — see Contributing
  • Translation: add or improve language support in api/locales/ and web/public/locales/
  • Documentation: improve these docs for future readers
  • Design: propose or implement UI/UX improvements
  • Feedback: report bugs, describe unmet needs, share your experience

The more communities that use and improve Helpbuttons, the more useful it becomes for everyone.

Getting support#

If you're starting a new network and need help, reach out through:

See Contact for the full list of channels.