Operator workflow

Daily publishing without spoiler or source mistakes

This page documents the Daily Game Hints editorial system: draft, verify, publish, validate, monitor, and correct visible issues.

Verification signals

published means checked, not guessed.

Required fields

Published entries need sourceNotes, verifiedAt, status, difficulty, hints, and a reveal-only answer definition.

Review cadence

Today pages are checked before publication and monitored after deployment with the Wordle monitor script.

Correction loop

If a page is wrong, update the entry, document the fix, re-run validation, and leave prototype/archive content noindexed until replaced.

Manual entry flow

Daily checklist

  1. Create a draft: bun run new:wordle -- --date YYYY-MM-DD --number ####.
  2. Manually verify the answer through the approved editorial process.
  3. Write original hints, difficulty notes, source notes, and reveal-only definition.
  4. Set status to published only after sourceNotes and verifiedAt are complete.
  5. Run bun run validate, then browser-check mobile and desktop flows.
  6. After deployment, run bun run monitor:wordle and verify production URLs.

Risk controls

Game-specific rules before expansion

Wordle: answer/help pages can use original hints and explicit reveal controls with clear non-affiliation language.

Connections/Strands/crosswords: do not copy full clue lists, grids, groups, or publisher puzzle text without permission.

All games: keep answers out of metadata, archives, sitemap labels, emails, and screenshots until explicit reveal.

Supporting files: content/publishing/production-readiness-runbook.md, content/publishing/launch-dependency-tickets.md, content/publishing/wordle-verification-checklist.md, content/publishing/brand-domain-notes.md, content/puzzles/wordle-draft.template.json.