resolved
Notion
notion.so/{workspace}/Team-Wiki-{page-id}
landed in 38msBookSlash for Notion · Project management
Notion writes the doc.
BookSlash takes you to it.
Notion is where teams write things down — the wiki, the roadmap, the brainstorm. BookSlash is how teams reach those pages without searching, scrolling, or guessing folder names. Type b/wiki and land instantly.
wiki
other shortcuts you might save
b/wikib/roadmapb/meeting-notesb/handbook
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Notion, with notes on why each one survives the URL changes that break personal bookmarks.
- b/wiki
The team’s primary Notion wiki landing page.
Every new hire learns this slug day one; every team member reaches it weekly.
https://www.notion.so/{workspace}/Team-Wiki-{page-id} - b/roadmap
Product or company roadmap page.
Stakeholders across the org reach it constantly.
https://www.notion.so/{workspace}/Roadmap-{page-id} - b/meeting-notes
Active meeting notes folder or template.
Replaces "did anyone capture notes?" Slack pings.
https://www.notion.so/{workspace}/Meeting-Notes-{page-id} - b/handbook
Company handbook landing page.
New hires reach it day one; managers reference it during reviews.
https://www.notion.so/{workspace}/Handbook-{page-id} - b/brainstorm
Active brainstorming page or template.
The "where do we put ideas?" question becomes "type b/brainstorm".
https://www.notion.so/{workspace}/Brainstorm-{page-id} - b/prd
PRD template or active product spec.
Product managers reach this for every new feature.
https://www.notion.so/{workspace}/PRD-Template-{page-id} - b/specs
Active engineering specs folder.
Engineering leads reach this during planning.
https://www.notion.so/{workspace}/Engineering-Specs-{page-id}
Common workflows
Three patterns that pay back in week one.
01
New-hire ramp
Day-one new hires learn three Notion slugs: b/wiki, b/handbook, b/roadmap. Replaces the 30-page onboarding doc with a board (see /use-cases/onboarding) anchored on those three URLs.
02
Roadmap update flow
b/roadmap points at the live roadmap page. PMs update the page; stakeholders reach the latest via the same slug. No re-bookmarking, no version drift.
03
Meeting notes capture
Every meeting starts with b/meeting-notes. The template is the latest team format; the slug carries through template revisions.
With and without
Same Notion. Different team experience.
Without shortcuts
New hires search Notion for the wiki for two days before someone shares the URL. Stakeholders ping PMs weekly for the roadmap link. Meeting notes scatter across personal Notion folders.
With BookSlash
b/wiki, b/roadmap, b/meeting-notes, b/handbook, b/prd, b/specs. Six slugs anchor the team’s Notion namespace. New hires productive day one.
Frequently asked
BookSlash + Notion
No — they solve different problems. Notion is for writing and organising docs; BookSlash is for reaching destinations and building shared canvases. Most teams keep both. See /vs/notion for a deeper comparison.
No — search is Notion’s job. BookSlash skips the search by giving every important Notion page a memorable name. The two layers complement each other.
Make the Notion page public (Notion → Share → Publish to web), then point a slug at the public URL. Internal-only pages require a Notion login at the destination.
Notion preserves the page ID even if the title (and URL slug) changes. The BookSlash slug points at the URL with the ID; it survives renames automatically. For folder-based shortcuts, you may need to repoint the slug after a folder restructure.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
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