What you are building
A snippet library inside the team’s internal, login-only WordPress install. Members create pastes for shell commands, config snippets, runbook procedures, regex tested against production logs - anything the team currently re-derives from Slack history every week.
The goal: a searchable archive that pays for itself the first time someone finds the right command in 30 seconds instead of grepping #ops chat for 20 minutes.
Why an intranet snippet archive beats the alternatives
What teams currently use, and what each costs:
- Slack history - searchable but ephemeral on free plans, full of context noise, no syntax highlighting, no versioning
- Confluence / Notion - good for docs, bad for code (lossy formatting, terrible for multi-file, no diff)
- GitHub Gist - great for sharing but secret gists are link-only with no team scoping, and personal accounts mix in
- Notion code blocks - no diff between versions
- Shared Google Docs - the worst of all - no syntax highlighting at all
SnipShare on a private WP install gives you syntax highlighting, multi-file pastes, revision diffs (Developer and up), and search by title, description, tag and language. All inside the team’s already-existing intranet.
How visibility works for a team
This is the part to get right first. SnipShare has three visibility levels:
- Public - listed in the
/pastes/archive and readable by anyone who can reach the site - Unlisted - readable by anyone with the link, kept out of the archive
- Private - readable only by the person who created it
There is no “share with my team” level, and no SnipShare setting that forces a login to read. So a team library works like this: put the whole site behind a login (an intranet, a membership plugin or Cloudflare Access), then use Public for the team library and Private for each person’s own scratch notes.
Setup for a private team install
- Install SnipShare on the team intranet WP install, which should already require a login for every page.
- Settings - General - set default visibility to Public if the whole site is login-only, so team pastes land in the shared archive. Members switch to Private for personal notes.
- Check who can create pastes. Any logged-in member can create pastes by default; Editors and Administrators also moderate. The Permissions tab lists the mapping read-only, and developers change it through the WordPress
user_has_capfilter. - Settings - Appearance - pick a code theme: Tomorrow, Okaidia, Twilight, Dark, Coy or Solarized Light.
- Turn off burn-after-read, password protection or expiration in the feature toggles if the team will not use them (keeps the create form simpler).
- Set up Collections - create named buckets like “Production runbook”, “DB queries”, “Deploy commands” so snippets self-organize.
Privacy posture
Keeping the library private comes down to the site, not the plugin:
- Login on every page - SnipShare lets guests read public and unlisted pastes, so the intranet itself has to block anonymous visitors
- Private for personal notes - anything one person keeps for themselves stays owner-only
- No secrets - even a private paste is plain text in the database
Pair with a private DNS + Cloudflare Access if you want zero-trust on top.
What a shared snippet library for teams is, and what it is not
A shared snippet library for teams is one searchable place where the commands, configs and queries your people keep re-deriving are written down once, named for the job they do and found by anyone on the team. It is not a wiki and it is not a code repository. A wiki holds explanations. A repository holds a project’s history. A snippet library holds the small, reusable pieces in between, and its value comes from how fast someone finds one.
That is why the first rule is a boring one: name each paste for the task, not the technology. “Rotate the staging database password” gets found. “Bash script 3” does not. Search covers the title, the description, the tags and the language, and it does not search inside the code, so the words you put in those fields are the words people will type.
Who can add and edit
Decide this before the first day. By default any logged-in member can create pastes, and Editors and Administrators also moderate. The Permissions tab lists the mapping and does not let you change it there. A developer can change who may create through the WordPress user_has_cap filter if your team needs a narrower rule.
For most teams the default is right. A library people cannot add to stays empty, and a library with no owner fills with duplicates. Name one person who tidies it each quarter, and let everyone else add freely.
Fork instead of overwrite
When a snippet is nearly right for a different system, a team member can fork it, which makes their own copy to change. That keeps the original intact for the people who depend on it, and the fork shows where an improvement came from. Stars work as a quiet vote: the paste people star is the one that saved them time, and it is worth keeping near the top of a collection.
If you are on the Developer tier or above, the revision history with diffs shows how a paste changed and who changed it. That is the feature that makes a shared library safe to edit, because a bad change can be seen and undone. On the entry tier, agree that a paste is edited only by its author and forked by everyone else.
How should the library be organised?
Collections do most of the work, and they are in the entry tier. A useful pattern is one collection per system and one for each recurring situation: an on-call collection with the commands an on-call engineer needs at three in the morning, a collection for each service, and one for the first week of a new hire.
Tags handle the cross-cutting questions. Use a short fixed list, such as the name of the tool or the environment, and write it down where the team will see it. Tags that anyone can invent turn into five spellings of the same word within a month.
Keep descriptions to two sentences: what the snippet does and when to use it. A description that explains the whole system belongs in your docs, with a link.
A first-week plan
A library only works if it is useful on the first day, so plan the first week.
On day one, install it, set the default visibility and put the site behind a login. Test it logged out. On day two, seed thirty to fifty snippets yourself from the places your team already goes for answers, and put each in the right collection. On day three, write the naming convention and the tag list on one page and pin it in your chat tool.
On day four, ask each team member to add one snippet they used that week. Keep the bar low: a title, a two-sentence description and the code. On day five, run one real search together, for something a person actually needed, and see whether the right paste comes up. If it does not, fix the title and tags, because that is how the team learns what makes a paste findable.
After that week, the habit is simple. When someone answers a question with a command, the answer goes into the library and the link goes back to the thread.
What to keep out of the library
A snippet library is plain text in your database. Do not store passwords, tokens or keys in it, even in private pastes. Store the command that fetches a secret from your secrets manager instead, and the paste stays useful without becoming a risk. If a snippet contains a value that was rotated, edit it or delete it, and put the cleanup on the calendar so it happens.
The library is only as private as the site around it. SnipShare lets guests read public and unlisted pastes, so the intranet must block anonymous visitors. Test it logged out after any hosting or DNS change.
How does it fit beside what you already use?
Keep the tools that do their own jobs well. Your chat tool is for conversation, your docs are for explanation and your repository is for projects. The library is for the pieces people copy. When someone answers a question in chat with a useful command, the habit that makes the library work is “I’ll put that in the library”, with a link back in the thread.
If you are comparing this with a local snippet manager app, the post on a snippet manager app or a shared library sets out when each fits. For a one-person setup, see the solo developer notebook, and for the wider overview of sharing code on your own domain, the code snippet sharing page.
Common snippet categories worth seeding
Seed the archive yourself before the team starts using it. A library with 50 pre-loaded snippets feels useful on day 1. With 0 snippets it feels abandoned.
Useful seed categories:
- Deploy + rollback commands - the actual commands your team runs
- Database queries - the actual SELECTs ops runs to investigate issues
- Production debug - the actual incantations for tail-ing logs, checking queue depth, etc.
- Config snippets - the WAF rules, nginx blocks, redis configs you typically edit
- Onboarding commands - the dev environment setup steps for new joiners
- Test data - the seed SQL or curl requests that get a feature to a testable state
- Regex catalog - the regexes your team has spent time deriving + verifying
By the time you finish seeding, you have already used the tool more than most teams do in a month.
Collections, the feature that makes it an archive
Individual pastes are useful on their own, but for a team it is collections that turn a pile of them into something you can navigate. A collection is a named bucket of pastes, and it is in the entry tier rather than an upgrade.
Useful collection patterns:
- One per major system - “API service”, “Worker queue”, “Admin dashboard”
- One per oncall rotation - “Oncall runbook” with every command + check oncall actually needs
- One per common bug - “Production debug - Redis OOM” - so the next person who hits it finds the solution in 1 search
- One per onboarding role - “Backend engineer - first week”
Members can have their own Collections too (personal scratchpad). Make shared collections public on the login-only site and keep personal ones private.
Common pitfalls
- No seed content. Team members never adopt a tool that feels empty on day 1. Seed 30-50 snippets minimum.
- Relying on the plugin for privacy. If the intranet ever becomes accidentally public (DNS misconfig, etc.), public and unlisted pastes are readable. Keep the site-wide login in place and check it after every hosting change.
- Defaulting team pastes to Private. Private means only the author can read it, so the rest of the team never sees it.
- Vague titles. Search covers titles and descriptions, not the code itself. Name every paste for the task it does.
- Skipping Collections. Without them, the archive feels like a wall of pastes after the 100th entry.
- No deletion policy. Some snippets reference passwords or secrets that were rotated. Set a quarterly cleanup ritual.
When SnipShare fails for team intranets
If you need:
- Inline execution of code (run a snippet to test) - this is Replit / CodeSandbox territory, not SnipShare
- Strict secrets management (passwords + tokens) - this is 1Password / Bitwarden territory
- Full Git history with branching + PRs - this is GitHub / GitLab
- Pair programming - this is VS Code Live Share
SnipShare is best for read-side archival - the team’s library of “things that worked once and might work again.”
Ship checklist
- Plugin installed on a login-only team intranet
- Default visibility chosen (Public for the shared library, Private for personal notes)
- Logged-out visit tested: the archive and a paste URL should both hit the login wall
- 30-50 seed pastes loaded by an admin
- Collections configured per major system / process
- Search verified - “find a command by typing 3 words of its title”
- Quarterly cleanup ritual added to the team calendar
Then start asking the team to add their own. Adoption follows the first useful query someone runs that saves them 20 minutes.