A Friendly Place to Share, Ask, and Celebrate
The Facebook Group is our most approachable community space—a front porch where practitioners swap tips, show work-in-progress, and celebrate progress together. It complements the structured problem-solving in the Community Forum and the fast, work-focused flow of the Slack Community and Discord Community. Posts here tend to be story-driven: small wins from a launch, lessons learned after an experiment, photos from Local Meetups, and reflections from recent Events or Training Sessions.
Because Facebook favors discovery and casual browsing, the group is excellent for welcoming newcomers and reconnecting with alumni. When conversations uncover repeatable solutions, moderators route readers to deeper writeups in the Forum, code examples in the GitHub Repo, or recordings linked from the Conference Schedule. In short: the group is the conversation starter; the forum and repo are where answers live for the long term.
What to Post (and Where Links Should Point)
Posts that thrive in the group are narrative and visual:
- Show and tell: Before/after screenshots, a short screen recording, or a short story about how you solved a thorny issue. Link the technical steps to a thread in the Community Forum so future readers can follow along.
- Event recaps: Notes, photos, and highlights from Events, especially workshops listed under Training Sessions or talks on the Conference Schedule.
- Meetup moments: Announce or recap regional gatherings via Local Meetups, then share a link back to the canonical forum summary for details and slides.
- Calls for collaboration: Invite folks to test a GitHub Repo branch, review a checklist, or co-host a community session.
Time-sensitive notices—maintenance windows, security advisories, or last-minute schedule changes—are echoed to Twitter Updates and LinkedIn Updates for reach, then pinned in the group with a link to the authoritative thread in the Forum.
Keeping Knowledge Organized
Facebook’s feed is great for visibility but not ideal for long-term reference. To prevent helpful advice from getting buried, moderators practice “linking out and looping back.” A typical flow looks like this:
- Short story or question posted in the group.
- Answers gathered; a moderator links to a detailed solution in the Forum.
- Any code or configuration is maintained in the GitHub Repo for reproducibility.
- If interest stays high, we schedule a hands-on session in upcoming Training Sessions and list it on Events.
- Recordings or slides are added to the Conference Schedule when applicable, then the group post is updated with “where to watch.”
This loop keeps the group welcoming and lively while protecting the long-term usefulness of the knowledge we create together.
Safety, Security, and Accuracy
We want discussions to be generous and safe. If a post touches security configuration, we ask members to cite current guidance from Web Security Trends and the checklists compiled in Cybersecurity Resources. When a vulnerability or breaking change is discovered, moderators post a concise alert and link to a deeper explanation in the Forum. For urgent reach, we also broadcast to Twitter Updates and LinkedIn Updates.
In cases where sensitive details are involved, we remove specifics from the public thread and preserve a sanitized summary that still teaches the lesson. Accuracy matters more than speed here; if advice evolves, we edit the top comment with a date stamp and pointers to the latest canonical resources.
How the Group Connects to the Rest of the Ecosystem
The group is one of several community doors: jump into the Slack Community for structured real-time help, join the Discord Community for casual voice rooms and co-working, and head to the Forum for evergreen guidance and accepted answers. When you are ready to meet in person, explore Local Meetups. When you want planned learning, register for Training Sessions or browse the full slate on Events. If you prefer to watch talks, check the Conference Schedule for recordings and decks.
As projects mature, we encourage contributors to share code in the GitHub Repo and post progress threads in the group so others can follow along. Finished guides belong in the Forum, with a “story version” in the group to help newcomers discover what’s new.
Ways to Support the Community
If the group helps you connect faster or learn more, consider supporting the ecosystem. One option is a one-time contribution via Donate—funds help us keep servers reliable, publish recordings, and subsidize inclusive Training Sessions. Another is to partner through Sponsor Us, which sustains year-round programming across the group, the forum, Slack/Discord, and in-person Meetups. Non-financial contributions—moderating threads, writing forum summaries, or stewarding examples in the Repo—are just as valuable.
Community health is a team sport. If you see a great answer in Slack or Discord, cross-post a summary here with a link to the canonical forum thread. If you run a local meetup, drop photos and notes to inspire the next organizer. If you ship a helpful repo example, add a short story in the group to invite testers and feedback.
Keep Momentum Beyond a Single Thread
The most valuable posts end with a next step: a forum summary others can reference, a repo link people can try, a training slot on the calendar, or a meetup on the horizon. When your thread reaches a conclusion, loop back with results and edit your original post with “what worked.” If guidance changes—especially around security—tag a moderator so we can update the top comment and broadcast a quick notice. In doing so, you help the group stay welcoming today and useful tomorrow.