|
| 1 | +# Den Page Refresh Implementation Plan |
| 2 | + |
| 3 | +> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task. |
| 4 | +
|
| 5 | +**Goal:** Rewrite the public `/den` marketing page so a founder or team lead can understand Den in one fast scroll and take the "deploy your first worker" action. |
| 6 | + |
| 7 | +**Architecture:** Implement the refresh in the landing app that actually serves `openwork.software/den`, not in the Den control-plane service. Keep the existing nav/footer/layout primitives, replace the page body with the new hero, use-case cards, details, and pricing sections, and add a reusable carbon-window activity panel plus a small set of landing-specific style tokens and motion helpers. |
| 8 | + |
| 9 | +**Tech Stack:** Next.js app router, React, Tailwind utility classes, landing global CSS in `packages/landing/app/globals.css`, Framer Motion for staggered reveals. |
| 10 | + |
| 11 | +--- |
| 12 | + |
| 13 | +## Recommended Target |
| 14 | + |
| 15 | +The brief says the page "should be under `services/den`", but the live route is currently rendered from: |
| 16 | + |
| 17 | +- `packages/landing/app/den/page.tsx` |
| 18 | +- `packages/landing/components/landing-den.tsx` |
| 19 | + |
| 20 | +`services/den` currently serves a plain control-plane demo at `/`, not the public marketing site. Updating only `services/den` would not update `openwork.software/den` unless routing/deployment architecture also changes. |
| 21 | + |
| 22 | +## Approach Options |
| 23 | + |
| 24 | +### Option A: Update `packages/landing` only (recommended) |
| 25 | + |
| 26 | +```text |
| 27 | +Browser -> openwork.software |
| 28 | + -> packages/landing app |
| 29 | + -> /den page |
| 30 | +``` |
| 31 | + |
| 32 | +Why: |
| 33 | +- Matches the current production route. |
| 34 | +- Reuses existing nav, footer, background, chips, and page shell. |
| 35 | +- Smallest diff with the highest confidence. |
| 36 | + |
| 37 | +### Option B: Move `/den` ownership to `services/den` |
| 38 | + |
| 39 | +```text |
| 40 | +Browser -> openwork.software/den |
| 41 | + -> services/den |
| 42 | + -> marketing page + control-plane demo |
| 43 | +``` |
| 44 | + |
| 45 | +Why not: |
| 46 | +- Requires routing/deployment changes, not just page work. |
| 47 | +- Mixes marketing and control-plane demo concerns in one service. |
| 48 | +- Higher risk for no product gain. |
| 49 | + |
| 50 | +### Option C: Build shared Den page primitives used by both apps |
| 51 | + |
| 52 | +```text |
| 53 | +shared Den UI |
| 54 | + -> packages/landing /den |
| 55 | + -> services/den demo shell |
| 56 | +``` |
| 57 | + |
| 58 | +Why not: |
| 59 | +- Premature abstraction for a single landing page refresh. |
| 60 | +- Adds coordination cost between two runtimes. |
| 61 | + |
| 62 | +## Recommendation |
| 63 | + |
| 64 | +Use Option A. If the team later wants the Den service to host the same marketing content, extract shared pieces after the copy and layout settle. |
| 65 | + |
| 66 | +## Affected Files |
| 67 | + |
| 68 | +**Primary edits** |
| 69 | +- Modify: `packages/landing/components/landing-den.tsx` |
| 70 | +- Modify: `packages/landing/app/den/page.tsx` |
| 71 | +- Modify: `packages/landing/components/site-footer.tsx` |
| 72 | +- Modify: `packages/landing/app/globals.css` |
| 73 | + |
| 74 | +**Reference files** |
| 75 | +- Check: `DESIGN-LANGUAGE.md` |
| 76 | +- Check: `packages/landing/components/site-nav.tsx` |
| 77 | +- Check: `packages/landing/components/landing-home.tsx` |
| 78 | +- Check: `packages/landing/README.md` |
| 79 | + |
| 80 | +**Verification artifacts** |
| 81 | +- Create: `packages/landing/pr/screenshots/den-page-refresh/` (or the repo’s current PR artifact location for landing screenshots) |
| 82 | + |
| 83 | +--- |
| 84 | + |
| 85 | +### Task 1: Lock the real target and content model |
| 86 | + |
| 87 | +**Files:** |
| 88 | +- Check: `packages/landing/app/den/page.tsx` |
| 89 | +- Check: `packages/landing/components/landing-den.tsx` |
| 90 | +- Check: `packages/landing/components/site-footer.tsx` |
| 91 | +- Check: `DESIGN-LANGUAGE.md` |
| 92 | + |
| 93 | +**Step 1: Confirm routing assumption** |
| 94 | + |
| 95 | +Run: |
| 96 | + |
| 97 | +```bash |
| 98 | +rg -n "LandingDen|app/den/page" packages/landing -S |
| 99 | +``` |
| 100 | + |
| 101 | +Expected: `/den` resolves through `packages/landing`. |
| 102 | + |
| 103 | +**Step 2: Map the brief into concrete page sections** |
| 104 | + |
| 105 | +Create a small in-file content model in `packages/landing/components/landing-den.tsx` for: |
| 106 | +- hero trust chips |
| 107 | +- activity timeline entries |
| 108 | +- use-case cards |
| 109 | +- details grid items |
| 110 | + |
| 111 | +Keep copy literal and short. Do not introduce CMS-style abstractions. |
| 112 | + |
| 113 | +**Step 3: Commit** |
| 114 | + |
| 115 | +```bash |
| 116 | +git add packages/landing/components/landing-den.tsx |
| 117 | +git commit -m "refactor(landing): prepare den page content structure" |
| 118 | +``` |
| 119 | + |
| 120 | +--- |
| 121 | + |
| 122 | +### Task 2: Rebuild the hero around the new value prop |
| 123 | + |
| 124 | +**Files:** |
| 125 | +- Modify: `packages/landing/components/landing-den.tsx` |
| 126 | +- Check: `packages/landing/components/site-nav.tsx` |
| 127 | + |
| 128 | +**Step 1: Replace the current hero copy** |
| 129 | + |
| 130 | +Update the hero to: |
| 131 | +- keep eyebrow `OpenWork hosted` |
| 132 | +- keep heading `Swarms` |
| 133 | +- change subheading to `Always-on AI workers for your team.` |
| 134 | +- change body to the new brief copy |
| 135 | +- change CTA label to `Deploy your first worker` |
| 136 | +- change pricing line to `$50/mo per worker · Cancel anytime` |
| 137 | +- remove the expired early-adopter line |
| 138 | + |
| 139 | +**Step 2: Add trust chips below the CTA** |
| 140 | + |
| 141 | +Render four chips: |
| 142 | +- `YC backed` |
| 143 | +- `11.5K stars` |
| 144 | +- `Open source` |
| 145 | +- `50+ LLMs` |
| 146 | + |
| 147 | +Use the existing chip/shell styling instead of inventing a new component. |
| 148 | + |
| 149 | +**Step 3: Convert the hero layout to a two-column grid** |
| 150 | + |
| 151 | +Use a layout equivalent to: |
| 152 | + |
| 153 | +```text |
| 154 | +| left: copy + CTA + trust chips | right: carbon worker activity panel | |
| 155 | +``` |
| 156 | + |
| 157 | +On mobile, stack the carbon panel below the copy. |
| 158 | + |
| 159 | +**Step 4: Commit** |
| 160 | + |
| 161 | +```bash |
| 162 | +git add packages/landing/components/landing-den.tsx |
| 163 | +git commit -m "feat(landing): rebuild den hero" |
| 164 | +``` |
| 165 | + |
| 166 | +--- |
| 167 | + |
| 168 | +### Task 3: Add the carbon-window worker activity panel |
| 169 | + |
| 170 | +**Files:** |
| 171 | +- Modify: `packages/landing/components/landing-den.tsx` |
| 172 | +- Modify: `packages/landing/app/globals.css` |
| 173 | + |
| 174 | +**Step 1: Build a small presentational carbon-window block** |
| 175 | + |
| 176 | +Inside `landing-den.tsx`, add a lightweight presentational component or local JSX block for: |
| 177 | +- dark panel shell |
| 178 | +- titlebar with mac dots |
| 179 | +- worker name `ops-worker-01` |
| 180 | +- `RUNNING` status row |
| 181 | +- 5 activity entries from the brief |
| 182 | + |
| 183 | +Do not pull in unrelated shared app window code. The landing page only needs a visual panel. |
| 184 | + |
| 185 | +**Step 2: Add semantic styling hooks** |
| 186 | + |
| 187 | +Add CSS classes for: |
| 188 | +- carbon shell background `#151718` |
| 189 | +- carbon titlebar `#1d1f21` |
| 190 | +- mono timestamps |
| 191 | +- small source pills |
| 192 | +- status dots for success, warning, critical |
| 193 | +- pulsing running indicator |
| 194 | + |
| 195 | +**Step 3: Add staggered reveal motion** |
| 196 | + |
| 197 | +Use Framer Motion or CSS animation for entry fade-up with small stagger. |
| 198 | +Respect `prefers-reduced-motion` by disabling pulse/stagger in `globals.css`. |
| 199 | + |
| 200 | +**Step 4: Commit** |
| 201 | + |
| 202 | +```bash |
| 203 | +git add packages/landing/components/landing-den.tsx packages/landing/app/globals.css |
| 204 | +git commit -m "feat(landing): add den worker activity panel" |
| 205 | +``` |
| 206 | + |
| 207 | +--- |
| 208 | + |
| 209 | +### Task 4: Replace feature cards with use-case cards |
| 210 | + |
| 211 | +**Files:** |
| 212 | +- Modify: `packages/landing/components/landing-den.tsx` |
| 213 | +- Modify: `packages/landing/app/globals.css` |
| 214 | + |
| 215 | +**Step 1: Remove the current infrastructure-first feature card section** |
| 216 | + |
| 217 | +Delete: |
| 218 | +- `Hosted sandboxed workers` |
| 219 | +- `Desktop, Slack, and Telegram access` |
| 220 | +- `Skills, agents, and MCP included` |
| 221 | + |
| 222 | +**Step 2: Add three use-case cards** |
| 223 | + |
| 224 | +Render cards for: |
| 225 | +- Ops |
| 226 | +- Code |
| 227 | +- Content |
| 228 | + |
| 229 | +Each card should contain: |
| 230 | +- gradient category dot |
| 231 | +- uppercase label |
| 232 | +- short title |
| 233 | +- one-sentence description |
| 234 | +- mono detail line |
| 235 | + |
| 236 | +**Step 3: Reuse the existing frosted-card treatment** |
| 237 | + |
| 238 | +Keep: |
| 239 | +- rounded cards |
| 240 | +- hover lift |
| 241 | +- frosted shell feel |
| 242 | + |
| 243 | +Only add minimal new CSS if utility classes are not enough. |
| 244 | + |
| 245 | +**Step 4: Commit** |
| 246 | + |
| 247 | +```bash |
| 248 | +git add packages/landing/components/landing-den.tsx packages/landing/app/globals.css |
| 249 | +git commit -m "feat(landing): turn den features into use cases" |
| 250 | +``` |
| 251 | + |
| 252 | +--- |
| 253 | + |
| 254 | +### Task 5: Replace the OpenCode block with details + pricing |
| 255 | + |
| 256 | +**Files:** |
| 257 | +- Modify: `packages/landing/components/landing-den.tsx` |
| 258 | +- Modify: `packages/landing/components/site-footer.tsx` |
| 259 | + |
| 260 | +**Step 1: Replace the current lower section** |
| 261 | + |
| 262 | +Add a two-column details section: |
| 263 | + |
| 264 | +Left: |
| 265 | +- `How it works` |
| 266 | +- short paragraph from the brief |
| 267 | + |
| 268 | +Right: |
| 269 | +- 2x3 grid of short feature labels with blue arrow markers |
| 270 | + |
| 271 | +**Step 2: Add a dedicated pricing section** |
| 272 | + |
| 273 | +Centered section with: |
| 274 | +- bold `$50/month per worker.` |
| 275 | +- the human-time comparison sentence |
| 276 | +- CTA `Deploy your first worker` |
| 277 | +- subtext `No credit card to start` |
| 278 | + |
| 279 | +**Step 3: Update the footer copy** |
| 280 | + |
| 281 | +Keep the structure, but add `Backed by Y Combinator` to the copyright line. |
| 282 | +Do not move footer nav around unless needed for spacing. |
| 283 | + |
| 284 | +**Step 4: Commit** |
| 285 | + |
| 286 | +```bash |
| 287 | +git add packages/landing/components/landing-den.tsx packages/landing/components/site-footer.tsx |
| 288 | +git commit -m "feat(landing): add den details and pricing sections" |
| 289 | +``` |
| 290 | + |
| 291 | +--- |
| 292 | + |
| 293 | +### Task 6: Tighten metadata and CTA wiring |
| 294 | + |
| 295 | +**Files:** |
| 296 | +- Modify: `packages/landing/app/den/page.tsx` |
| 297 | +- Check: `packages/landing/components/landing-den.tsx` |
| 298 | + |
| 299 | +**Step 1: Update metadata description** |
| 300 | + |
| 301 | +Replace the current infrastructure description with copy aligned to the new positioning: |
| 302 | + |
| 303 | +```ts |
| 304 | +"Always-on AI workers that handle repetitive work for your team and report back in Slack, Telegram, or the desktop app." |
| 305 | +``` |
| 306 | + |
| 307 | +**Step 2: Confirm CTA destination** |
| 308 | + |
| 309 | +Keep `getStartedHref="https://app.openwork.software"` unless product wants a different checkout or onboarding URL. The brief changes the label, not necessarily the target. |
| 310 | + |
| 311 | +**Step 3: Commit** |
| 312 | + |
| 313 | +```bash |
| 314 | +git add packages/landing/app/den/page.tsx |
| 315 | +git commit -m "chore(landing): update den metadata" |
| 316 | +``` |
| 317 | + |
| 318 | +--- |
| 319 | + |
| 320 | +### Task 7: Verify the real page and capture artifacts |
| 321 | + |
| 322 | +**Files:** |
| 323 | +- Check: `packages/landing/README.md` |
| 324 | +- Create: `packages/landing/pr/screenshots/den-page-refresh/` |
| 325 | + |
| 326 | +**Step 1: Run the landing app locally** |
| 327 | + |
| 328 | +Run: |
| 329 | + |
| 330 | +```bash |
| 331 | +pnpm --filter @different-ai/openwork-landing dev |
| 332 | +``` |
| 333 | + |
| 334 | +Expected: local Next.js landing app starts successfully. |
| 335 | + |
| 336 | +**Step 2: Validate the `/den` route** |
| 337 | + |
| 338 | +Open the local landing URL in Chrome MCP and check: |
| 339 | +- desktop layout |
| 340 | +- mobile layout |
| 341 | +- hero copy readability in one viewport |
| 342 | +- carbon panel animation and reduced-motion sanity |
| 343 | +- trust chips and CTA placement |
| 344 | +- details and pricing sections fit the brief |
| 345 | +- footer line includes YC wording |
| 346 | + |
| 347 | +**Step 3: Run a production build** |
| 348 | + |
| 349 | +Run: |
| 350 | + |
| 351 | +```bash |
| 352 | +pnpm --filter @different-ai/openwork-landing build |
| 353 | +``` |
| 354 | + |
| 355 | +Expected: successful Next.js production build. |
| 356 | + |
| 357 | +**Step 4: Save screenshots** |
| 358 | + |
| 359 | +Capture at minimum: |
| 360 | +- desktop hero |
| 361 | +- desktop full page |
| 362 | +- mobile hero |
| 363 | +- mobile lower sections |
| 364 | + |
| 365 | +**Step 5: Optional service cleanup decision** |
| 366 | + |
| 367 | +Decide whether to leave `services/den/public/index.html` as the control-plane demo or move that demo to a non-root path later. Do not combine that cleanup with this marketing refresh unless there is explicit product direction. |
| 368 | + |
| 369 | +**Step 6: Commit** |
| 370 | + |
| 371 | +```bash |
| 372 | +git add packages/landing/pr/screenshots/den-page-refresh |
| 373 | +git commit -m "docs(pr): add den page verification artifacts" |
| 374 | +``` |
| 375 | + |
| 376 | +--- |
| 377 | + |
| 378 | +## Risks and Guardrails |
| 379 | + |
| 380 | +- Do not implement this in `services/den` unless the routing/deployment target changes first. |
| 381 | +- Do not over-componentize the page. One local component for the activity panel is enough. |
| 382 | +- Do not preserve the old "Powered by OpenCode" section on this page. The brief is explicit that it weakens the pitch. |
| 383 | +- Keep the page tight. Each major section should fit roughly in one viewport. |
| 384 | +- Keep motion subtle. The panel should feel alive, not noisy. |
| 385 | + |
| 386 | +## Verification Checklist |
| 387 | + |
| 388 | +- `/den` reads like a product pitch, not infra documentation. |
| 389 | +- The hero can be understood in under 10 seconds. |
| 390 | +- The CTA is specific. |
| 391 | +- Use cases are concrete and map to real team work. |
| 392 | +- Details and pricing are scannable. |
| 393 | +- Desktop and mobile both hold together. |
| 394 | +- `pnpm --filter @different-ai/openwork-landing build` passes. |
| 395 | + |
0 commit comments