Skip to content
TabREM
← All case studies
Headless CMS + publishingCase 10

SecondBrain

A portfolio and publishing platform that runs itself

A self-publishing platform that runs a portfolio website and articles from one source of truth, with 99% of the site managed from Payload CMS.

01 / 04A portfolio and publishing platform that runs itself.

Contribution

Product architecture · full-stack engineering · CI/CD

Domain

Content publishing · headless CMS · search and discoverability

Availability

Live website and shareable CMS visuals

Overview

A self-publishing platform that runs a portfolio website and articles from one source of truth, with 99% of the site configurable from Payload CMS and every change shipped through automated CI/CD.

The problem

A professional presence goes stale when every change needs a developer. Case studies and work history get rewritten for the site, articles and profiles, hard-coded pages make edits risky to the design, and a portfolio that isn't search-ready and share-ready rarely turns visitors into conversations.

What we built

  • Owner-Managed CMS: Runs every page, case study, article, testimonial, service and menu from Payload CMS across 9 collections and 8 page settings, so 99% of the site changes without touching code.
  • Single Source of Truth: Keeps case studies and work history once and reuses them across the site, articles and profiles, while name, title and positioning set in Site Settings flow to every page, search result and social card.
  • Block-Based Brand Consistency: Assembles pages from controlled content blocks and one shared project template, so editing content can't break the design.
  • Write Once, Publish Everywhere: Powers the article page, every article list and the "Read on Medium or LinkedIn" link from a single entry, with externally published pieces in the same feed and the platform detected from the URL.
  • Drafts, Publishing & Version History: Saves drafts, publishes when ready, and rolls back any change from the version history.
  • Search & Share Ready: Gives every page metadata, Open Graph and social cards, and canonical URLs, with site-wide SEO defaults, excerpt fallbacks, slugs that lock after publishing, and required alt text on every image.
  • Built-In Conversion Paths: Places calls to action to book a call or send a message throughout the site, with enquiries landing in Contact Requests inside the CMS.
  • Automated CI/CD Releases: Builds, checks and deploys every change automatically, with no manual release steps.
  • MCP-Ready Architecture: Designed to connect AI assistants and outside sources through an MCP server as the platform grows.
Next case studyBuilding a zero-friction B2B network for connected warehouses

Have a system like this in mind?

Let’s scope it together.