Using Dashboards to Help Manage All Community Channels
summary
Built a set of community dashboards that pull Slack and GitHub into a Postgres warehouse and visualize via Superset, showing concrete signals like 4,800 Slack members, thread counts per channel and introductions per week. Pipeline uses Airbyte → Postgres RDS → dbt → Superset; syncing and cleaning take far more effort than expected so vendor syncs (Fivetran/Stitch) are recommended. Key metric is membership by orbit levels (evangelists → lurkers); next step is cross-referencing Slack and GitHub identities.
AI-written summary · about
chapters (5)
related talks
06mLightning Talk: Metrics, How To Measure What Is Going On In Your Community
41mEffective Dashboard Design Using
08mInterview with Stewart Butterfield
43mCommunity Platforms Shootout
32mVisualize more, spend less: Unlock data visualizations with Apache Superset
21mData-driven approaches in a technology startup
26mCode & Community: The Synergy of Community Building and Task Automation
24mData Pipelines to Dashboards