Michael Krause
8104a8fdee
Created new single source of truth: - FIREFROST-PROJECT-SCOPE-V2.md (complete vision) - Archived 13 outdated/superseded documents - Updated INDEX.md with clear navigation - Reflects current state (60% Phase 0.5, automation system) Key updates: - Three-tier documentation architecture documented - Automation system fully described - Authentication phased approach included - BookStack→MkDocs pivot captured - Clear current vs future priorities All historical docs preserved in archive for reference. Clean slate for moving forward.
3.2 KiB
🔥❄️ Firefrost Gaming Documentation Index
Last Updated: February 9, 2026 Status: Reorganized & Current Purpose: Central navigation for all Firefrost Gaming documentation
🚀 START HERE
New team members, Claude sessions, or quick reference:
THE MASTER DOCUMENT
📋 FIREFROST-PROJECT-SCOPE-V2.md ⭐
The complete technical & business vision - single source of truth
ESSENTIAL CONTEXT
- 📝 session-handoff.md - Current status for Claude
- 🤝 workflow-guide.md - How Michael & Claude work together
- 🎨 design-bible-v1.1.md - Visual identity & branding
- ⚖️ path-philosophy.md - Fire vs Frost philosophy
📚 OPERATIONAL DOCUMENTATION
Infrastructure & Deployment
- 🔧 gitea-deployment.md - Service 1/5: Git version control
- 📊 uptime-kuma-deployment.md - Service 2/5: Monitoring
- 🤖 automation/USAGE.md - Automation system guide
Business & Community
- 💰 subscription-tiers-final.md - Tier structure
- 🤝 awakened-gateway.md - The $1 handshake
- 🗑️ server-deletion-policy.md - World backup policy
Assets & Branding
- 🎨 visual-assets-guide.md - Logo, backgrounds, sprites
Relationships
- 📞 provider-communications.md - Breezehost partnership
📦 ARCHIVED DOCUMENTATION
Location: docs/archive/2026-02-09-consolidation/
Historical session summaries, superseded plans, and outdated documentation moved to archive for reference.
Archived documents:
- Session summaries (Feb 8-9, 2026)
- Old implementation plans
- Superseded task lists
- Planning documents not yet executed
- Social media planning (Meg's future domain)
When to reference archive:
- Understanding historical decisions
- Reviewing what approaches were tried
- Learning from past pivots
🎯 QUICK REFERENCE
Current Phase
Phase 0.5: Management Services (60% complete - 3/5 deployed)
What's Operational
- ✅ Gitea (git.firefrostgaming.com)
- ✅ Uptime Kuma (uptime.firefrostgaming.com)
- ✅ MkDocs Public Docs (docs.firefrostgaming.com)
- ✅ Automation System (95% reduction in manual work)
- ✅ 12 Game Servers (6 NC1, 6 TX1)
What's Deploying
- ⏳ Wiki.js Subscriber Portal (subscribers.firefrostgaming.com)
- ⏳ NextCloud Downloads (downloads.firefrostgaming.com)
- ⏳ Wiki.js Staff Portal (staff.firefrostgaming.com)
Next Priorities
- Complete three-tier documentation (today)
- Deploy Netdata analytics (this week)
- Deploy Vaultwarden passwords (this week)
- Soft launch to community (next week)
📖 DOCUMENTATION PHILOSOPHY
One source of truth: FIREFROST-PROJECT-SCOPE-V2.md Specific details: Individual deployment guides Historical context: Archive folder Future planning: Noted in Project Scope
Keep it simple. Keep it current. Keep it accessible.
Fire + Frost = Where Passion Meets Precision 🔥❄️
Last major reorganization: February 9, 2026