What Shipped This Week: SnipShare, WB Member Wiki, an Astro Store, and What’s Coming Next
It’s been one of those weeks where a lot of things that have been in progress for a while all came together at once. Two new plugins launched, a bunch of updates shipped across the catalog, we rolled out a completely new approach to product pages and docs, and I’ve been quietly building something new that I want to share for the first time.
Let me walk through all of it.
SnipShare: A Code-Sharing Platform for WordPress Communities
The first new plugin is SnipShare, and this one’s been on my mind for a long time.
If you run a developer community or any kind of technical site on WordPress, your members are sharing code somewhere. Almost certainly somewhere that isn’t your site. Pastebin. GitHub Gist. Chat messages. Every time that happens, you lose engagement, you lose content, and you lose the accumulated knowledge that makes a technical community genuinely valuable over time.
There’s never been a WordPress plugin for this. I checked, the plugin directory has nothing, CodeCanyon has nothing. Every code-sharing tool on the web is a SaaS product built for individual developers, not for WordPress community platforms. So we built SnipShare.
It gives your community a self-hosted, versioned, searchable code-sharing platform built directly into your WordPress site. Members create pastes from the front end with a CodeMirror 6 editor. Code stays on your server. If you’re running BuddyPress, paste activity appears in the activity feed, every member gets a Pastes tab on their profile, and stars and forks trigger notifications.
A few things I’m particularly happy with in v1.0.0:
- Burn-after-read, a paste that deletes itself on first view. Simple idea, genuinely useful for sharing credentials or sensitive snippets within a team intranet
- Side-by-side diff view, every edit creates a revision, and you can compare any two versions with a proper diff viewer. This is one of those features that changes how people actually use the tool
- 5 privacy levels, public, unlisted, private, password-protected, and burn-after-read. One toggle per paste, no complex admin configuration needed
- The REST API, full CRUD for pastes, files, revisions, collections, stars, and reports under
snipshare/v1. Built it properly from the start rather than bolting it on later as an afterthought - bbPress integration, paste shortcodes render inline inside forum posts, so members can share code directly in forum threads without leaving
Setup is genuinely fast: install the plugin, create a WordPress page, add the [snipshare] shortcode, and your paste platform is live, automatically styled to match your existing theme, no additional configuration required. BuddyPress integration activates automatically when BuddyPress is present.
The live demo is at snipshare.instawp.co and there’s an instant sandbox at InstaWP if you want to try it without installing anything. Full details, pricing, and docs on the SnipShare product page.
WB Member Wiki: Collaborative Wikis for WordPress
The second new plugin is WB Member Wiki, a collaborative wiki platform that runs entirely inside your WordPress install.
The problem it solves is familiar to anyone who’s run a community for a while. Knowledge gets created constantly, in forum threads, in support tickets, in member conversations. And then it disappears. There’s no place for it to accumulate and become useful to the next person with the same question. A wiki fixes this. But until now, there’s been no decent WordPress-native option for community wiki editing.
WB Member Wiki gives your members Wikipedia-style collaborative editing, built into your site. Every edit is versioned. Every page is searchable. Members can watch pages and get email notifications when content changes. You control who can read, create, and edit through standard WordPress roles and permissions.
v1.1.0 shipped this week with some features I’m particularly excited about:
Three migration importers
The single biggest barrier to adopting a new knowledge base tool is the migration. You have years of documentation somewhere and rebuilding it manually isn’t realistic. v1.1.0 ships importers for the three most common sources:
- MediaWiki XML, full export with page structure and internal links preserved
- Notion Markdown ZIP, export your workspace, upload the ZIP, pages come in with their hierarchy intact
- Confluence HTML ZIP, migrate without reconstructing page by page
Also in v1.1.0: WPML and Polylang support, a helpfulness rating widget that gives real feedback on what documentation is working, HTML watchlist email notifications, a redirect management UI, and zero-result search logging. That last one is my favourite, seeing what your members search for and don’t find is a direct content roadmap handed to you automatically.
Product page and docs: store.wbcomdesigns.com/wb-member-wiki/
How We’re Building Product Pages and Docs Now: Astro + Cloudflare Pages
This is the part I want to talk about the most, because it changes how we’ll be doing things going forward.
Both SnipShare and WB Member Wiki launched with product pages and documentation at store.wbcomdesigns.com, and these pages are not built on WordPress. They’re built with Astro, deployed to Cloudflare Pages, and auto-deploy on every push to the GitHub repository.
The performance difference is immediate. Pages load in under a second on a cold request. There’s no PHP execution, no database query, no WordPress plugin stack to get through, just pre-built HTML delivered from Cloudflare’s edge network.
How it’s structured: Each product is a single JSON file in the repo. The Astro build reads that JSON and generates the full product page, hero section, feature list, pricing table, comparison chart, FAQ, screenshots. Updating a product page means editing a JSON file and pushing. Cloudflare rebuilds and redeploys automatically, usually in under a minute.
Checkout still flows through Easy Digital Downloads on wbcomdesigns.com. The Astro pages link directly to EDD’s add-to-cart URLs, so all payment processing, license management, and customer infrastructure stays exactly where it is. We get the performance win on the discovery side, where it matters for conversions, without touching commerce.
Docs follow the same pattern: Astro/MDX files in the same repository, building alongside the product pages, deploying to the same Cloudflare Pages project.
We’re planning to migrate all Wbcom product landing pages and documentation to this stack. Every product page, every docs site. The two new plugins are the first to launch this way and the rest of the catalog will follow. I’ve made plenty of mistakes building WordPress products over the years, slow product pages and docs buried in WordPress were two of the persistent ones. The Astro approach fixes both cleanly.
What I’m Building Next: WPMediaVerse
I’ve been working on something new for a while and this feels like the right moment to share it publicly for the first time.
It’s called WPMediaVerse. It’s going to be a free plugin. And it’s filling a gap that has existed in the BuddyPress ecosystem for too long.
The gap: there’s no modern, well-built media plugin for BuddyPress communities built with the current WordPress stack. The options that exist were built years ago. They don’t use the block editor. They don’t have a proper REST API. They weren’t designed for the social layer that community media actually needs. Media sharing on BuddyPress has been an afterthought for years, and it shows.
WPMediaVerse is being built from scratch with the tools WordPress developers use in 2026:
- 8 Gutenberg blocks, media grid, single media viewer, album, playlist, stories, upload form, lightbox, and lock overlay for gated content
- 40+ REST API endpoints, complete API coverage built in from the start, not added as an afterthought
- BuddyPress integration that’s native, not bolted on, when BuddyPress is active, members automatically get a Media tab on their profile, groups get a Media tab, uploads appear in the activity stream, and the social layer, reactions, @mentions, comments, all work natively with BP
Media organisation: Albums with drag-to-reorder and cover images. Playlists for audio with sequential playback. Smart Collections that auto-curate based on rules, type, tag, date range, author. Instagram-style Stories with auto-cleanup via WP Cron. Full tag and category support with autocomplete.
Privacy and access control: Six levels, public, logged-in, friends-only, group-only, private, custom. Signed URLs with HMAC-SHA256 for time-limited gated media delivery. A payment bridge with hooks for Stripe and WooCommerce so you can put media behind a paywall. Lock overlay block with blurred preview for paywalled content.
Upload and storage: Drag-and-drop with MIME validation and size limits. Automatic EXIF GPS stripping for privacy. Duplicate detection via file hash. Storage driver pattern with local default, extensible to S3, BunnyCDN, or any custom driver via a filter. Files stored in wp-content/uploads/wpmediaverse/.
Social features: Six reaction types (like, love, haha, wow, sad, angry, one per user per media). Threaded comments via the WP comment system with @mention support. Favorites, share links, and per-media view, download, and reaction stats.
AI moderation: OpenAI Vision (GPT-4) for automatic content analysis and tagging. Provider abstraction via mvs_ai_providers hook so you can swap in your own model. Budget controls with monthly limits and cost-per-analysis tracking. Auto-actions, flag, hide, or reject based on moderation score. Async processing via Action Scheduler with sync fallback.
The repository is public at github.com/vapvarun/wpmediaverse. Still in active development, I’m not calling it ready yet, but if you want to follow along or contribute, the repo is open. Issues, PRs, and feedback are all welcome.
My goal with WPMediaVerse is simple: give BuddyPress communities a media platform that feels like it was built in 2026. Free, open source, built with the block editor and a proper REST API, deeply integrated with BuddyPress without requiring it.
The Bigger Picture
SnipShare, WB Member Wiki, WPMediaVerse, these three projects share a common thread. They’re all filling gaps in what WordPress communities can do natively. Code sharing. Collaborative knowledge. Modern community media. None of these had a solid WordPress-native answer before, and community site owners have been working around that for years.
The Astro store and docs infrastructure is the other piece. Faster product pages and properly maintained documentation without the overhead of WordPress for every product site. That frees up time to build more actual product instead of maintaining infrastructure.
More updates as they ship. Watch the WPMediaVerse repo if you want to follow the development in real time.
We specialize in web design & development, search engine optimization and web marketing, eCommerce, multimedia solutions, content writing, graphic and logo design. We build web solutions, which evolve with the changing needs of your business.
