From cafcd71fe52d13c8a5f335cd7a15e7c8605f86e2 Mon Sep 17 00:00:00 2001 From: Floke Date: Tue, 20 Jan 2026 11:24:17 +0000 Subject: [PATCH] feat(dashboard): add Content Engine concept and dashboard link --- content-engine/README.md | 59 ++++++++++++++++++++++++++++++++++++++++ dashboard/index.html | 10 +++++++ 2 files changed, 69 insertions(+) create mode 100644 content-engine/README.md diff --git a/content-engine/README.md b/content-engine/README.md new file mode 100644 index 00000000..1af6f97d --- /dev/null +++ b/content-engine/README.md @@ -0,0 +1,59 @@ +# Content Engine (v1.0 - MVP) + +**Status:** Planning / Initial Setup +**Date:** Jan 20, 2026 + +## 1. Vision & Purpose +The **Content Engine** acts as the execution arm ("The Mouth") for the strategies developed in the GTM Architect ("The Brain"). +It is a **Content Generation Dashboard** designed to produce high-quality, SEO-optimized, and sales-ready marketing assets. + +**Core Philosophy:** +* **SEO First:** Keywords guide the structure, not just metadata. +* **Human-in-the-Loop:** Every generated asset is a draft that invites manual refinement. +* **Context-Aware:** It inherits deep strategic knowledge (ICPs, Pain Points, Hybrid Service Logic) from the GTM Architect database. +* **Tone:** Professional, fact-based, compelling, and "slightly aggressive" (Challenger Sale). + +## 2. Architecture & Tech Stack + +### Data Layer +* **Persistence:** A dedicated SQLite database (`content_engine.db`) stores all content projects, SEO strategies, and drafts. +* **Integration:** Read-only access to `gtm_projects.db` to import strategy baselines. + +### The Stack +* **Frontend:** React (Vite + TypeScript) - Focus on "Writer UI" (Split Screen: Config vs. Editor). +* **Backend:** Python (Flask/Process-based Orchestrator) - Utilizing `helpers.py` for AI interaction. +* **Container:** Dockerized service, integrated into the existing Marketing Hub network. + +## 3. Workflow (MVP Scope: Website & SEO) + +### Phase 1: Project Setup & Import +1. Select a source project from GTM Architect (e.g., "PUMA M20"). +2. Import core data: Product Category, Hybrid Logic, Pain Points per ICP. +3. **Competitor Scan:** Optional input of competitor URLs to analyze their tone and position against it. + +### Phase 2: SEO Strategy +1. **Seed Generation:** AI suggests seed keywords based on GTM data. +2. **Expansion & Validation:** Use Google Search/Suggest (via Gemini Tools) to find real-world query patterns. +3. **Selection:** User selects Primary and Secondary Keywords. + +### Phase 3: Structure & Copy Generation +1. **Sitemap:** AI proposes a site structure (Home, Use Case Pages, Tech Specs). +2. **Section Generation:** + * **Hero:** Headline (Keyword-focused) + Subline. + * **Value Prop:** "Pain vs. Solution" (from GTM Phase 4). + * **Features:** "Feature-to-Value" (from GTM Phase 9). + * **Proof:** FAQ & Objections (from GTM Phase 6 - Battlecards). +3. **Refinement:** "Re-Roll" buttons for specific sections (e.g., "Make it punchier", "More focus on Compliance"). + +### Phase 4: Export +* Copy to Clipboard (Markdown/HTML). +* PDF Export. + +## 4. Future Modules (Post-MVP) +* **LinkedIn Matrix:** Generate posts for (Persona x Content Type). +* **Outbound Email:** Cold outreach sequences. +* **Press Kit:** Automated PR generation. + +## 5. Quick Actions ("Türen öffnen") +A dashboard feature to bypass the full project flow: +* *"Write a LinkedIn post about [Feature] for [Role]."* diff --git a/dashboard/index.html b/dashboard/index.html index 6faaa9d4..cf83d09c 100644 --- a/dashboard/index.html +++ b/dashboard/index.html @@ -153,6 +153,16 @@ Starten → + +
+ ✍️ +

Content Engine

+

+ The "Mouth" for your Strategy. Generiert SEO-Websites, LinkedIn-Posts und Mail-Sequenzen aus GTM-Daten. +

+ Starten → +
+
🤖