* remove daisyui and rebuild styles * very basic setup of new design - missing components etc * basic navbar with reusable landing components * basic puzzle of the day * update todos * update todos * add curated landing puzzle cards with selectable board (#55) * update with footer * add button to solve today's puzzle * Make landing page a dead view Render the home page from PageController with a static board preview, link puzzle cards and CTAs to public-code play routes, count puzzles from the DB, and add a global footer. * Serve a marketing-only JS bundle on the landing page Build a small marketing entry point with phoenix_html and the plain-DOM navbar, select it on controller-rendered pages, and keep the full LiveView bundle for LiveView pages. * Add landing page SEO metadata Replace the Phoenix default title with a descriptive Lucid Chess title, and add description, canonical, Open Graph, and Twitter card tags to the landing page. * Complete the hero copy block Add the spark icon primitive and the Endgames, made clear eyebrow. The primary CTA keeps linking to the active puzzle rather than scrolling to the board. * Add a persisted global daily puzzle Assign one endgame per UTC day in a daily_puzzles table with a unique date, preferring endgames unused in the last 30 days and falling back to any. Concurrent first requests insert with on-conflict-ignore and read the winning row. The landing board now shows the daily puzzle. * remove unused CSS, nav links, time pill * allow devices to connect to dev server by changing IP address to 0.0.0.0 * Restore the colour-mode switch and add a dark palette * Use brand colour tokens on the play page * self host fonts - closes issue #62 * begin splitting CSS into modules * remove hover on hero chessboard, split more css modules * remove interactivity from hero chessboard * update todo
4.9 KiB
Chesstrainer
An endgame trainer: the user plays a stored endgame position against tablebase-optimal defence and is graded on every move.
Core model
Endgame: A stored chess position (FEN) plus metadata — side to move, result, rating, tags — that can be played as a puzzle. Avoid: Position, puzzle
Puzzle: A playable challenge derived from an endgame: play the winning (or drawing) side correctly against tablebase-optimal defence. Each endgame currently yields one puzzle. Avoid: Endgame (the stored record), exercise
Daily puzzle: The one endgame assigned to a UTC date and shared by every user; the assignment is persisted so it stays stable for that day. Avoid: Random puzzle, featured puzzle
Attempt: A recorded playthrough of a puzzle by a user, ending solved or failed; a per-user record, distinct from an endgame's global attempt and solve counts. Avoid: Run, session, game
Theme: A label describing an endgame's technique or goal, such as "mate in 2", "Lucena" or "opposition"; an endgame can carry several. Avoid: Tag, label, category, UI theme, colour mode
Interface
Colour mode:
A user's display preference for the interface — system, light or dark — where
system follows the operating system setting. It is a per-browser preference,
independent of any user account.
Avoid: Theme, colour scheme, display theme
Key: The canonical material signature of an endgame's starting position — which pieces each side has, written strongest side first and colour-agnostic (e.g. "KQ v KR"). Used to group and search endgames by material. Avoid: Material signature, hash
Public code: The short, stable identifier an endgame is played under in player-facing links, distinct from its database id and safe to share. Avoid: Slug, UUID, endgame id, token
Identity & access
User: A person who can sign in to the trainer, identified by a unique email address and a unique username. Avoid: Account, player
Role:
A user's authority tier — member, moderator, admin or super_admin — deciding access to the admin area and the power to manage other users.
Avoid: Permission, access level
Plan:
A user's subscription tier — free or premium — independent of their role.
Avoid: Tier, subscription, membership
Play
Winning side: The side that can force a win from the position; the side the user plays in win-type endgames.
Drawing side: In draw endgames, the side that must hold the draw; the side the user plays. Avoid: Defender
Optimal move: The tablebase's best move for the side to move (sharpest win / hardest defence).
Winning move: A move that keeps the win (the opponent is still lost). Passes. Avoid: Good move, accurate move
Losing move: A move that throws away the result (the position becomes drawn or lost). Fails the puzzle. Avoid: Blunder, mistake
Conversion: The decisive zeroing move — a promotion — that ends a conversion-type puzzle.
Cutoff: The terminal condition short of mate at which a puzzle counts as solved: promotion (still winning) for conversion puzzles, mate otherwise.
Ratings
Rating: A user's estimated solving skill, or an endgame's estimated difficulty, on a scale that lets the two be compared. Avoid: Score, ELO, rank
Rating deviation: The uncertainty around a rating; it widens with inactivity and narrows with rated results, so a less certain rating moves further per result. Avoid: Error margin, variance
Rating window: The minimum interval before the same user replaying the same endgame can change either rating again. Avoid: Cooldown (reserved for tablebase rate-limiting)
Volatility: A measure of how erratic a competitor's recent results are, used by some rating systems; the trainer deliberately does not track it. Avoid: Variance, inconsistency
Infrastructure
Tablebase: A database of precomputed optimal outcomes for every position with at most seven pieces. Positions with five or fewer pieces are answered from local Syzygy files; six and seven piece positions come from the lichess API. The trainer keeps only the outcome data it grades on — enough to tell a winning move from a losing one — and caches API answers only; local answers are cheap enough to refetch.
Probe: A single lookup of one position in the tablebase, returning its result and its legal moves. A probe is answered locally or by the API.
Position key: The identity of a tablebase position — board, side to move, castling and en-passant — excluding the move clocks. FENs that differ only in their clocks share a position key. Avoid: Full FEN
Cooldown: Rate-limit state entered after a 429 from the lichess API, during which the trainer blocks play for positions that need the API (six or seven pieces). Local positions are unaffected.
Cache sweep: The periodic halving of LFU cache frequencies (weekly) that lets rarely-used entries age out.