firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity

Task #58: The Trinity Image - Upload to Ghost CMS #211

New Issue
Closed
opened 2026-03-21 02:34:10 -05:00 by mkrause612 · 1 comment
mkrause612 commented 2026-03-21 02:34:10 -05:00
Owner
Copy Link

Task #58: The Trinity Image - Upload to Ghost CMS

Time Estimate: 10 minutes

Documentation: docs/tasks/ (see operations manual)

Time: 10 minutes
Status: PENDING
Priority: HIGH
Documentation: docs/tasks/trinity-image-deployment/

Upload The Trinity image to Ghost CMS media library for use across the website.

Steps:

  1. Log into Ghost Admin (firefrostgaming.com/ghost)
  2. Go to Settings → Files
  3. Upload The_Trinity.png
  4. Note the CDN URL (https://firefrostgaming.com/content/images/...)
  5. Document URL in this task

Purpose: Makes image available for use in Ghost pages/posts

Dependencies:

  • Ghost CMS admin access
  • Task #57 (asset committed to repo)

Source: docs/core/tasks.md (Task #58)

### Task #58: The Trinity Image - Upload to Ghost CMS **Time Estimate:** 10 minutes **Documentation:** `docs/tasks/` (see operations manual) --- **Time:** 10 minutes **Status:** PENDING **Priority:** HIGH **Documentation:** `docs/tasks/trinity-image-deployment/` Upload The Trinity image to Ghost CMS media library for use across the website. **Steps:** 1. Log into Ghost Admin (firefrostgaming.com/ghost) 2. Go to Settings → Files 3. Upload The_Trinity.png 4. Note the CDN URL (https://firefrostgaming.com/content/images/...) 5. Document URL in this task **Purpose:** Makes image available for use in Ghost pages/posts **Dependencies:** - Ghost CMS admin access - Task #57 (asset committed to repo) --- --- **Source:** `docs/core/tasks.md` (Task #58)
mkrause612 commented 2026-04-01 18:16:11 -05:00
Author
Owner
Copy Link

This issue is being closed as part of the task system migration on April 1, 2026.

Why: The Gitea Issues + Kanban approach proved too heavyweight for daily operations and lacked accessibility for non-technical team members (Meg, Holly).

New System:

  • BLOCKERS.md - Critical soft launch tasks
  • BACKLOG.md - Future work organized by theme
  • Trinity Console v2 Task Module (planned) - Web-based task management

Archive: All issues preserved in docs/archive/gitea-issues-archive-2026-04-01.md

— Chronicler #54

This issue is being closed as part of the task system migration on April 1, 2026. **Why:** The Gitea Issues + Kanban approach proved too heavyweight for daily operations and lacked accessibility for non-technical team members (Meg, Holly). **New System:** - `BLOCKERS.md` - Critical soft launch tasks - `BACKLOG.md` - Future work organized by theme - Trinity Console v2 Task Module (planned) - Web-based task management **Archive:** All issues preserved in `docs/archive/gitea-issues-archive-2026-04-01.md` — Chronicler #54
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/automation
n8n workflows and automation
 area/billing
Paymenter billing system
 area/development-tools
Internal tools for workflow automation and team productivity
 area/email
Mailcow email system
 area/game-servers
Minecraft or other game servers
 area/networking
Network infrastructure and configuration
 area/operations
General operations and documentation
 area/panel
Pterodactyl Panel
 area/website
Ghost CMS website
 area/wings
Pterodactyl Wings
 duplicate
This issue is a duplicate of another issue
 for/holly
Assigned to Holly (unicorn20089)
 for/meg
Assigned to Meg (GingerFury)
 for/michael
Assigned to Michael (Frostystyle)
 good-first-issue
Good for newcomers
 help-wanted
Extra attention needed
 needs-board-sync
New issue needs to be added to project board
 operations
priority
critical
Emergency — immediate attention required
priority
high
Important — address soon
priority
low
Nice to have, not urgent
priority
medium
Normal priority
status
backlog
Not yet started, in backlog
status
blocked
Cannot proceed, blocked by dependency
status
done
Completed and closed
status
in-progress
Currently being worked on
status
review
Work complete, awaiting review
status
to-do
Ready to start, in queue
type
bug
Something isn't working
type
docs
Documentation improvements or additions
type
feature
New feature or enhancement request
type
infrastructure
Infrastructure, deployment, or DevOps work
type
refactor
Code refactoring or technical debt
type
task
General task or work item
wont-do
This will not be worked on
No Label area/website for/michael
priority
medium
status
backlog
type
infrastructure
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Gingerfury Unicorn20089 mkrause612
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: firefrost-gaming/firefrost-operations-manual#211
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?