Rules and Editorial Standards
CardGamesHQ aims to keep each playable game, rules explanation, strategy guide, and comparison page accurate, useful, and consistent with the ruleset actually implemented.
Rules Selection
Traditional card games rarely have a single universal ruleset. Names, deck sizes, redeals, scoring values, legal moves, and tie procedures can differ by region, publisher, or household. CardGamesHQ starts with a widely recognized version that works clearly in a browser game.
When several common choices exist, the game page should state the choice used by the playable version. Variants may be described separately, but they should not be mixed into the main instructions in a way that makes the implemented rules ambiguous.
Gameplay Review
Rules text is checked against the behavior of the game itself. Review covers setup, legal and illegal actions, turn changes, card draws, stock and discard behavior, scoring, special cards, round transitions, victory, defeat, ties, undo behavior, and starting a new game.
A playable game is not considered accurately documented when its written instructions describe a different variation. When a mismatch is found, the implementation and explanation are reviewed together so the correction does not leave a second contradiction elsewhere on the page.
Strategy and Recommendations
Strategy guidance focuses on decisions available in the implemented game. It should explain why a choice improves position, information, flexibility, scoring, or winning chances rather than rely on generic advice that could appear on any card-game page.
Recommendation pages compare actual CardGamesHQ games by player count, difficulty, session length, and play style. They are intended to help a visitor choose a suitable game, not to manufacture a ranking where the underlying games are not comparable.
Corrections and Updates
Substantive corrections may update gameplay logic, rules, scoring explanations, metadata, or related guidance. Sitemap modification dates are intended to reflect meaningful page changes rather than routine deployments or cosmetic footer updates.
Readers can report a correction through the Contact page. Useful reports name the page, describe the disputed behavior or wording, and identify the expected rule or result. Regional variants are welcome context even when the current implementation deliberately uses another accepted version.