60 lines
2.8 KiB
Markdown
60 lines
2.8 KiB
Markdown
# 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]."*
|