Task Tracker

What It Does

• Multiple Trackers — Organize tasks by project, client, or effort. Each tracker is its own workspace with a name and type label.
• Severity at a Glance — 1–10 severity scale with green-to-red color coding. No guessing which task is on fire.
• Completion Tracking — Toggle tasks done with a single click. Progress you can see without a burndown chart.
• Drag-and-Drop Reordering — Prioritize by dragging. No up-arrow button mashing required.
• Rich Text Notes — Every task gets a full notes panel with a TipTap rich text editor. Title, date, and formatted content stay with the work.
• Dynamic Checklists — Build reusable checklist templates, then clone them across devices or items. Steps can be plain text or shell commands with copy-to-clipboard, optional display labels, and hide/show toggling. Completion timestamps give you an audit trail.
• Projects with Steps — Multi-step project plans with a TipTap rich-text editor per step, code blocks with syntax highlighting, per-step reference links, drag-reorder, completion toggling that auto-advances to the next step, progress bars, and search filtering.
• Bearer Token Auth — All /api/v1/* endpoints require an Authorization: Bearer token. No secrets in the Docker image — the frontend picks up its token at runtime via /config.js. MCP-ready design lets any API consumer hit the same endpoints.
• Real-Time Updates — TanStack Query handles caching and revalidation. Changes reflect without a full page reload.

Architecture

Why I Built It

I needed it. Every task tracker assumes you have one project. Real infrastructure work means juggling multiple efforts across multiple environments, each with its own priority stack and its own fire drill. I needed something that treats trackers as first-class citizens, not tags on a flat list.

But needing it was only the first win. Publishing it gave me the opportunity to see if others would find it useful, and more importantly, it gave me a real project to learn public GitHub integrations and CI/CD pipelines end to end (I have a Forgejo Internal Git Repository). The plan is to push a DockerHub image so anyone can pull it and run it without touching the build stack. That's the full cycle that I need to know in and out. Build what I need, share what I built, and learn what it takes to ship it properly.

Win. Win. Win.

The royal aesthetic is intentional. It's your realm. Manage it like you rule it.

My Co-Workers Feedback: It's nice, but the royal theme isn't my thing. How about a Pirate or Egyptian Theme? My response was: "Sounds like an RFE to me..."

Version History

• v1 — Task Tracking Foundation — Multiple trackers, severity-coded tasks, drag-and-drop reordering, completion tracking, rich text notes.
• v2 — Checklist System — Reusable checklist templates, clone-to-device deployment, text and command step types, copy-to-clipboard for commands, hide/show toggling, completion timestamps and audit reports.
• v3 — Projects & API Security — Multi-step projects with TipTap rich-text content per step, code blocks with syntax highlighting, per-step references, drag-reorder steps, auto-advance on completion, progress bars, incomplete-only filter, full-text search. Bearer token authentication on all API endpoints, runtime token injection via /config.js, MCP-ready CRUD endpoints.

API Endpoints

Details