resolved
Vercel
vercel.com/
landed in 38msBookSlash for Vercel · Engineering
Vercel projects accumulate URLs fast: the production deploy, the latest preview, the env settings, the analytics dashboard. BookSlash gives each one a name your whole team agrees on, so design and product can reach the latest preview without an engineer pasting the URL.
resolved
Vercel
vercel.com/
landed in 38msother shortcuts you might save
Suggested slug patterns
Battle-tested shortcut conventions for Vercel, with notes on why each one survives the URL changes that break personal bookmarks.
The production app URL (canonical domain).
Ops, support, and marketing all need this. Saving it as a slug stops the recurring "what’s our production URL?" question.
The Vercel deploys dashboard.
Engineers check it after every merge; saving the URL is faster than navigating Vercel’s sidebar.
The latest preview deploy.
Designers and PMs request this constantly. b/preview always shows the latest.
Environment variables page for the production environment.
Engineering leads need it during incidents; saving it as a slug avoids the multi-click navigation.
Vercel Web Analytics dashboard.
Marketing and growth teams check it daily; engineering owns the slug.
Production runtime logs.
On-call engineers reach this during alert investigation. Pairs with b/dash (Datadog) for full coverage.
Common workflows
b/preview points at the project’s "latest preview deploy" URL, which Vercel updates automatically on every preview build. Designers and PMs reach the freshest preview without an engineer pasting the URL into Slack — the slug always shows the latest.
When an alert fires, the on-call engineer types b/prod to confirm the symptom is reproducible, then b/logs to inspect runtime errors, then b/deploy to identify the offending deployment. Three slugs, one keystroke each.
Marketing reviews b/analytics weekly. The slug points at the Vercel Web Analytics dashboard; the destination URL never changes even as the analytics view evolves.
With and without
Without shortcuts
Designers ping engineers for the preview URL after every build. Marketing keeps a stale bookmark to last quarter’s analytics page. New hires take a week to memorise which Vercel sub-domain is "production".
With BookSlash
b/prod, b/preview, b/deploy, b/env, b/analytics, b/logs. Six shortcuts, every team. Designers reach the latest preview in one keystroke; ops reaches production logs in another.
Frequently asked
It points at whichever URL you tell it to. Most teams use Vercel’s "latest preview" alias (e.g., my-project-git-main-org.vercel.app), which Vercel rotates automatically. Some teams use a per-PR convention: b/preview-pr-1234.
No — slugs are URL → URL redirects. Triggering a deploy is a Vercel CLI / API action. Most teams put a slug at the deploy hook URL (b/redeploy) so non-engineers can re-trigger known-safe rebuilds.
Namespace per project: b/prod-marketing, b/prod-app, b/prod-docs. Or use a per-team prefix: b/eng-prod, b/marketing-prod. The b/ stays constant; the segment after is the project.
Not natively today, but the BookSlash API lets you update slugs from CI. Many teams call the BookSlash API in their post-deploy step so b/preview always points at the freshest preview without manual edits.
Start with one team. Roll out when it sticks.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial