Site Settings: Customize Triggers Per Website

Use site settings when one editor behaves differently from the rest of your browser workflow; keep the default trigger path everywhere else.

Why do 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

What should you read next?

• Use the compatibility playbook to test direct insertion and the menu separately.
• Follow trigger troubleshooting before treating one editor as unsupported.