Vivaldi setup map • Dev first

Profiles split identities.
Workspaces split modes.
Stacks split projects.

A clean browser architecture for development work. Keep your coding life segmented without turning Vivaldi into a junk drawer with a logo.

Primary profile: Dev 6 core workspaces Project based tab stacks Personal kept separate later

Profile Structure

Use profiles sparingly. They are the expensive layer.

Identity layer
Profile Purpose Accounts Notes
Dev Coding, docs, repos, AI tools GitHub, OpenAI, Claude, build tooling Main daily driver
Personal General browsing, media, shopping Personal Google and social accounts Add later, not now
Client / Admin Vendor portals, alternate org logins Separate client accounts Only if collisions appear

Core Rules

Simple rules so the setup stays useful instead of theatrical.

Operating system
  • 1 workspace = 1 mode of thinking
  • 1 stack = 1 project, bug, or objective
  • Keep active workspace count around 5 to 7
  • Keep most stacks around 3 to 8 tabs
  • Pin only permanent tools, not temporary research junk
  • Your Inbox workspace is the only approved mess
  • Hibernate or archive dormant stacks instead of hoarding them

Dev Workspaces

Click any workspace to reveal its recommended tab stacks and contents.

Interactive mockup

Use it for

  • Random links from chat, docs, or notes
  • Temporary searches and rough comparisons
  • Tabs you have not triaged yet

Rule

  • Empty daily or weekly
  • Move real work into a proper workspace fast

Prompt Lab

  • Local app
  • Repo
  • Issues or roadmap
  • Test page or current branch target

Trailkeeper

  • Live site
  • Repo
  • API docs
  • UI notes

Garden OS

  • Planner page
  • Repo
  • Scoring or content docs

NotionWidgets

  • Widget repo
  • Live demo
  • Launch docs

JS / HTML / CSS Docs

  • MDN
  • Specs
  • Framework or API references

UI Inspiration

  • Competitor products
  • Patterns worth stealing tastefully

Reading Queue

  • Longform docs
  • Articles you actually plan to finish

Current Bug

  • Failing page
  • Issue thread
  • Relevant docs

Test Environments

  • Staging
  • Local dev
  • Variant repro cases

Fix Verification

  • Post fix checks
  • Regression references

ChatGPT

  • Active working chats
  • Reference threads

Claude

  • Coding and planning flows

Prompt Library

  • Saved prompts
  • Templates and experiments

Model Testing

  • Playgrounds
  • API comparisons

GitHub Control

  • Repos
  • PRs
  • Actions or release notes

Hosting

  • GitHub Pages
  • Netlify or other deployment surfaces

Domains / DNS

  • Registrar tools
  • Records and verification flows

Analytics

  • Traffic checks
  • Release validation

Holding Zone

  • Paused projects worth reopening later
  • Older research worth keeping around
  • Candidate tabs for hibernation or session saves

Pinned Tabs

Pin only the stuff you want on nearly every workday.

Low count only
Tool Why it earns a pin
GitHub Dashboard Fast repo and PR navigation
ChatGPT Core writing and planning assistant
Claude Coding and architecture support
MDN Reliable front end reference
Deploy Surface Quick release validation

Rollout Plan

Start lean, then harden the setup once it proves useful.

Adoption path
Phase Action
Phase 1 Create the Dev profile and core workspaces
Phase 2 Create stacks for Prompt Lab, Trailkeeper, Garden OS, and NotionWidgets
Phase 3 Move research, bug, and deploy tabs into their homes
Phase 4 Add a Personal profile only if account overlap becomes annoying

Decision Framework

Use this when you are not sure what organizational layer a tab belongs to.

Fast triage

Use a Profile

  • Different login needed
  • Different extension set
  • Hard separation desired

Use a Workspace

  • Same accounts, different mode
  • Build vs research vs debug
  • You need mental context separation

Use a Tab Stack

  • One project or bug
  • One objective with a few related tabs
  • One group inside a workspace

This mockup is structured to act like a lightweight reference dashboard. It can easily be turned into a printable one pager, a Notion embed, or a richer browser setup guide later.