BuddyPress Statistics - Website Documentation
BuddyPress family / BuddyPress Statistics
BuddyPress Statistics
Section titled “BuddyPress Statistics”- Plugin
- Premium
- Version 2.0.2
- Docs updated 20 Nov 2026
Track BuddyPress and BuddyBoss community activity with engagement charts, retention analysis, a Community Pulse score, and member-facing profile statistics.
Get started
Section titled “Get started”Requirements, install and first setup.
Shape and build
Section titled “Shape and build”What it does, how to set it up and how to use it.
Keep running
Section titled “Keep running”Upgrades, code changes, answers and fixes.
Every page also has the full sidebar. Open any guide to see all sections at once.
This folder holds the customer and developer documentation for BuddyPress Statistics. The docs live in this GitHub repository. The central Wbcom docs hub is built from it.
Structure
Section titled “Structure”website/├── docs_config.json # Content manifest (categories, titles, slugs)├── getting-started/ # Introduction and installation├── global-settings/ # Admin tabs: Overview, Analytics views, Activity Log, Settings sub-tabs├── user-stats/ # Users tab and the member profile Statistics tab├── group-stats/ # Group Statistics tab├── widgets/ # Sidebar and Dashboard widgets├── developer-guide/ # Developer reference└── faq/ # FAQs and troubleshootingCategories
Section titled “Categories”| Folder | Category Name | Slug |
|---|---|---|
| getting-started | Getting Started | getting-started-bpstats |
| global-settings | Global Settings | global-settings-bpstats |
| user-stats | User Statistics | user-stats-bpstats |
| group-stats | Group Statistics | group-stats-bpstats |
| widgets | Widgets | widgets-bpstats |
| developer-guide | Developer Guide | developer-guide-bpstats |
| faq | FAQ | faq-bpstats |
Images
Section titled “Images”Images belong in images/ inside this folder, saved as .webp, and are referenced with relative paths from each doc (for example ../images/admin-overview.webp).
Updating Docs
Section titled “Updating Docs”- Check every claim against the current plugin code and screens (labels, menu paths, defaults).
- Edit the markdown files in this folder.
- Update
docs_config.jsonwhen you add, rename, or remove a doc. - Commit the changes with the code change they describe.
Customer docs use plain language: no file paths, hook names, or function names. Those belong in developer-guide/.

