With regard to support, the maintainers of this repository are not obligated to provide assistance and likely never will. If you have received support in the past, consider it a rare and unlikely-to-be-repeated stroke of luck. For modifications, enhancements, or custom support, you are encouraged to fork the repository and make the necessary changes independently. Contributions via merge or pull requests are welcome, but please be aware that there is no guarantee they will be reviewed or merged. Treat this project as though it is effectively archived, even if it has not been officially labeled as such. While any contributions you make are appreciated, please lower and manage your expectations and keep them modest.

• If server restarts while playing, the next guess will end in a "fake rows" error. Resolved by reloading the page.

• generate session (cookie) when none is present
• keep user data in server memory
• optional: session memory management based on cookie lifetime

• word generation – requires: allowed word list
• input validation (check matches) – requires: allowed word list, generated/current word, input of last word, number of tries
• trigger like quiz win/fail – requires: number of tries
• refactoring
  • rename wordle to lettr bec of trademark
  • use packages instead of everythiung in one file
  • move leftover routing from main.go to routes packages
  • session handling
• check out https://github.com/torenware/vite-go
  • https://vitejs.dev/guide/backend-integration VS https://www.npmjs.com/package/webpack-assets-manifest

• must
  • word not InWordDB
  • website app version via ??? (assets? or on webpage?)
  • (mobile) keyboard (use + indication for used letters)
  • protect against request size + correct http 413 error code throw
  • fix scripts/tools.sh func_exec_cli passing parameter issue
  • bugfix: full page get form submit request on random occations when it should just be a htmx post
  • avoid same word twice (words to exclude (previous taken quizes))
  • editorial work: e.g. words like games or gamer are missing + maybe we introduce a common vs uncommen word list
    • word suggestion (button to save (unknown) word eg. in LiteFS/email/github-issue/something)
      • form spam protection mechanism
        • easy honeypot (html form fields)
        • captcha: https://github.com/altcha-org/altcha
        • other (research task)?
    • corpora dataset export https://corpora.uni-leipzig.de/en/res?corpusId=eng_news_2023&word=would
      • https://github.com/Leipzig-Corpora-Collection
    • https://api.wortschatz-leipzig.de/ws/swagger-ui/index.html#/Words/getWordInformation
    • https://wortschatz.uni-leipzig.de/en/download/English
  • fix past words display
  • add github action ci pipeline build + tests
    • build
    • tests
    • linting
    • test image build
    • formatting
  • add imprint/link to imprint
  • fix letter hints is not reset with new game bug
  • add metrics endpoint
  • add scheduled RemoveExpiredSessions func (go routine in main.go)
  • tailwind check build succes (with files)
  • os.SIGNAL handling (gracefull server Shutdown)
    • main func testing
      • https://stackoverflow.com/questions/31352239/how-to-test-the-main-package-functions
  • self include unpack htmx javascript lib
    • reasons:
      • supply chain security
        • don't trust external script sources, even so they are very very well known
        • best example was the polyfill incident
        • also: htmx repo probbably should be forked + synced with upstream
        • • add renovate
      • much more clean & professional to own it + allows customizations
  • add shellcheck to ci pipeline & local setup
  • ESLint
  • decide if we want to use htmx response extension vs htmx oob-swat core + custom js code
    • note: we want philosopical correct http error codes
    • atm we use both => quesion should we only use one, when, which one, when not, why both + wrote adr (decision record)
  • "someone" does not trust our tests, and with this bulletpoint solved would
    • include browser based e2e tests e.g. playwright/cypress
    • api tests?
    • load tests?
    • more unit tests?
    • more integration tests? (e.g. go's testserver based tests)
  • renoevate: for docker images add compatibility / build versioing to also update alpine version
• nice-to-have (e.g. node & golang)
  • option for double letter hint
  • auto updates via e.g. renovate
    • installing-onboarding
  • more hints
    • which lttrs are duplicats
    • give next position of letter which wo do not have one yet
  • add tls/https serve capability (enabled e.g. via commandline flags)
  • move all tests and build etc to container image build and out of github workflow (so we only use the container build in the workflow)
    • reason: making it more ci tool independant / easier to adapt in other ci tools
  • Circuit Breaker Support
  • pick word dataset picker
  • get definition (e.g. wikitionary)
    • options:
      • https://raw.githubusercontent.com/wordset/wordset-dictionary/master/data/%s.json
      • wikitionary API
        • en
          • https://en.wiktionary.org/api/rest_v1/page/definition/hund
          • https://en.wiktionary.org/wiki/hund
        • de
          • no api
          • https://de.wiktionary.org/wiki/hund
      • openthesaurus (de only)
        • https://www.openthesaurus.de/synonyme/search?q=test&format=application/json
  • hint feature / give me one letter
  • ui languge should also change
  • http error codes:
    • 414 URI Too Long
    • 431 Request Header Fields Too Large (RFC 6585)
  • improve VS Code dev container
  • htmx routing ? (keep nav + footer but change body + change url)
  • mark suggested word on keyboard (pink letters)