Run a personal code notebook on your own WordPress site

What you are building

A private, searchable code-snippet notebook on your own domain. For the curl commands you keep re-discovering, the regex you spent 40 minutes crafting last quarter, the docker-compose configs that finally worked, the wp-cli incantations specific to your client sites.

A solo dev who keeps re-googling the same Stack Overflow answer is paying compound time interest on un-archived knowledge. SnipShare on a personal site fixes that.

Why this beats a ~/notes/ folder

Most solo devs have one of these:

• A ~/notes/ folder with git.sh, docker.sh, wp-cli.sh files - searchable via grep, but no syntax highlighting, no diffs, no shared link
• A Notion or Obsidian vault - good for prose, lossy for code, no tag-based search optimized for snippets
• A pile of GitHub Gists - good but mixes personal + professional, lives in someone else’s product
• Slack DMs to self - searchable for 90 days on free tier, then gone
• Browser bookmarks to Stack Overflow - works until the answer gets edited or the page redirects

SnipShare on a private WP install gives you:

• Syntax highlighting for 20+ languages
• Multi-file pastes (perfect for “remember this docker-compose + .env combo”)
• Tag-based browse (/pastes/tag/wp-cli/)
• Full-text search across all your pastes
• Revision history (your snippet evolves, you keep all versions)
• Shareable links when you want to send a peer one
• Lives on your own domain - same DNS as your site

The 5-minute setup

1. Install SnipShare on your personal WP site (or spin up a dedicated notes.yourname.com install).
2. Settings - Permissions - lock down:
   • Default visibility: Private
   • Public archive: disabled
   • Search indexing: off
3. Pick syntax theme that matches your editor. JetBrains Mono + One Dark feels familiar to most devs.
4. Bookmark /pastes/create/ - or assign it a browser keyboard shortcut.
5. Optionally add a wp-cli helper to your shell:

   alias snip='open https://notes.yourname.com/pastes/create/'

   Now snip from anywhere opens your snippet creator.

What to actually store

Things solo devs keep re-deriving:

• wp-cli commands for specific operations on specific client sites
• MySQL queries for finding orphaned posts, broken meta, etc.
• curl + API request templates for the services you frequently test
• regex patterns that took multiple iterations to get right
• bash one-liners for log parsing, file conversion, etc.
• docker-compose snippets for local dev environments
• nginx + .htaccess rules that solved a specific problem
• GitHub Actions workflow YAML you copy across projects
• brew install lists for new machine setup
• JSON Schema definitions for APIs you work with

If you have re-derived the same thing twice, paste it. Future-you will thank present-you.

Tag strategy for a personal notebook

Tags matter because search-by-tag is the fastest retrieval path. Useful patterns:

• Tool tag - wp-cli, docker, nginx, curl, ssh
• Action tag - migrate, debug, seed, deploy
• Client tag - client-acme, client-foo (private; never share)
• Status tag - tested-prod, untested, deprecated

A tagged paste is found in 5 seconds. An untagged paste is found by full-text search in 30 seconds. Both work, but the habit of tagging compounds.

Collections vs tags

Use tags for cross-cutting concerns (the same snippet applies to multiple categories). Use Collections (Pro) for one-shot organization.

Examples:

• wp-cli as a tag (applies to dozens of pastes)
• “January 2026 client work” as a Collection (a finite set of related pastes from one project)
• “My VS Code config” as a Collection (one bundle, edited over time)

If you only ever use one organization mode, use tags.

Backup + portability

Your snippets are valuable IP. Back them up.

Options:

• WP database backup covers all SnipShare data (pastes are stored in custom tables). Use any standard WP backup plugin or WP-CLI db export.
• REST API export - GET /wp-json/snipshare/v1/pastes?author=me&per_page=100 returns paginated JSON. Script a daily export.
• WP-CLI command - SnipShare ships wp snipshare export --user=me --format=json (Pro feature). Cron it to a private Git repo for versioned offsite backup.
• Single paste export - any paste can be downloaded as ZIP from the paste detail page.

Common pitfalls

• Default visibility set to Public - personal notes leak to the public archive + Google. Always Private by default.
• No tag discipline early on - tagging starts late = no retrieval value. Tag every paste as you create it.
• Storing secrets in pastes - even private pastes go to your WP database. Don’t paste production passwords or tokens. Use a real secret manager.
• No backup ritual - the snippets are valuable + portable. Back them up monthly minimum.
• Forgetting the URL - bookmark /pastes/ archive + /pastes/create/. Speed of access determines whether you actually use it.

When SnipShare is wrong as a notebook

It is wrong if you want:

• Rich prose alongside code - use Obsidian or Notion; SnipShare is code-first
• Linked notes / graph view - SnipShare is flat; use Obsidian for backlinks
• Diagrams + images alongside code - SnipShare does not embed images; use your blog or Notion
• Mobile-first capture - SnipShare works on mobile but the creation flow is desktop-optimized; if mobile capture matters more, use Drafts or Apple Notes

For code-first archival on a domain you own, SnipShare is right.

Ship checklist

• Plugin installed on personal WP install
• Default visibility set to Private
• Public archive disabled or noindex-tagged
• Syntax theme matched to your editor
• /pastes/create/ bookmarked or shortcutted
• First 10 snippets pasted (the ones you keep re-deriving)
• Tag taxonomy decided + applied to first batch
• Backup ritual scheduled (monthly minimum)

Then start pasting every time you solve something twice. The library compounds.