175 lines
6.1 KiB
Markdown
Executable File
175 lines
6.1 KiB
Markdown
Executable File
# Tools & Infrastructure
|
||
|
||
## Overview
|
||
|
||
TekDek operates across multiple platforms and tools to manage personas, content, narratives, and community.
|
||
|
||
## Critical Path Tools (MVP — Phase 2)
|
||
|
||
### 1. Persona Management System
|
||
**Purpose**: Central hub for persona profiles, voice guides, platform presence tracking, and character consistency.
|
||
|
||
**Must-have features**:
|
||
- Persona profile (name, expertise, voice/tone guide, relationships)
|
||
- Platform presence tracking (which channels they publish on)
|
||
- Voice guide (how they write, speak, communicate across formats)
|
||
- Personality consistency rules (what's on-brand vs. off-brand)
|
||
- History/timeline (articles, posts, video links across all platforms)
|
||
|
||
**Status**: In design (OpenClaw-based)
|
||
|
||
### 2. Storyline & Narrative Planning Tool
|
||
**Purpose**: Track character arcs, plan narrative beats, schedule content tie-ins, and coordinate drama.
|
||
|
||
**Must-have features**:
|
||
- Arc planner (3–6 month timelines, character involvement, key beats)
|
||
- Content calendar tied to narrative (posts that support specific story moments)
|
||
- Conflict/collaboration tracker (who's involved, what's the status)
|
||
- Engagement hooks (what will drive user interest)
|
||
- Curated content log (you approve/reject content before publication)
|
||
|
||
**Status**: In design (combination of docs + dashboard)
|
||
|
||
### 3. Content Curation & Approval System
|
||
**Purpose**: Central intake for persona-generated content; review for technical accuracy, narrative fit, and voice consistency before publication.
|
||
|
||
**Must-have features**:
|
||
- Content submission form (title, draft, persona, narrative arc tie-in)
|
||
- Approval workflow (pending, approved, rejected with feedback)
|
||
- Scheduling (publish date/time, multi-platform coordination)
|
||
- Consistency check (does this match the persona's voice?)
|
||
- SEO/tagging (keywords, trending alignment)
|
||
|
||
**Status**: In design (form-based workflow)
|
||
|
||
## Phase 2 Nice-to-Have Tools
|
||
|
||
### 4. Persona Agent Framework
|
||
**Purpose**: AI agents that generate content drafts in each persona's voice.
|
||
|
||
**Must-have features**:
|
||
- Voice consistency (trained on persona's previous work)
|
||
- Topic/expertise alignment (generates appropriate content)
|
||
- Multi-format output (blog posts, social media captions, code comments)
|
||
- Draft generation (not auto-publish; requires your curation)
|
||
|
||
**Tech approach**: Fine-tuned LLM or prompt engineering with persona voice guide + examples
|
||
|
||
**Status**: Research phase (OpenClaw subagents)
|
||
|
||
### 5. Content Syndication System
|
||
**Purpose**: Pull content from persona's independent platforms (YouTube videos, blog posts, GitHub repos) into Stack Legion aggregation.
|
||
|
||
**Must-have features**:
|
||
- Feed ingestion (RSS, API, webhook)
|
||
- Metadata extraction (title, date, persona, expertise tag)
|
||
- Cross-linking (persona's site + Stack Legion)
|
||
- Attribution (credit the original source)
|
||
|
||
**Status**: Integration planning
|
||
|
||
## Phase 3+ Tools (Growth & Scale)
|
||
|
||
### 6. Persona Portal
|
||
**Purpose**: Publishing and identity management platform for personas.
|
||
|
||
**Must-have features**:
|
||
- Publishing interface (write, schedule, preview)
|
||
- Analytics dashboard (views, engagement per persona)
|
||
- Revenue tracking (integrations with YouTube, Patreon, course platforms)
|
||
- Branding tools (custom templates, fonts, colors)
|
||
- Community moderation (comments, member interactions)
|
||
|
||
**Status**: Under external development
|
||
|
||
### 7. Community & Gamification System
|
||
**Purpose**: Stack Legion member engagement through challenges, points, leaderboards.
|
||
|
||
**Must-have features**:
|
||
- Challenge creation (persona-authored coding challenges)
|
||
- Points/badges system (users earn for participation)
|
||
- Leaderboards (global, per-challenge, per-persona)
|
||
- Member-exclusive content (early access to articles, special threads)
|
||
|
||
**Status**: Part of Stack Legion development
|
||
|
||
### 8. Analytics & Growth Dashboard
|
||
**Purpose**: Track engagement, SEO, trending alignment, and narrative arc performance.
|
||
|
||
**Must-have features**:
|
||
- Persona performance (views, engagement per content)
|
||
- Narrative arc metrics (virality, user investment, discussion volume)
|
||
- SEO tracking (search rankings, traffic sources)
|
||
- Trending alignment (what's being discussed, how our content fits)
|
||
- Cohort analysis (which personas drive retention, growth)
|
||
|
||
**Status**: In planning (custom dashboard)
|
||
|
||
## TekDek Infrastructure
|
||
|
||
### Hosted Services
|
||
|
||
| Service | Domain | Purpose |
|
||
|---------|--------|---------|
|
||
| **Gitea** | `git.tekdek.dev` | Git repository hosting for all projects |
|
||
| **BookStack** | `docs.tekdek.dev` | Internal documentation wiki |
|
||
| **Stack Legion** | `web.tekdek.dev` (TBD) | Main user-facing portal |
|
||
| **This Site** | TBD | Documentation & strategy hub |
|
||
|
||
### Tech Stack (This Site)
|
||
|
||
- **PHP** (no framework — lean and intentional)
|
||
- **Markdown** for content (parsed to HTML)
|
||
- **Custom CSS** (no frameworks)
|
||
- **Vanilla JavaScript** (minimal)
|
||
|
||
### Tech Stack (Stack Legion)
|
||
|
||
- **TBD** (external development team)
|
||
- Requirements: article publishing, community, gamification, API support
|
||
|
||
## Build vs. Buy Strategy
|
||
|
||
### Build (Internal)
|
||
- Persona Management System
|
||
- Storyline Planning Tool
|
||
- Content Curation Workflow
|
||
- Persona Agent Framework (experimental)
|
||
|
||
### Buy / Integrate
|
||
- Stack Legion (external dev)
|
||
- Community & Gamification (external dev)
|
||
- Analytics (Google Analytics, Mixpanel, or custom)
|
||
- Syndication (Zapier, IFTTT, or custom API)
|
||
|
||
### Partner / Outsource
|
||
- Stack Legion Portal (external dev team)
|
||
- Video hosting (YouTube, TikTok — personas own)
|
||
- Course platform (Teachable, Udemy, or custom)
|
||
- Email/communication (SendGrid, ConvertKit, etc.)
|
||
|
||
## Immediate Next Steps
|
||
|
||
1. **Week 1**: Finalize Brick persona profile
|
||
2. **Week 1**: Create narrative arc template
|
||
3. **Week 2**: Build content curation spreadsheet/form
|
||
4. **Week 2**: Sketch 3–5 additional persona profiles
|
||
5. **Week 3**: Start persona agent prototyping
|
||
6. **Week 4**: SEO/growth strategy documentation
|
||
|
||
## API Integration Points
|
||
|
||
### Portal ↔ Management System (OpenClaw)
|
||
|
||
**Persona API**: `GET /persona/{id}`
|
||
- Returns: profile, system prompt, voice guide
|
||
|
||
**Content Sync API**: `POST /content/published`
|
||
- Sync when articles go live
|
||
|
||
**Analytics API**: `GET /analytics/article/{id}`
|
||
- Returns: engagement metrics
|
||
|
||
**Narrative API**: `GET /narrative/arc/{id}`
|
||
- Returns: arc beats, status, engagement
|