initial commit

PerisanWordle v1.4.1

.env

@@ -0,0 +1 @@
+CI= npm run build

.gitignore

@@ -0,0 +1,23 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+
+# testing
+/coverage
+
+# production
+/build
+
+# misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

.prettierrc

@@ -0,0 +1,2 @@
+singleQuote: true
+semi: false

.vscode/settings.json

@@ -0,0 +1,4 @@
+{
+  "editor.formatOnSave": true,
+  "editor.defaultFormatter": "esbenp.prettier-vscode"
+}

Dockerfile

@@ -0,0 +1,7 @@
+FROM node
+
+COPY . . 
+RUN npm install
+
+EXPOSE 3000
+CMD npm run start

README.md

@@ -1,2 +1,35 @@
-# PersianWordle
-Persian wordle base an Typescript , React js , TaliwindCss , PostCss , PersianWord Dictionary and productuon build run static host
+# Persian Wordle a  Wordle Clone
+
+- Go play the real Wordle [here](https://www.powerlanguage.co.uk/wordle/)
+- Read the story behind it [here](https://www.nytimes.com/2022/01/03/technology/wordle-word-game-creator.html)
+- Try a Live of this clone project [here](https://persianwordle.githup.io)
+
+
+_Design Decisions:_
+I used a combination of React, Typescript, and Tailwind to build this Wordle Clone. When examining the original Wordle, I assumed the list might come from an external API or database, but after investigating in chrome dev tools I found that the list of words is simply stored in an array on the front end. I'm using the same list as the OG Wordle uses, but watch out for spoilers if you go find the file in this repo! The word match functionality is simple: the word array index increments each day from a fixed game epoch timestamp (only one puzzle per day!) roughly like so:
+
+```
+WORDS[Math.floor((NOW_IN_MS - GAME_EPOCH_IN_MS) / ONE_DAY_IN_MS)]
+```
+
+React enabled me to componentize the littlest parts of the game - keys and letter cells - and use them as the building blocks for the keyboard, word grid, and winning solution graphic. As for handling state, I used the built in useState and useEffect hooks to track guesses, whether the game is won, and to conditionally render popups.
+
+In addition to other things, Typescript helped ensure type safety for the statuses of each guessed letter, which were used in many areas of the app and needed to be accurate for the game to work correctly.
+
+I implemented Tailwind mostly because I wanted to learn how to use Tailwind CSS, but I also took advantage of [Tailwind UI](https://tailwindui.com/) with their [headless package](https://headlessui.dev/) to build the modals and notifications. This was such an easy way to build simple popups for how to play, winning the game, and invalid words.
+
+_To Run Locally:_
+Clone the repository and perform the following command line actions:
+```bash
+$ cd wordle
+$ npm install
+$ npm run start
+```
+
+_To build/run docker container:_
+```bash
+$ docker build -t notwordle .
+$ docker run -d -p 3000:3000 notwordle
+```
+open http://localhost:3000 in browser.
+