Deploy: Complete TekDek documentation website with all content pages, CSS, and infrastructure

2026-04-12 11:20:19 -04:00
parent 1be079d7a7
commit d8da25107e
29 changed files with 2627 additions and 0 deletions
--- a/publish/web1/public/content/about.md
+++ b/publish/web1/public/content/about.md
@@ -0,0 +1,82 @@
+# Vision & Strategy
+
+TekDek is a **narrative-driven content platform** that aggregates and manages developer personas across multiple channels while driving engagement through interconnected storylines and high-quality educational content.
+
+**Core thesis:** Technical education + Character-driven entertainment = sticky, differentiated community
+
+## The Three Layers
+
+### 1. Business Layer
+- **Multi-platform content management**: Track where each persona publishes (YouTube, TikTok, GitHub, personal sites, Stack Legion)
+- **Revenue model**: Membership tiers on Stack Legion, course/challenge monetization, persona-specific revenue streams
+- **Community engagement**: Member-exclusive content, challenges, gamification, cross-persona collaboration
+
+### 2. Technical Layer
+- **Stack Legion Dev site**: Central hub article-based platform (under development)
+- **Persona agents**: Each persona has their own AI agent with distinct voice/personality
+- **Content syndication**: Personas publish independently; Stack Legion aggregates and curates
+- **Persona Portal**: Publishing and management system for persona content, brands, and identity
+
+### 3. Narrative/Entertainment Layer
+- **Character arcs**: Personas are *characters* in an evolving story
+- **Conflict & drama**: Feuds, collaborations, team dynamics drive engagement
+- **Authenticity + Strategy**: Real technical knowledge + curated narrative = education that feels organic
+- **Storyline management**: Planned arcs that tie personas, content, and community together
+
+## The Persona Model
+
+### What Is a Persona?
+- Independent brand with own platform presence (YouTube, TikTok, personal site, GitHub)
+- Specialized expertise (frontend, backend, DevOps, etc.) or "learning journey" archetype
+- Distinct personality: quirks, voice, relationship dynamics with other personas
+- AI-powered agent for content generation + human curation
+- Character in a larger narrative (TekDek storyline)
+
+### Key Properties
+- **Expertise**: What they teach (PHP, React, DevOps, etc.)
+- **Voice/Tone**: How they communicate
+- **Platform Presence**: Where they publish independently
+- **Relationships**: Allies, rivals, neutral parties within TekDek
+- **Personality Consistency**: Rules for maintaining character across posts
+
+## The Narrative Engine
+
+### Storyline Management
+**Purpose**: Drive long-term engagement through character arcs, conflicts, and plot beats.
+
+**Structure**:
+- **Arcs** (3–6 month timelines): Feud between two personas, team collaboration, industry challenge
+- **Beats** (weekly/monthly): Specific conflict, resolution, or collaboration moment
+- **Content tie-ins**: Tutorial posts, rant blog posts, GitHub contributions that support the arc
+
+### Example Arc
+1. Persona A (PHP expert) and Persona B (Node expert) disagree on a best practice
+2. They each publish educational content defending their position
+3. Community sides form, challenges emerge
+4. Mid-arc: They collaborate on a comparison article (unity moment)
+5. Resolution: New "hybrid" tutorial that bridges both approaches
+
+## Target Audience & Use Cases
+
+### Primary: Stack Legion Dev (Developers)
+- **Learning**: Tutorials, code challenges, expert-led education
+- **Community**: Engage with other developers, vote on challenges, earn points
+- **Entertainment**: Follow persona storylines, watch conflicts unfold, participate in meta-drama
+
+### Secondary: Content Creators
+- **Independent publishing**: Personas manage their own platforms while leveraging Stack Legion
+- **Monetization**: Multiple revenue streams (membership share, courses, sponsorships, merchandise)
+- **Community**: Collaborate with other experts under the TekDek umbrella
+
+### Tertiary: Brands & Sponsors
+- Partner with individual personas or the Stack Legion platform for credible tech education
+
+## Replication Across Verticals
+
+The model is designed to be **replicable across industries**:
+- **Stack Legion Dev** (current): Developer education + character drama
+- **DIY/Makers**: Tutorial creators teaching carpentry, electronics, 3D printing
+- **Fitness/Wellness**: Personal trainers and nutritionists under one brand
+- **Finance**: Financial experts/advisors with distinct philosophies
+
+The core mechanics remain the same: personas, narrative arcs, community engagement, multi-platform presence.
--- a/publish/web1/public/content/decisions.md
+++ b/publish/web1/public/content/decisions.md
@@ -0,0 +1,241 @@
+# Critical Decisions Checklist
+
+## Phase 0: Foundation (NOW — Week 4)
+
+This week's decisions lock in everything needed for 12 weeks of confident execution.
+
+### 🔴 DECISION 1: Brick's Technical Specialty
+**Why**: Templates his first articles, determines his voice in depth
+
+**Status**: ⏳ **PENDING**
+
+**Options**:
+- Backend (servers, databases, APIs)
+- Frontend (React, Vue, CSS, UX)
+- DevOps (deployment, infrastructure, containerization)
+- Full-stack (end-to-end development)
+- Architecture (system design, scalability)
+- Database design (data modeling, optimization)
+
+**Action**: Pick one, finalizes his profile and content roadmap
+
+**Deadline**: This week
+
+---
+
+### 🔴 DECISION 2: Initial Persona Roster (Personas 2–10)
+**Why**: Determines content calendar, arc participants, expertise mix
+
+**Status**: ⏳ **PENDING**
+
+**What we need**:
+- 5–9 persona sketches (name, expertise, rough voice idea)
+- Real people you know, or recruit during Phase 1?
+- Mix of expertise (ensure complementary skills)
+
+**Example structure**:
+- Persona name
+- Technical specialty
+- Voice idea ("rough but relatable," "professional educator," "comedy-focused")
+- Platform presence (YouTube? Blog? GitHub?)
+
+**Deadline**: End of Week 1
+
+---
+
+### 🔴 DECISION 3: First Narrative Arc
+**Why**: Drives all content scheduling and engagement
+
+**Status**: ⏳ **PENDING**
+
+**Options**:
+- **Conflict arc**: Persona A (PHP expert) vs. Persona B (Node expert) — which is better?
+- **Learning journey arc**: New persona builds in public, learns on camera
+- **Collaboration arc**: Multiple personas team up to build something
+- **Drama arc**: Personal storyline (career change, comeback story)
+- **Other custom arc**: Your idea!
+
+**What's needed**:
+- Arc title
+- Main characters involved
+- 3–6 month timeline
+- Key beats (monthly story moments)
+- Content tie-ins (which articles support this story)
+- Engagement hooks (why will users care?)
+
+**Deadline**: End of Week 2
+
+---
+
+### 🔴 DECISION 4: Revenue Model
+**Why**: Dev team needs this to build payment processing
+
+**Status**: ⏳ **PENDING**
+
+**Decisions needed**:
+- **Membership tiers**: Free / $5/mo / $15/mo? What's included?
+- **Courses**: One-time purchase? Pricing ($29–$99)?
+- **Persona revenue share**: 70/30 split? 80/20? What cuts to TekDek?
+- **Sponsorships**: Per-article? Seasonal? Partner discounts?
+- **Challenge rewards**: Premium users only? Paid challenges?
+
+**Deadline**: End of Week 3
+
+---
+
+### 🔴 DECISION 5: Launch Target Date
+**Why**: Everything else is scheduled around this
+
+**Status**: ⏳ **PENDING**
+
+**Options**:
+- Q3 2026 (July–September)
+- Q4 2026 (October–December)
+- Early 2027 (January–March)
+- Flexible/TBD
+
+**Why it matters**: Determines sprint length, dev team roadmap, Phase 1/2/3 timing
+
+**Deadline**: End of Week 4
+
+---
+
+## Phase 1: Foundational Development (Week 5–12)
+
+### ⏸️ CHECKPOINT 6: Voice Consistency Validation (Week 8)
+**Decision**: Does Brick's voice actually work across platforms?
+
+**Why**: If not, we pivot before scaling to other personas
+
+**Validation criteria**:
+- [ ] 2–3 Brick articles published (blog, tutorial, opinion)
+- [ ] Consistent voice across platforms (blog, social media, code comments)
+- [ ] Reader feedback positive (comments, shares, engagement)
+- [ ] Technical accuracy verified
+
+**If voice works**: Proceed with personas 2–3, confident in scaling
+
+**If voice fails**: Adjust Brick profile, try different approach
+
+---
+
+### ⏸️ CHECKPOINT 7: Arc 1 Engagement (Week 10)
+**Decision**: Is the narrative arc driving user engagement?
+
+**Why**: If not, we adjust narrative strategy before Phase 2
+
+**Engagement metrics**:
+- [ ] Views per article (target: 1K+)
+- [ ] Comments per article (target: 20+)
+- [ ] User retention (target: 40%+ repeat readers)
+- [ ] Social shares (target: 100+ per major post)
+
+**If arc engages**: Proceed to Phase 2 with confidence
+
+**If arc is flat**: Try different conflict, different personas, or pivot narrative strategy
+
+---
+
+### ⏸️ CHECKPOINT 8: Go/No-Go for Phase 2 (Week 12)
+**Decision**: Ready to launch MVP to public?
+
+**Why**: This is the major go/no-go moment for public beta
+
+**Success criteria**:
+- ✅ 3 personas with proven voice consistency
+- ✅ 8–10 quality articles published
+- ✅ Arc 1 showing engagement
+- ✅ Portal MVP complete and tested
+- ✅ APIs operational and documented
+- ✅ Content monitor tracking publications
+- ✅ Curation workflow proven
+
+**If all criteria met**: Launch Phase 2
+
+**If criteria not met**: Extend Phase 1, address gaps
+
+---
+
+## Phase 2: MVP Launch (Week 13–16)
+
+### ⏸️ CHECKPOINT 9: MVP Success Metrics (Week 16)
+**Decision**: Did MVP launch meet success criteria?
+
+**Metrics to review**:
+- [ ] 500+ registered members (target)
+- [ ] 100+ challenge participants
+- [ ] Arc 2 engagement (comments, participation)
+- [ ] Revenue conversion (50%+ to membership)
+- [ ] Site stability (99.5%+ uptime)
+
+**If metrics healthy**: Proceed to Phase 3 scale
+
+**If metrics poor**: Reassess product-market fit, gather user feedback, potentially pivot
+
+---
+
+## Phase 3: Scale & Iteration (Week 17–24)
+
+### ⏸️ CHECKPOINT 10: Vertical 2 Launch Go/No-Go (Week 21)
+**Decision**: Is DIY/Fitness/Finance vertical ready to launch?
+
+**Why**: Critical validation that replication template works
+
+**Evaluation criteria**:
+- [ ] 3–5 personas for vertical 2 onboarded
+- [ ] Voice consistency across new domain
+- [ ] First arc planned and ready
+- [ ] Portal ready for multi-vertical support
+- [ ] Marketing plan for vertical 2 launch
+
+**If template replicates well**: Proceed with vertical 2 expansion
+
+**If replication struggles**: Refine template, extend timeline, or select different vertical
+
+---
+
+## Decision Log
+
+```
+PHASE 0 (THIS WEEK)
+[ ] 1. Brick's specialty — PENDING
+[ ] 2. Initial persona roster (5–9) — PENDING
+[ ] 3. First narrative arc — PENDING
+[ ] 4. Revenue model — PENDING
+[ ] 5. Launch target date — PENDING
+
+PHASE 1
+[ ] 6. Voice consistency validation — CHECKPOINT WEEK 8
+[ ] 7. Arc 1 engagement — CHECKPOINT WEEK 10
+[ ] 8. Go/no-go for Phase 2 — CHECKPOINT WEEK 12
+
+PHASE 2
+[ ] 9. MVP success metrics — CHECKPOINT WEEK 16
+
+PHASE 3
+[ ] 10. Vertical 2 launch readiness — CHECKPOINT WEEK 21
+```
+
+---
+
+## How Decisions Flow
+
+Each decision unlocks the next phase:
+
+1. **Brick's specialty** → Determines his first content, tests voice consistency
+2. **Persona roster** → Enables arc planning, content calendar drafting
+3. **First arc** → Drives Phase 1 content production
+4. **Revenue model** → Dev team builds payment + analytics systems
+5. **Launch date** → Entire timeline cascades from this commitment
+
+**If any decision slips, all downstream work is blocked.**
+
+---
+
+## Next Step
+
+**For Glytcht**: Reply with Decisions 1–3 (Brick specialty, personas, first arc)
+
+Once locked, ParzivalTD finalizes all profiles, narrative framework, and content calendar for Phase 1 execution.
+
+**Then we're off to the races.**
--- a/publish/web1/public/content/projects.md
+++ b/publish/web1/public/content/projects.md
@@ -0,0 +1,175 @@
+# Active Projects & Roadmap
+
+## Master Roadmap
+
+TekDek operates on a phased timeline with two parallel execution tracks:
+
+| Track | Owner | Deliverable | Purpose |
+|-------|-------|-------------|---------|
+| **Development** | External Dev Team | Article publishing platform, community, APIs | Content delivery, monetization, user engagement |
+| **Management** | TekDek | Persona roster, narrative engine, content monitoring | Character operations, storyline tracking, curation |
+
+```
+Phase 0: Discovery & Planning (NOW)
+   ↓ (Week 4)
+Phase 1: Foundational Development (Week 5–12)
+   ↓ (Week 12)
+Phase 2: MVP Launch (Week 13–16)
+   ↓ (Week 16)
+Phase 3: Scale & Iteration (Week 17–24)
+   ↓ (Week 24)
+Phase 4: Expansion (Week 25+)
+```
+
+## Phase 0: Discovery & Planning (NOW)
+
+### Purpose
+Lock in product definition, persona prototypes, narrative framework, and team specifications before major development begins.
+
+### Current Deliverables
+- ✅ TekDek Strategy & Vision
+- ✅ Master Project Plan
+- ✅ Tool Requirements
+- 🔄 Persona System (Brick prototype, 5–9 additional persona sketches)
+- 🔄 Narrative Framework & First Arc Definition
+- 🔄 Decision Checkpoints & Timeline
+
+### Key Decisions This Week
+1. **Brick's Technical Specialty** — Templates his voice, determines first content
+2. **Initial Persona Roster** — 5–10 people for wave 1
+3. **First Narrative Arc** — What drives engagement in early phase
+4. **Revenue Model** — Membership tiers, course pricing, persona share %
+5. **Launch Target** — Q3? Q4 2026? Firm commitment needed
+
+## Phase 1: Foundational Development (Week 5–12)
+
+### Purpose
+Build core systems, test persona voice consistency, begin content production, establish the content/narrative feedback loop.
+
+### Management Deliverables
+- **Persona System**: Build roster tracker in OpenClaw (profile, voice guide, relationships, narrative state)
+- **Narrative System**: Arc tracker, content calendar, storyline planning tool
+- **Content Monitoring**: Track publications, engagement, voice consistency
+- **Content Production**: Publish 8–10 articles (Brick, personas 2–3)
+- **Analytics**: Arc performance metrics, voice consistency feedback
+
+### Development Deliverables
+- **Portal MVP Build**: Auth, publishing interface, article display, community features skeleton
+- **API Development**: Persona API, content sync, analytics, narrative endpoints
+- **Integration Readiness**: Test data flow between OpenClaw and Portal
+
+### Success Criteria
+- ✅ 3 personas fully onboarded with consistent voices
+- ✅ 8–10 articles published with proven quality
+- ✅ Arc 1 live and showing engagement
+- ✅ Content monitor tracking all publications
+- ✅ Portal MVP ready for Phase 2
+- ✅ APIs operational and tested
+
+## Phase 2: MVP Launch (Week 13–16)
+
+### Purpose
+Launch public beta, establish community, prove engagement model (narrative + education), gather user feedback.
+
+### Management Deliverables
+- **Persona Expansion**: Personas 4–5 fully onboarded
+- **Narrative Expansion**: Arc 1 conclusion, Arc 2 launch
+- **Content Production**: 15–20 articles across all active personas
+- **Platform Integrations**: BookStack, Gitea, social media syncing
+- **Launch Coordination**: Marketing plan, user onboarding, community guidelines
+
+### Development Deliverables
+- **Portal Beta Launch**: Public-facing Stack Legion live with articles, community, challenges
+- **User Registration**: Member tiers, gamification live
+- **Performance**: Load testing, database optimization, caching strategy
+- **API Maturity**: Versioning, rate limiting, documentation, monitoring
+
+### Success Criteria
+- ✅ Stack Legion MVP live with 5 personas, multiple articles
+- ✅ 500+ registered members, 100+ challenge participants
+- ✅ Arc 2 live and generating engagement
+- ✅ Site handles 1K+ concurrent users
+- ✅ Revenue model validated (50%+ conversion to membership/courses)
+- ✅ All APIs stable and documented
+
+## Phase 3: Scale & Iteration (Week 17–24)
+
+### Purpose
+Grow community, expand persona roster, launch multiple narrative arcs in parallel, prove replication template with second vertical.
+
+### Management Deliverables
+- **Full Wave 1 Roster**: Personas 6–10 onboarded
+- **Vertical 2 Planning**: Choose second vertical (DIY? Fitness? Finance?)
+- **Narrative Expansion**: 3–4 concurrent arcs, seasonal themes, community-driven narratives
+- **Content Production**: 40–60 articles across all personas
+- **Analytics & Growth**: Cohort analysis, content performance, SEO growth
+
+### Development Deliverables
+- **Platform Scaling**: Microservices architecture, database sharding, cache optimization
+- **Advanced Features**: Persona Portal MVP, advanced gamification, recommendation engine
+- **Revenue Systems**: Course hosting, membership tiers, payment processing, revenue sharing
+- **API Expansion**: Persona Portal APIs, recommendation APIs, revenue APIs
+
+### Success Criteria
+- ✅ 10,000+ active community members
+- ✅ 10 personas across 2 verticals
+- ✅ 150+ articles published
+- ✅ 3–4 narrative arcs generating measurable engagement
+- ✅ Monthly recurring revenue established
+- ✅ Platform handles 10K+ concurrent users
+- ✅ 50K+ monthly organic visitors (SEO)
+- ✅ Replication template proven with second vertical
+
+## Phase 4: Expansion (Week 25+)
+
+### Purpose
+Scale to 3–5 verticals, build revenue streams, establish moat through narrative depth, prepare for external partnerships.
+
+### Management Deliverables
+- **Multi-Vertical Operations**: 3–5 verticals live, 30–50 personas
+- **Narrative Complexity**: 10–15 concurrent arcs, cross-vertical storylines, annual events
+- **Monetization & Partnerships**: Sponsorships, affiliate marketing, white-label opportunities
+
+### Development Deliverables
+- **Enterprise-Grade Platform**: Advanced analytics, internationalization, white-label features
+- **API Marketplace**: Third-party integrations, ecosystem partnerships
+
+### Success Criteria
+- ✅ $50K+ monthly recurring revenue
+- ✅ 50+ personas across 3–5 verticals
+- ✅ Enterprise partnerships established
+- ✅ Replication playbook proven
+
+## Critical Success Factors
+
+### Week 1 (This Week)
+- [ ] Brick specialty finalized
+- [ ] 5 personas sketched
+- [ ] Arc 1 defined
+- [ ] Dev team aligned
+
+### Week 4 Checkpoint
+- [ ] All Phase 0 decisions locked
+- [ ] Personas documented
+- [ ] Narrative engine designed
+- [ ] Revenue model detailed
+- [ ] Launch date committed
+
+### Week 12 Checkpoint (Phase 1 Go/No-Go)
+- [ ] 3 personas with proven voice consistency
+- [ ] 8–10 quality articles published
+- [ ] Arc 1 showing engagement
+- [ ] Portal MVP complete
+- [ ] APIs operational
+
+### Week 16 Checkpoint (Phase 2 Go/No-Go)
+- [ ] Stack Legion MVP public
+- [ ] 500+ members
+- [ ] Revenue model working
+- [ ] Ready for Phase 3 scale
+
+### Week 24 Checkpoint (Phase 3 Go/No-Go)
+- [ ] 10 personas, 2 verticals
+- [ ] 10K+ users
+- [ ] Replication validated
+- [ ] Ready for Phase 4 expansion
--- a/publish/web1/public/content/tools.md
+++ b/publish/web1/public/content/tools.md
@@ -0,0 +1,174 @@
+# 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