Create tasks-index system for Decap CMS task management
- New directory: docs/tasks-index/ with individual task markdown files - Each task = separate file with frontmatter (priority, status, blocker flag) - Sample tasks created: #26, #87, #94, #99 - README explains structure and relationship to full task docs Benefits for Trinity: - Decap CMS shows clean task list at firefrostgaming.com/admin - Click any task → edit just that task - Blockers auto-sort to top - Mobile-friendly individual entries - Replaces monolithic BLOCKERS.md + BACKLOG.md files in UI Next: Update Decap CMS config to point at tasks-index folder
This commit is contained in:
60
docs/tasks-index/README.md
Normal file
60
docs/tasks-index/README.md
Normal file
@@ -0,0 +1,60 @@
|
||||
# Tasks Index — Decap CMS Task Management
|
||||
|
||||
**Purpose:** Individual task files for Decap CMS UI at firefrostgaming.com/admin
|
||||
|
||||
## Structure
|
||||
|
||||
Each task is a separate markdown file with frontmatter:
|
||||
|
||||
```markdown
|
||||
---
|
||||
task_number: 26
|
||||
title: Modpack Version Checker
|
||||
status: In Progress | Planned | Complete | Blocked
|
||||
priority: P0-Blocker | P1-High | P2-Medium | P3-Low | P4-Personal
|
||||
is_blocker: true | false
|
||||
tags:
|
||||
- category1
|
||||
- category2
|
||||
owner: Michael | Meg | Holly | Trinity
|
||||
estimated_hours: X
|
||||
---
|
||||
|
||||
# Task #26: Title
|
||||
|
||||
Brief description and notes...
|
||||
```
|
||||
|
||||
## Priority Levels
|
||||
|
||||
- **P0-Blocker** — Launch critical, blocks soft launch
|
||||
- **P1-High** — Direct revenue impact or major force multiplier
|
||||
- **P2-Medium** — Operational improvements, infrastructure hardening
|
||||
- **P3-Low** — Nice-to-have, backlog
|
||||
- **P4-Personal** — Trinity member personal projects
|
||||
|
||||
## Status Values
|
||||
|
||||
- **Planned** — Spec exists, not started
|
||||
- **In Progress** — Currently being worked on
|
||||
- **Blocked** — Waiting on external dependency
|
||||
- **Complete** — Done and deployed
|
||||
|
||||
## Relationship to Full Task Docs
|
||||
|
||||
- **This directory:** High-level task cards for Decap CMS UI
|
||||
- **docs/tasks/:** Full implementation specs, code, guides
|
||||
|
||||
Each task in this directory links to its full documentation in `docs/tasks/` for detailed implementation guidance.
|
||||
|
||||
## Decap CMS Display
|
||||
|
||||
Tasks appear in the 🔥 TASKS collection at firefrostgaming.com/admin:
|
||||
- Sorted by priority (blockers first)
|
||||
- Click to edit individual task
|
||||
- Update status, add notes, change priority
|
||||
- All changes commit to Git automatically
|
||||
|
||||
---
|
||||
|
||||
**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
|
||||
33
docs/tasks-index/task-026-modpack-version-checker.md
Normal file
33
docs/tasks-index/task-026-modpack-version-checker.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
task_number: 26
|
||||
title: Modpack Version Checker
|
||||
status: In Progress
|
||||
priority: P1-High
|
||||
is_blocker: false
|
||||
tags:
|
||||
- commercial
|
||||
- builtbybit
|
||||
- revenue
|
||||
owner: Michael
|
||||
estimated_hours: 40
|
||||
---
|
||||
|
||||
# Task #26: Modpack Version Checker
|
||||
|
||||
**Commercial product for BuiltByBit marketplace — passive income potential**
|
||||
|
||||
## Status
|
||||
Phases 1-4 complete (scaffolding, admin UI, React component, API controller). Phase 5 code written but not deployed due to Blueprint corruption.
|
||||
|
||||
## Next Steps
|
||||
1. Reinstall Blueprint on Dev Panel
|
||||
2. Deploy Phase 5 code (UpdateBadge.tsx, cron command, status route)
|
||||
3. Test at-a-glance update status on server list
|
||||
|
||||
## Full Documentation
|
||||
See: `docs/tasks/task-026-modpack-version-checker/` for complete specs and implementation details.
|
||||
|
||||
## Revenue Potential
|
||||
- Sell on BuiltByBit marketplace
|
||||
- Recurring revenue from Blueprint extension
|
||||
- Increases Firefrost credibility in Minecraft hosting space
|
||||
33
docs/tasks-index/task-087-arbiter-lifecycle-handlers.md
Normal file
33
docs/tasks-index/task-087-arbiter-lifecycle-handlers.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
task_number: 87
|
||||
title: Arbiter Lifecycle Handlers
|
||||
status: Complete
|
||||
priority: P0-Blocker
|
||||
is_blocker: true
|
||||
tags:
|
||||
- arbiter
|
||||
- payments
|
||||
- launch-critical
|
||||
owner: Michael
|
||||
estimated_hours: 8
|
||||
completed_date: 2026-04-06
|
||||
---
|
||||
|
||||
# Task #87: Arbiter Lifecycle Handlers
|
||||
|
||||
**LAUNCH BLOCKER — Payment lifecycle management**
|
||||
|
||||
## Status
|
||||
✅ **COMPLETE** (April 6, 2026)
|
||||
|
||||
## What Was Implemented
|
||||
- Discord role sync on new subscriptions
|
||||
- Grace period handling (3 days) on cancellation
|
||||
- Automatic downgrade to Awakened when grace expires (hourly cron)
|
||||
- Chargeback = immediate ban + role removal
|
||||
|
||||
## Philosophy
|
||||
"We Don't Kick People Out" — Expired grace period converts to permanent Awakened tier instead of full removal.
|
||||
|
||||
## Full Documentation
|
||||
See: `docs/tasks/arbiter-2-1-cancellation-flow/` for implementation details.
|
||||
35
docs/tasks-index/task-094-global-restart-scheduler.md
Normal file
35
docs/tasks-index/task-094-global-restart-scheduler.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
task_number: 94
|
||||
title: Global Restart Scheduler
|
||||
status: Planned
|
||||
priority: P1-High
|
||||
is_blocker: false
|
||||
tags:
|
||||
- automation
|
||||
- pterodactyl
|
||||
- operations
|
||||
owner: Michael
|
||||
estimated_hours: 12
|
||||
---
|
||||
|
||||
# Task #94: Global Restart Scheduler
|
||||
|
||||
**Reduce manual server restart work with automated scheduling**
|
||||
|
||||
## Overview
|
||||
680-line complete specification exists for a centralized restart scheduling system with drag-and-drop interface.
|
||||
|
||||
## Features
|
||||
- Database schema designed
|
||||
- Express routes planned
|
||||
- EJS/HTMX templates specified
|
||||
- SortableJS drag-and-drop interface
|
||||
- Pterodactyl API sync with rate limiting
|
||||
|
||||
## Why It Matters
|
||||
- Saves hours per week on manual restart coordination
|
||||
- Prevents server drift and memory leaks
|
||||
- Professional appearance (scheduled maintenance)
|
||||
|
||||
## Full Documentation
|
||||
See: `docs/tasks/task-094-global-restart-scheduler/` for complete 680-line specification.
|
||||
37
docs/tasks-index/task-099-claude-projects-architecture.md
Normal file
37
docs/tasks-index/task-099-claude-projects-architecture.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
task_number: 99
|
||||
title: Claude Projects Architecture
|
||||
status: Planned
|
||||
priority: P1-High
|
||||
is_blocker: false
|
||||
tags:
|
||||
- claude
|
||||
- infrastructure
|
||||
- documentation
|
||||
owner: Michael
|
||||
estimated_hours: 3
|
||||
---
|
||||
|
||||
# Task #99: Claude Projects Setup
|
||||
|
||||
**Separate Claude Projects for Dev/Ops/Marketing to prevent context bloat**
|
||||
|
||||
## Overview
|
||||
Create 3 separate Claude Projects with Master Documents in Project Knowledge to optimize token usage and prevent context bleeding.
|
||||
|
||||
## Projects Structure
|
||||
1. **Firefrost Dev** — Coding, MVC, Arbiter (Master Docs: ModpackChecker-State, Arbiter-Architecture, Dev-Environment, Trinity-Console)
|
||||
2. **Firefrost Ops** — Operations, handoffs (Master Docs: Current-State, Infrastructure-Manifest, Active-Tasks, Standards-Reference)
|
||||
3. **Firefrost Marketing** — Brand, social, FOMO (Master Docs: Brand-Guidelines, FOMO-Campaign, Social-Platforms, Subscription-Tiers)
|
||||
|
||||
## Benefits
|
||||
- Prevents context bloat (Dev code doesn't contaminate Marketing prompts)
|
||||
- Micro-session workflow (new chat per task)
|
||||
- Optimized token usage
|
||||
- Cleaner handoffs between sessions
|
||||
|
||||
## Full Documentation
|
||||
See: `docs/tasks/task-099-claude-projects-architecture.md` for complete implementation guide.
|
||||
|
||||
## Time Estimate
|
||||
2-3 hours browser work (no SSH needed)
|
||||
Reference in New Issue
Block a user