One dashboard for three sites.
— Ecosystem
Anahê Canavezzi is a writer and a designer. She needed three public sites (the book, the studio and the blog) and a dashboard to manage all of it without depending on me. I built the four Next.js apps in a Turborepo and pnpm monorepo, served by a single NestJS API and a single database.
Architecture decision
I considered micro-frontends and dropped the idea: there are no multiple teams and no runtime composition. These are four sites sharing a design system, types and schemas, which is exactly what Turborepo is for.
One dashboard and one API manage the content of all three public sites.
— The story
Chapter 01Login · Dashboard
The dashboard calls the API through its own /api, so the session cookies stay on the dashboard's domain and never reach the public sites. The second login step is an emailed code or an authenticator app. The dashboard shows first-party analytics for all three sites, with no third-party scripts.
Chapter 02Posts · Editor
The editor uses Tiptap and shows the text in the same style it will have on the site (Editorial, Essay or Visual). When publishing, the question is "Where to publish": Blog or Writings.
Chapter 03Writer · Studio · Portfolio
Stores, services, steps, clients, testimonials: all follow one pattern. Search, a drag-to-sort list, a "show on site" switch and editing in a side drawer. Case studies, being longer, open a full-page editor.
Chapter 04Leads · Briefs · Media
Contacts and quotes land in Leads, on a kanban board where they're dragged between stages, and the reply to the client is written and emailed from inside the dashboard. Briefs, comments waiting for moderation and the media library of all three sites live in the same place.
Chapter 05Settings · Account
The account menu sits at the bottom of the sidebar: language (Portuguese or English), light or dark theme, and sign out. The dark theme is a warm brown, never pure black, and a guided tour introduces the dashboard the first time.