Skip to content
SlashSnip
Back to documentation

Operations

Site Settings: Customize Triggers Per Website

Learn how to tune SlashSnip trigger behavior for specific sites and editors — enable alias triggers where slash typing is awkward.

Published March 14, 2026Updated March 14, 2026

Why site settings matter

Not every editor behaves the same way. The practical value of SlashSnip comes from adapting to the websites you actually use.

Good uses for site settings

  • Enable alias triggers on problem surfaces.
  • Keep your main trigger path consistent elsewhere.
  • Verify critical workflows after changing settings.

Suggested workflow

  1. Pick your top three sites.
  2. Test direct insert and menu flow on each one.
  3. If slash triggers are awkward, enable aliases only for that environment.

Documentation rule

When a site-specific behavior changes, update both:

  • the operator docs
  • the compatibility messaging on the website

Continue the workflow

Compatibility Playbook

Verify the target surface before you standardize a workflow.

Starter Pack Article

Turn the docs into the first practical snippet bundle.

Browse related articles