Contact and Feedback

Send a note

The most reliable contact path on the site is the form below. It is built for bug reports, wording fixes, guide requests, and other messages that are specific enough to turn into a clear next action.

How to reach the project

The public inbox for the project is hello@dontwordle.top. Keep that address for people who prefer email, but use the on-page form if you want the most dependable delivery path from the site itself.

If your note is primarily about how the project works or why the site is structured the way it is, read the About page first. If your question is about rule logic, start with the How to Play guide. Contact is most useful when a public page does not already answer the question.

What kinds of feedback help most

The best messages are specific enough that they can turn into a fix or a better page. That includes bug reports tied to a date and a guess sequence, wording that feels misleading on a guide page, and strategy questions that reveal a real gap in the site's current explanations. Those signals help improve both the playable board and the content network around it.

Good contact messages often point to a single page and a single problem. For example: a clue explanation on the rules page that still feels ambiguous, a missing bridge between the definition guide and the strategy guide, or a bug on the homepage board that can be reproduced step by step.

How to send a useful bug report

If you are writing about game behavior, include the puzzle date, the guesses you entered, the feedback you saw, and the point where the board stopped matching your expectation. Screenshots help, but the most valuable part is usually the sequence of guesses. Reverse-word-game bugs are often about history and constraints, so the path matters as much as the final state.

If the issue is content rather than gameplay, include the page URL and the exact sentence or section that felt off. That is far more actionable than a general note like "the guide is confusing." The site is intentionally structured so each page answers a distinct question. Pointing to the specific sentence that fails helps keep future revisions focused instead of turning into broad rewrites that add little value.

When not to use contact first

Some questions are better answered by public pages because the answer should be useful for more than one reader. If you are new to the project, start with the blog hub and follow the sequence into definition, rules, and strategy. That path exists so the site does not need to repeat the same onboarding reply in private.

In practice, contact should be the escalation path, not the first click. The more a question maps to one of the public pages, the more likely the right fix is improving that page instead of sending a one-off reply. That helps the site stay compact, readable, and worth indexing, because each new update becomes durable public value rather than hidden inbox work.

What happens next

Not every message will lead to a public response, but the most useful ones usually lead to one of three outcomes: a gameplay fix, a wording fix, or a new guide topic. That is the standard the site tries to keep. Feedback should strengthen the playable board or the supporting information architecture, not create noise.

If you are unsure where to start, the safest route is simple: play the homepage puzzle, read the rules guide, then use the form or email the project if something still feels unresolved. That keeps the public pages and the feedback loop working together instead of in separate silos.