f8d1210089
WHAT: - Comprehensive architectural review request for Gemini - Ghost CMS vs static/custom website decision - Analysis of current Ghost usage after Discord pivot - Timeline and cost-benefit analysis - Team workflow considerations (Meg/Holly content editing) WHY: - Re-evaluate architecture after moving access control to Discord - Ghost being used as static site host (using <10% of features) - 13 days to launch - decide now or post-launch - Michael's argument: migrate now during website cleanup phase - RV operation constraint favors simpler architecture QUESTIONS FOR GEMINI: 1. Is Ghost still the right tool for static marketing pages? 2. Migrate now (pre-launch) or later (post-launch)? 3. Platform recommendation (Hugo, Jekyll, 11ty, plain HTML, custom) 4. Content editing workflow for non-technical team members 5. Migration time estimate reality check (1-2 hours feasible?) 6. Hidden Ghost value we might be missing 7. Cost-benefit over 5 years 8. Does this violate 'ship, then build' principle? CONTEXT: - All 7 Ghost pages documented in Git (backup complete) - Homepage cleanup needed anyway (remove blog, subscribe forms) - Michael: 'Why clean Ghost pages we'll throw away later?' - Could do cleanup + migration in one 2-hour pass - RV vision: simpler = better for remote management STATUS: Ready to send to Gemini for architectural review Signed-off-by: Chronicler #55 <claude@firefrostgaming.com>
🔥❄️ Firefrost Gaming — Operations Manual
Document ID: FFG-ROOT-001
Version: 2.0
Last Updated: February 12, 2026
Status: 🟢 CURRENT
What This Is
The complete operational repository for Firefrost Gaming — a subscription-based Minecraft server network built on the philosophy of Fire + Frost = Where Passion Meets Precision.
This repository contains infrastructure documentation, deployment guides, planning documents, branding assets, consultant archives, and the relationship context that makes Firefrost more than just servers.
Current Infrastructure
6 Servers — 2 dedicated (Dallas, Charlotte) + 4 VPS (Dallas, Charlotte, Chicago x2)
12 Game Servers — 6 on TX1 (Dallas), 6 on NC1 (Charlotte)
8 Management Services — Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js (Subscribers), Wiki.js (Staff)
Repository Structure
├── docs/core/ — Critical living documents (scope, manifest, tasks)
├── docs/relationship/ — Partnership context, consultants, legacy
├── docs/deployment/ — Service deployment guides
├── docs/planning/ — Strategy, design, roadmap, ideas backlog
├── docs/reference/ — Technical reference, architecture decisions
├── docs/external/ — Provider communications, friend assistance
├── docs/sandbox/ — Brainstorming sessions (Gemini, Claude)
├── docs/archive/ — Historical session logs and completed plans
├── automation/ — Deployment automation system
├── branding/ — Logos, backgrounds, visual assets
├── photos/ — Consultant photo archive (249 photos by year)
└── web/ — Nginx configurations
Key Documents
Start here: SESSION-HANDOFF-PROTOCOL.md → DOCUMENT-INDEX.md
For current server inventory, see docs/core/infrastructure-manifest.md (FFG-CORE-002).
For project scope and roadmap, see docs/core/project-scope.md (FFG-CORE-001).
The Team
- Michael "Frostystyle" Krause — Owner/Operator, Technical Lead (The Wizard)
- Meg "Gingerfury" — Community Manager (The Emissary)
- The Five Consultants — Jack, Oscar, Jasmine, Butter, Noir (They're family, not pets)
Document Standards
All documents follow FFG-STD-001 — the Firefrost Revision Control Standard. See docs/core/revision-control-standard.md.
Maintained By: The Wizard & The Chronicler
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-08 | Michael + Claude | Initial | Basic Phase 0 readme |
| 2.0 | 2026-02-12 | The Chronicler | Rewrite | Complete rewrite reflecting current state (8 services, 6 servers, 12 game servers). Updated repo structure. Applied FFG-STD-001. |