Back to projectsProject PDF
Publishing platform

StreamCRM

A central workspace for the content, media, and operations behind multiple publishing brands.

Publishing applicationWeb applicationNext.js · TypeScript · Supabase · Tiptap
My contribution

Application development: publishing workflows, content management, and integrations.

Preview only

The external site is currently unavailable. The case study and sample workspace remain available here.

Product walkthrough01 / 02
Editorial work, across publishing sites

Actual editorial interface rendered in an isolated preview with fictional posts and sample site names. The private application and its editorial records require authorized access.

Editorial work, across publishing sites
StreamCRM editorial workspace showing fictional posts, publishing statuses, site filters, and edit actions
A closer look at the result

One editorial list, across two sample sites.

The preview uses the application’s actual post-list component. Titles, publishing states, site assignments, and edit actions sit together so an editor can find the right work in context.

Search by post title
Find
Narrow by status or site
Filter
Open the selected post
Edit

Interface example with fictional posts and .example domains. No private editorial records or measured publishing gains are shown.

The challenge

Publishing across several websites means keeping drafts, media, SEO settings, and access rules organized without mixing up the brands.

What I built

  • A publishing workflow with a rich text editor and shared media library.
  • Site-aware content management and role-based access.
  • SEO controls and analytics visibility alongside day-to-day editorial work.

Key implementation decisions

Keep each brand’s content in context

Site-aware content and role-based access organize editorial work across separate publishing brands.

Put the publishing tools together

The editor, media library, and SEO controls live alongside the content workflow, so publishing does not depend on disconnected screens.

The result

Content and the controls around it live in one operational workspace, while each public brand retains its own website.