Issue: Task numbers showed as 'Task #:' instead of 'Task #26:'
Root cause: Config used 'task_number' but files use 'number'
Changes:
- summary: 'Task #{{number}}:' (was task_number)
- slug: task-{{number}} (was task_number)
- field name: 'number' (was 'task_number')
- blocker field: 'blocker' (was 'is_blocker')
- Added 'full_spec' field to match existing files
Now matches the actual task file structure in tasks/ folder.
Error: 'The Gitea backend does not support editorial workflow'
Editorial workflow (draft/review/publish) is a GitHub-only feature.
Gitea backend requires direct commits to master branch.
Keeping all other task improvements:
- Individual task files in docs/tasks-index/
- Priority-based sorting
- Improved field labels and hints
- Changed folder from 'docs/tasks-active' to 'docs/tasks-index'
- Updated priority values to P0-Blocker, P1-High, P2-Medium, P3-Low, P4-Personal
- Updated status values to: Planned, In Progress, Blocked, Complete
- Added Owner field (Michael, Meg, Holly, Trinity)
- Improved hints and labels for better UX
- Tasks now sort by priority (blockers first automatically)
Result: Individual task cards at firefrostgaming.com/admin instead of monolithic files
- Changed TASKS collection from 'files' to 'folder' type
- Points at docs/tasks-active/ for individual task files
- Each task shows as separate entry in CMS
- Sortable by priority, status, task number
- Filterable: blockers, high priority, in progress
- Summary shows: Title (P# BLOCKER if applicable)
Fields Added:
- task_number (required, integer)
- title, priority, status, is_blocker
- tags, estimated_hours, completed_date, blocked_by
- body (markdown for task details)
UI Improvements:
- Blockers sort to top automatically
- Click task → edit just that task
- Mobile-friendly (individual entries vs giant files)
- Links to full specs in /docs/tasks/ preserved
Replaces:
- Old: Two files (BLOCKERS.md, BACKLOG.md)
- New: Individual task files in /docs/tasks-active/
- Keep editorial_workflow enabled (draft/review/publish)
- Revert preview: true back to preview: false
- Dark mode causes font/background color issues in preview pane
- Editorial workflow still functional without preview
Issue: Preview pane has unresolvable dark mode styling conflicts
- Added publish_mode: editorial_workflow for draft/review/publish workflow
- Enabled preview pane (changed from false to true) for better markdown editing
- Meg and Holly can now save drafts without immediate publish
- Preview lets editors see formatted content while editing
Benefits:
- Drafts saved as Git branches (safety net)
- 'Ready for Review' workflow available
- 'Publish' merges to master branch
- Full audit trail of all changes
- Split-screen markdown preview improves UX
- Removed format: yaml-frontmatter requirement
- Added identifier_field: name to use filename
- Added summary: {{filename}} to display filename in list
- Simplified fields to just body/content
This allows existing markdown files without YAML frontmatter to be edited.
Changed from firefrost-website to firefrost-operations-manual.
This is what Decap was always meant to manage - Markdown docs,
not complex HTML templates.
Collections:
- Core Documents (SESSION-HANDOFF-NEXT.md, tasks.md)
- Planning Docs (folder)
- Milestones (folder)
- Implementation Guides (folder)
Branch: master (ops manual uses master, not main)
- Added format: frontmatter and extension: njk
- Changed body widget from markdown to code (HTML)
- Added hidden layout field
- Added description field to match existing frontmatter
This allows editing existing pages without restructuring the site.
