Back Home

ContentPlan

The content-collection problem, finally solved.

Role
Design + Engineering
Client
Double Up Digital
Year
2026

Toolkit

Next.js 16Tailwind v4ExpressSupabaseTipTap@dnd-kitmotion.dev
01
The problem

Every agency project stalls at content.

The site is designed, built, ready — and then dies for three weeks waiting on the client's About-page copy. Email threads fragment, Google Docs rot, and the project manager turns into a content cop.

ContentPlan replaces the scavenger hunt with a single shared workspace: every page, every deadline, every comment, every revision in one place.

02
Approach

Two views, one system.

Agencies see a project dashboard, hierarchical sitemap (drag to reparent), and per-page review queues. Clients see a calm, kanban-style flow with a guided page-by-page editor.

Both sides write into the same TipTap rich-text content store. Status auto-promotes from 'not started' → 'draft' the moment a client types. Comments are threaded per-page; notifications fire on every move.

01
Plan
Sitemap + scope
02
Write
Guided client editor
03
Review
Threaded notes
04
Approve
Sign-off + lock
05
Ship
Bulk export
03
Built with

Stack & infrastructure

  • Next.js 16 App Router with route groups for agency vs. client surfaces.
  • Express API with org/project/page-level RLS via Supabase helper functions.
  • TipTap rich text + @dnd-kit drag-and-drop + a custom pannable sitemap canvas.
  • Threaded comments, in-app notifications, and bulk file ZIP export.
04
Outcome

Real client engagements, ahead of schedule.

Used in production at Double Up Digital. The 'where's the content?' phase is no longer the longest part of a build.

First two engagements wrapped two weeks ahead of the prior baseline — content collection went from the longest phase to one of the shortest.
Up Next

Double Up Digital

We build modern websites for growing brands.

Continue