A developer community on WordPress needs two places: somewhere to ask and answer, and somewhere to keep the code that comes out of the answers. Jetonomy gives you the forum. SnipShare gives you shared, forkable code snippets on your own domain. They run side by side on one site and one login, and they don’t share any code, so you connect them with a link and a clear house rule, not a setting.
That plain answer saves a lot of confusion, because a developer community fails in a specific way. People ask a good question, someone pastes the answer into a chat window or a third-party site, and a month later the link is dead. This post follows a community owner from the first week to the first year and shows where snippets belong, what to let people paste, and where each plugin stops.
Key points
- A forum holds the conversation and a snippet library holds the code. Keep them separate and link between them.
- SnipShare works with BuddyPress and bbPress. It has no integration with Jetonomy or BuddyNext that we can find in code.
- Members must be logged in to create a paste. Anyone can view a public one.
- SnipShare doesn’t scan code for secrets or malware. Your policy and your moderators do that job.
Why code and conversation should live apart
A forum thread is a poor home for code. It scrolls away, it mixes the question with six replies, and a long block of PHP wrecks the layout of a phone screen. A snippet wants a name, a language, a stable address and a way to improve without losing the old version.
Put the other way round, a snippet library is a poor place to ask a question. Nobody comments on a paste the way they reply in a thread.
So give each job its own home. The question goes in the forum, where people can answer, vote and accept a solution. The working code goes in a snippet, and the reply links to it. That small habit is what turns a forum from a pile of questions into a library people can search.
Week one: the forum
Start with the conversation, because the code comes from it.
Jetonomy runs on your own site and keeps topics and replies in its own database tables. It has four space types: Forum for threaded talk, Q&A where the asker accepts one answer, Ideas for votes on requests, and Show & Tell for short updates, which the admin labels Feed. For a developer community we’d start with one Q&A space, because a coding question has a right answer and a good community shows it. Our post on starting a forum you fully own covers the first week in detail.
Add a Show & Tell space once the first people start building things. Developers like to show what they made, and a space for it keeps those posts out of your help queue.
Don’t open all the rooms at once. A forum with one busy space beats one with five quiet ones, and the same is true here.
Week two: add the snippet library
Once people are answering questions, you’ll see the same pattern: someone writes ten lines of code in a reply, someone else asks for the full version, and the thread gets long. That’s the signal to add SnipShare.
SnipShare turns your site into a self-hosted code pastebin, much like GitHub Gists. A paste can hold several files, each with its own language, and syntax highlighting covers about 40 of them. Pastes can be forked and starred, grouped into collections and tagged by topic. The editor is CodeMirror 6 and the viewer uses Prism, and both load only on pages that need them, so your forum pages stay light.
SnipShare is sold on licences, so check the terms on the product page before you plan around it. There’s a live demo you can open first.
Install it the way our guide on going from install to first paste describes, then set three things before anyone else touches it: the maximum paste size, the maximum number of pastes per member, and the maximum files per paste. The defaults are a 100 KB total size, no per-member limit and 10 files per paste. A per-member limit of zero means unlimited, and moderators are never limited.
What to let people paste, and what to refuse
This is the part owners skip, and it’s the part that protects you. Write a short paste policy before the first member posts, and pin it in the forum.
A workable policy has four lines.
Code you wrote, or code whose licence lets you share it, is welcome. Anything copied from somewhere that forbids it is not.
Secrets never go in a paste. That means API keys, database passwords, tokens and private keys. We found no code in SnipShare that scans for them, so this is a rule people follow and moderators enforce. A visibility setting doesn’t make a leaked key safe, and our post on whether a pastebin is safe for code explains why in more detail.
Code meant to harm is out. A paste that’s an exploit with no explanation, or malware, gets reported and removed.
And personal data, real customer records or log files full of email addresses, doesn’t belong in a public paste.
Pastes have three visibility levels. Public pastes appear in listings. Unlisted pastes are reachable only by direct link. Private pastes are visible only to the author and moderators, and everyone else sees “not found”. A paste can also be locked with a password, set to burn after reading, or given an expiry anywhere from 10 minutes to a year. Burn after reading is revealed with one click, so a link preview in a chat app doesn’t use it up.
For a community, the sensible default is public for answers and unlisted for anything someone is still working on.
Reporting and moderation
You won’t read every paste, so give members a way to flag the bad ones. Turn on Content Reporting under SnipShare settings, and a logged-in member can report a paste as spam, inappropriate, malicious, copyright or other, with an optional note.
Reports land in a moderation queue under SnipShare, Moderation, with tabs for Pending, Reviewed and Dismissed. Each report shows the paste, the reporter, the reason and the actions available to you. Administrators and editors can use it by default, and it works on every licence tier.
Guests can’t create pastes. Creating one needs a logged-in account, though anyone can view a public paste. That one rule removes most drive-by spam, and it’s worth saying out loud in your policy so people know why they’re asked to sign up.
Helping people find the good snippets
A library with 400 pastes and no way to browse it is a junk drawer. SnipShare gives you three tools, and each one is a switch under Settings, General, so turn on the ones you’ll actually tend.
Tags are site-wide labels shared by every member. When someone saves a paste they type a comma-separated list such as php, wordpress, helper-functions, and the plugin turns each into a lowercase URL-safe tag, creating new ones as needed. That’s convenient and it drifts quickly. If one member writes js and another writes javascript, you’ll have two tags for one thing. Pick the names you want in your policy and tidy up now and then.
Stars are a personal bookmark. A member stars a public paste to find it again later, and the star count shows on listings. A paste with many stars is a decent signal that people found it useful, which makes the count a cheap way to spot what belongs in a pinned post.
Collections are named groups of pastes, like a playlist for code. Each member can make as many as they like, public or private. A collection can include other members’ public pastes, though not ones set to burn after reading. Its address has the form /pastes/collection/username/slug/, and renaming a collection never changes that address, so links you’ve shared keep working. As the site owner you can see and manage every member’s collections from the admin.
Put that last point to work. Create a public collection from your own account for each theme your community cares about, such as “WordPress hooks” or “Database queries”, and fill it from the best public pastes. Then link each collection from the matching forum space.
Embedding a snippet where people already read
Not everything lives in the library. A tutorial, a blog post or a pinned announcement often needs one snippet inline. SnipShare registers a [snipshare hash="..."] shortcode and an oEmbed provider, so a paste can sit in a page or post without copying the code across.
Making forks useful
Forking is what makes a snippet library feel alive. A member finds a snippet, forks it and changes it for their own case. SnipShare records the fork, and with BuddyPress active it can notify the owner when their paste is starred or forked. Our post on forking and revision history goes through the workflows where it helps, and which parts need a higher licence.
For you as the owner, the benefit is quieter. People improve each other’s code in the open, and the best versions rise because they’re starred.
Where the three plugins connect, and where they don’t
Here’s what we checked, so you don’t promise members more than they get.
SnipShare and BuddyPress connect. With BuddyPress active, a member’s profile gets a Pastes tab with their pastes and the ones they’ve starred. A public paste creates an activity entry, and private, unlisted and burn-after-read pastes never do. Stars and forks send notifications.
SnipShare and bbPress connect. A paste URL posted in a topic or reply turns into an inline code viewer, and an Insert Paste button above the reply box lists the member’s ten most recent pastes. A shortcode, [snipshare hash="..."], embeds a paste anywhere on the site.
SnipShare and Jetonomy do not connect. We searched both plugins for a reference to the other and found none. Jetonomy has its own handling of embedded links, and we haven’t tested whether a SnipShare paste URL turns into a code viewer inside a Jetonomy reply. Until you test it on your own site, share snippets in a Jetonomy thread as plain links, and don’t promise members an inline preview.
SnipShare and BuddyNext do not connect either. The profile tab and activity feed integration is for BuddyPress. BuddyNext, our newer community platform, has no SnipShare code in it. Jetonomy and the free BuddyNext plugin do work together, so a forum discussion can appear in a BuddyNext feed, but snippets won’t.
Does that make the plan weaker? Not really. A link in a reply is how developers already share code. What you lose is the preview, and what you keep is a library that belongs to you.
A first year, in order
- Week one: open a Q&A space and invite ten people who’ll answer.
- Week two: install SnipShare, set the limits and pin your paste policy.
- Month two: turn on reporting and name two moderators.
- Month three: group the best snippets into public collections by topic, and fix any tags that drifted.
- Month six: add a Show & Tell space and look at which pastes were forked most.
- Month twelve: decide whether you need BuddyPress for profiles and activity, because that’s the combination SnipShare supports.
When a hosted option is the better call
If your community is small and your code is mostly public, GitHub Gists or a hosted pastebin does the job for nothing. If nobody on your team will look after plugin updates and backups, the same applies. Self-hosting pays off when you want the snippets, the members and the conversation to live on your own domain, under your own rules, for years.
Questions people ask
Does SnipShare work with Jetonomy? They run on the same site, but there’s no integration between them that we found. Share pastes in a Jetonomy thread as links.
Can guests post snippets? No. Creating a paste needs a logged-in account. Viewing a public paste doesn’t.
Does it scan for leaked keys? Not that we found. Write a no-secrets rule and let members report anything that slips through.
Can I limit how much a member pastes? Yes. You can set a size cap, a files-per-paste cap and a pastes-per-member cap. Moderators aren’t limited.
Do I need BuddyPress? No. It’s optional. It adds a Pastes tab on profiles, activity entries and notifications.
How is SnipShare licensed? It’s sold on annual and lifetime licences, and there’s a live demo to try first. Check the product page for current terms.