03/32proof of conceptWorkspace Launcher
Command Center
One signed-in front door to the marketing, comms, finance and translation workspaces.
What it solves
The marketing, comms, finance and translation workspaces each live at their own address. This gives the team one signed-in place to find and open them.
How it runs
Five steps, input to output
Goes inOne password at the login page
- 01
Sign in
The login route checks the password and sets an access cookie.
- 02
Front door
One page lists the workspaces and the tools that sit under them.
- 03
Search
A search box narrows the list of platforms.
- 04
Launch
Each card opens its live workspace.
- 05
Sign out
The logout route returns the visitor to the login page.
Comes outA launcher for the marketing, comms, finance and translation workspaces
What it does
One authed front door that launches the marketing, comms, finance and translation workspaces.
Three decisions
What shaped the build
One door, no work of its own
The launcher runs none of the workspaces. Each card links out to the live system behind it.
The cookie holds a hash, not the password
Sign-in compares the password in constant time, then sets an httpOnly cookie that carries a hash.
Live and planned are kept apart
Workspaces that exist are marked live. Departments still to come sit in a separate roadmap list.
Built with
8 parts
- Next.js
- app + routing
- React
- command interface
- Login route
- auth gate
- Drizzle ORM
- wired, schema still empty
- GSAP
- launch motion
- Tailwind CSS
- design tokens
- Vite · vinext
- sites build
- Cloudflare
- deploy target