Solopreneur Content Stack Architecture

Overview

  • Project: Unified Content Pipeline
  • Status: Adopted — “Markdown-First” stack
  • Principle: One input (Obsidian/Markdown), multiple outputs (Web, Slides, Video)

Stack Decisions

ToolVerdictRole
ObsidianRETAINSingle source of truth — CMS
QuartzRETAINWeb output — static blog/knowledge site
MarpRETAINPresentation output — version-controlled slides
RemotionADOPTVideo output — programmatic video generation
Django CMSREJECTOverkill — heavy Python backend duplicates Quartz
StrapiREJECTOverkill — API layer unnecessary for single-output sites

The Unified Content Pipeline

Tag-Driven Publishing

  1. Write consulting methodology in Obsidian
  2. Tag #public → Quartz publishes as blog post
  3. Tag #slide → Marp renders as presentation deck
  4. Tag #script → Remotion pulls text for video generation

Remotion Integration Strategy

  • Build one template (“Consulting Tip” video: Intro → 3 Bullets → Outro)
  • Feed template via JSON exported from Obsidian notes
  • Result: produce video content by writing Markdown, no video editor needed

Client Portal (Instead of Strapi/Django)

Use Quartz with password-protected folders (yoursite.com/clients/client-name). Publish deliverables (Plane updates, Peppermint summaries, PDF reports) as Markdown.

Operational Tools

ToolRoleStatus
PlaneProject managementAdopted
PeppermintTicket managementAdopted
Krayin/EspoCRMCRM (under evaluation)Evaluating
Firefly IIIPersonal finance ledgerAdopted
InvoiceNinjaClient invoicingRecommended

Brand Consistency Enhancement

Create custom Marp CSS theme matching Quartz site branding — unified identity across web presence and slide decks.