Tim McCarthy
ed7900656d
The lobby Copy buttons now flip to a transient "✓ Copied" label instead of popping a modal alert, matching the admin page's copy buttons. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
24 lines
2.4 KiB
Markdown
24 lines
2.4 KiB
Markdown
## Major Improvements
|
|
|
|
- [ ] **Replace polling in the frontend with a websocket connection** I believe the 2s polling interval is an artifact of the previous HTMX-based frontend implementation, and the app might feel more responsive if it were websocket-based or otherwise event driven.
|
|
|
|
- [ ] **Allow Deep players to roll back game events.** This may require some updates to how game state is handled. Feel free to propose significant overhauls/refactors to enable this cleanly, I am not attached to the current architecture at all.
|
|
|
|
- [ ] **Dead Pi-Rat re-roll flow.** I suspect this is badly broken, as it was implemented in a rush by an older model. In particular, other players will need to contribute likes/hates and techniques, which I believe are not currently implemented. This flow should also be used for new players who join after initial character creation, and should take place as a between-scenes phase after Deep Upkeep.
|
|
|
|
## Missing Features
|
|
|
|
- [x] **Incomplete admin page.**: The Admin page should include links for players to re-join the game.
|
|
- [x] **Less intrusive link copied notification.** When you copy a join link from the lobby page, it pops up an alert() to let you know the link was copied. I'd prefer something more subtle, and more importantly not modal.
|
|
- [ ] **Rules endpoint** Make a nicely formatted HTML version of the rulebook. It should probably also be linked from a help menu somewhere that's always available, rather than only being surfaced on the splash page of the site (which joining players don't even see). Work from "Rats with Gats beta.pdf" rather than "RULEBOOK.md", which is a low fidelity AI summary of the former.
|
|
|
|
## Cosmetic
|
|
|
|
- [ ] **Refactor the CSS.** Make it easy to re-theme by keeping the definitions of primary/background/highlight/etc colors confined to a few specific styles. If this requires adopting some kind of CSS framework/preprocessing, so be it.
|
|
- [ ] **Re-styling**. The entire app could use a face lift, but in particular the splash page is ugly.
|
|
|
|
## Worth Double-Checking / Minor
|
|
|
|
- [ ] **Dev/prod server flows.** Investigate where assets are served from in both development and production workflows. Make sure we're not committing any compiled svelte code. In production, the app should be used through the Nix flake, which should handle the compile step when the flake is built.
|
|
- [ ] **More formal database migration procedures.**
|