update boker to myboker.org

public/content/index.json

@@ -21,15 +21,15 @@
       "path": "./public/content/projects/schedule-generator-app.md"
     },
     {
-      "title": "Boker",
-      "slug": "boker",
+      "title": "myboker.org",
+      "slug": "myboker-org",
       "type": "projects",
-      "summary": "A lightweight poker tracking web app for recording buy-ins, payouts, and session history through an append-only ledger, with player stats and analytics over time.",
+      "summary": "A home poker league tracker with player stats, leaderboards, session history, and settlement tracking — built around an append-only event ledger and now live as a public web app.",
       "label": "Project",
-      "date": "2026-03-22",
+      "date": "2026-06-28",
       "status": "Active",
-      "github": "https://github.com/SowinskiBraeden/boker",
-      "demo": null,
+      "github": null,
+      "demo": "https://myboker.org",
       "featured": true,
       "order": 2,
       "tags": [
@@ -37,10 +37,10 @@
         "Flask",
         "Jinja",
         "Chart.js",
-        "CSV",
+        "PostgreSQL",
         "Analytics"
       ],
-      "path": "./public/content/projects/boker.md"
+      "path": "./public/content/projects/myboker-org.md"
     },
     {
       "title": "DayZ Reforger Bot",

public/content/projects/boker.md

@@ -1,28 +0,0 @@
----
-title: Boker
-slug: boker
-summary: A lightweight poker tracking web app for recording buy-ins, payouts, and session history through an append-only ledger, with player stats and analytics over time.
-label: Project
-date: 2026-03-22
-status: Active
-featured: true
-order: 2
-github: https://github.com/SowinskiBraeden/boker
-tags: Python, Flask, Jinja, Chart.js, CSV, Analytics
----
-
-## Overview
-
-This project reflects my interest in practical software that solves a real problem with a clean and trustworthy data model.
-
-I built it as a web portal for tracking low-stakes poker nights without relying on a spreadsheet. The app includes public-facing statistics pages, per-session and per-player views, and an admin area for recording buy-ins, cash-outs, payouts, and notes. Rather than overwriting records, the system uses an append-only CSV ledger so the full financial history stays visible and easy to audit.
-
-## Focus Areas
-
-- Designing an append-only event ledger for trustworthy record keeping
-- Building clear player and session analytics from raw event data
-- Creating simple admin tooling for real-world use without unnecessary complexity
-
-## Notes
-
-One of the parts I like most about this project is the storage model. Each row represents an event rather than a final snapshot, which makes rebuys, corrections, payouts, and session changes easier to follow over time. It is a small project, but it reflects how I like to build software: practical, structured, and designed so the data remains easy to trust.

public/content/projects/myboker-org.md

@@ -0,0 +1,31 @@
+---
+title: myboker.org
+slug: myboker-org
+summary: A home poker league tracker with player stats, leaderboards, session history, and settlement tracking. Built around an append-only event ledger and now live as a public web app.
+label: Project
+date: 2026-06-28
+status: Active
+featured: true
+order: 2
+live: https://myboker.org
+tags: Python, Flask, Jinja, Chart.js, PostgreSQL, Analytics
+---
+
+## Overview
+
+This project started as a small internal tool called Boker for tracking buy-ins and payouts during casual poker nights. It has since grown into [myboker.org](https://myboker.org), a more complete home league tracker that I now run publicly.
+
+The app covers the full workflow: recording sessions, tracking buy-ins and rebuys, calculating settlements and payouts, and surfacing per-player stats and leaderboards over time. There is a public-facing side for players to check standings and session history, and an admin area for managing the actual data entry during and after a game.
+
+The core data model is an append-only event ledger backed by PostgreSQL in production. Every buy-in, rebuy, payout, and correction is recorded as its own event rather than overwriting state, which keeps the full history auditable and makes it straightforward to reconstruct any session at any point.
+
+## Focus Areas
+
+- Designing an append-only event ledger for trustworthy, auditable record keeping
+- Building player stats, leaderboards, and session analytics from raw event data
+- Handling settlement and payout calculations across variable buy-ins and rebuys
+- Creating simple admin tooling that works well in a real-world, low-distraction context
+
+## Notes
+
+The storage model is the part I keep coming back to. Because every action is an event rather than a snapshot, it is easy to trace what happened in a session, catch data entry mistakes, and replay history accurately. It is a genuinely useful tool for a specific problem — nobody wants to manage a poker league in a spreadsheet — and that constraint kept the design grounded throughout.