diff --git a/README.md b/README.md
index 27760f9..2de07ac 100644
--- a/README.md
+++ b/README.md
@@ -4,14 +4,198 @@
 
 Exercism exercises in ReScript.
 
+## Installation
+
+Track exercises target [Rescript] 12.2.0 using the [ReScript Test][ReScriptTest] testing framework on [Node.js] 22+. If you're contributing to the track, you will also need [make](https://www.gnu.org/software/make/).
+
+### Setting up the development environment
+
+Run the following commands from inside the project root directory to install the required tools:
+
+```shell
+npm install
+git submodule update --init --recursive # add/update a local copy of the problem-specification submodule
+```
+
+To automate the creation of practice exercise tests, our track tooling consumes data from the the [problem specifications][exercism-problem-specifications-link] submodule. Because these specifications serve as the canonical source for all Exercism tracks, any upstream updates ensure our test cases remain consistent with the global exercise standard.
+
+If you have format on save enabled for JSON files, it is recommended to disable this feature. Alternatively save JSON files with `Ctrl+K s` to save without applying formatting rules.
+
+### Running the development environment
+
+Open up two terminals. By running the commands below, files will compile on save and re-run the test suite.
+
+```shell
+# Terminal 1
+npm run res:start
+
+# Terminal 2
+npm run test
+```
+
+## Coding Style
+
+Use `PascalCase.res` for Reason implementation file names.
+
+A ReScript [interface file][rescript-interface-file-link] (`.resi`) should be included with every exercise to help the user get started.
+For example:
+
+```shell
+# exercises/practice/<exercise-name>/.meta/Example.resi
+let add: (int, int) => int
+```
+
+Run `make format` on your code before pushing.
+
+If you are using VS Code, install the official [ReScript VS Code extension](https://marketplace.visualstudio.com/items?itemName=chenglou92.rescript-vscode) for syntax highlighting and code formatting. Unofficial plugins exist for JetBrains products.
+
+Terminal based text editors often work with the [ReScript Language Server][rescript-language-server-link] installed. Refer to the documentation of your text editor / IDE for further instructions
+
+## Contributing to Exercises
+
+Contributing to the exercises in this track can involve: adding a new exercise, updating an existing one, or managing the test suite.
+
+Documentation on contributing to Exercism can be found [here][exercism-contributing-docs-link].
+
+### Adding a new exercise
+
+To introduce a brand new practice exercise to the track, follow these steps:
+
+- **Initialise the exercise:** Run the generator script to create the folder structure and boilerplate.
+
+```shell
+bin/add-practice-exercise <exercise-slug>
+
+# Optionally, you can also specify the exercise's difficulty (via `-d`) and/or author's GitHub username (via `-a`):
+bin/add-practice-exercise -a foobar -d 3 <exercise-slug>
+```
+
+- **Register the exercise:** Open the root `config.json` file. Update the difficulty rating of the exercise, and then ensure that that exercise is correctly placed in order of difficulty and then alphabetically within that difiiculty rating.
+
+- **Create the stub:** In `exercises/practice/<exercise-slug>/src/`, modify the .res file to return `panic("'<function-name>' has not been implemented")`.
+
+- **Define the interface:** Update the .resi (interface) file in `exercises/practice/<exercise-slug>/src/` and `exercises/practice/<exercise-slug>/.meta/` directories to include the function signatures. This provides students with the necessary type hints.
+
+- **Generate test cases:** Follow the steps in the [Generating and managing tests](#generating-and-managing-tests) subsection below.
+
+- **Provide an example solution:** In `exercises/practice/<exercise-slug>/.meta/`, implement a working solution in the .res file. This does not need to be an exemplar solution, but must pass all test cases.
+
+### Generating and managing tests
+
+We use a templating system to keep tests consistent with Exercism's canonical data found in the problem-specification git submodule.
+
+Tests are written using [rescript-test](https://bloodyowl.github.io/rescript-test/). Follow these steps when writing tests:
+
+- **Filter canonical data:** Open `exercises/practice/<exercise-slug>/.meta/tests.toml`. If a specific canonical test case is not applicable to ReScript, add ignore = true below its description. E.g.
+
+```toml
+[7ee45d52-5d35-4fbd-b6f1-5c8cd8a67f18]
+description = "Seven-digit number that is not an Armstrong number"
+
+[5ee2fdf8-334e-4a46-bb8d-e5c19c02c148]
+description = "Armstrong number containing seven zeroes"
+include = false
+
+[12ffbf10-307a-434e-b4ad-c925680e1dd4]
+description = "The largest and last Armstrong number"
+include = false
+```
+
+- **Configure the test template:** Edit `test_templates/<ExerciseName>_template.res`. Delete and uncomment the code where indicated. Use previous templates as examples of how to achieve what you need. Common comparator functions are found in `test_generator/Assertions.res`
+
+- **Generate and run tests:** To build the test file and run it, run `make test EXERCISE=<exercise-slug>`. Your generated test cases are found in `exercises/<exercise-slug>/tests/<ExerciseName>_test.res`. Verify that the test cases accept and return the correct data.
+
+- **Creating new comparator functions:** If none of the comparator functions satisfy the exercise's test requirements, you can write a new one in `test_generator/Assertions.res` and `test_generator/AssersionGenerators.res`, following the guidelines at https://bloodyowl.github.io/rescript-test/assertions. The function should be returned as a string, so that our templating system can inject the code into the generated tests.
+
+### Updating an existing exercise
+
+When syncing with upstream changes or fixing bugs:
+
+- **Update an exercise:** Modify the exercise files within the `.meta/` folder to reflect changes to the exercise, such as ignored tests or signature changes.
+
+- **Sync interface files:** If the function signature changes, ensure both the stub interface at `src/_.resi` and the example interface at `.meta/_.resi` are updated to match.
+
+- **Verify integrity:** Run the full test suite to ensure no regressions with `make test`.
+
+### Running tests
+
+- Run a single exercise's tests:
+
+```shell
+make test EXERCISE=<exercise-slug>
+```
+
+- Run all exercise's tests:
+
+```shell
+make test
+```
+
+This command will iterate over all exercises and check to see if their example implementation passes all the tests.
+
+- It is worth running the below commands to test if the code will likely pass CI checks for test cases:
+
+````shell
+./bin/verify-exercises
+
+# test a single exercise:
+./bin/verify-exercises <exercise-slug>
+``` -->
+
+<!-- ## Adding Exercises
+
+Documentation on contributing to Exercism can be found [here][exercism-contributing-docs-link].
+
+New practice exercises can be added via:
+
+```shell
+bin/add-practice-exercise <exercise-slug>
+
+# Optionally, you can also specify the exercise's difficulty (via `-d`) and/or author's GitHub username (via `-a`):
+bin/add-practice-exercise -a foobar -d 3 <exercise-slug>
+````
+
+Now complete the following steps:
+
+- `config.json` - ensure that the new exercise data is correctly placed in order of difficulty and then alphabetically within that difficulty rating.
+- implement exercise test cases, detailed in the [testing](#testing) section below.
+- `exercises/practice/<exercise-slug>/.meta/<exercise-name>.res` - write an example of code here that will pass all test cases. This does not need to be the finest example of how to complete this exercise, but it must pass all the test cases. Update the interface file with the exposed function signatures in the `.resi` file.
+- `exercises/practice/<exercise-slug>/src/<exercise-name>.res` - create an exercise stub here which returns `panic("'<function-name>' has not been implemented")`. Update the interface file with the function signatures, so that the student has a reference to what names and types are used.
+
 ## Testing
 
-To test all exercises, run `./bin/verify-exercises`.
-This command will iterate over all exercises and check to see if their exemplar/example implementation passes all the tests.
+Tests are written using [rescript-test](https://bloodyowl.github.io/rescript-test/). There is a test templating system in place to reduce the amount of work needed by a developer. Follow these steps when writing tests:
 
-To test a single exercise, run `./bin/verify-exercises <exercise-slug>`.
+- `exercises/practice/<exercise-slug>/.meta/tests.toml` - if any of these test cases are not relevant to the language, add `ignore = true` on a newline below the description
+- `exercises/practice/<exercise-slug>/.meta/testTemplate.js` - edit this file to allow the test generator to automatically create test files.
+  - you must write your comparator functions - https://bloodyowl.github.io/rescript-test/assertions.
+  - common assertions with comparator functions are located at `test_generator/assertions.js`. Pass the required ones into the `assertionFunctions` array.
+  - edit the `template` function so that it will generate the test cases. The `c` variable refers to a test case in `problem-specifications/exercises/<exercise-slug>/canonical-data.json`. Look at other exercise test templates for inspiration.
 
-### Using Docker
+Run a single exercise's tests:
+
+```shell
+make test EXERCISE=<exercise-slug>
+```
+
+Run all exercise's tests:
+
+```shell
+make test
+```
+
+This command will iterate over all exercises and check to see if their example implementation passes all the tests.
+
+To test that the example solution will pass the test suite, run:
+
+````shell
+./bin/verify-exercises
+
+# test a single exercise:
+./bin/verify-exercises <exercise-slug>
+``` -->
+
+<!-- ### Using Docker
 
 If your track has a working [test runner](https://exercism.org/docs/building/tooling/test-runners), the `./bin/verify-exercises-in-docker` script can also be used to test all exercises.
 This script pulls (_downloads_) the test runner's [Docker image](https://exercism.org/docs/building/tooling/test-runners/docker) and then uses Docker to run that image to test an exercise.
@@ -19,51 +203,62 @@ This script pulls (_downloads_) the test runner's [Docker image](https://exercis
 ```exercism/note
 The main benefit of this approach is that it best mimics how exercises are tested in production (on the website).
 Another benefit is that you don't have to install track-specific dependencies (e.g. an SDK) locally, you just need Docker installed.
-```
+````
 
-To test a single exercise, run `./bin/verify-exercises-in-docker <exercise-slug>`.
+To test a single exercise, run `./bin/verify-exercises-in-docker <exercise-slug>`. -->
 
-### Linting
+## Linting & Formatting
 
 [`configlet`](https://exercism.org/docs/building/configlet) is an Exercism-wide tool for working with tracks. You can download it by running:
 
 ```shell
-$ ./bin/fetch-configlet
+./bin/fetch-configlet
 ```
 
-Run its [`lint` command](https://exercism.org/docs/building/configlet/lint) to verify if exercises have the required files and if config files are correct:
+Run the [`lint` command][configlet-link-link] to verify if exercises have the required files and if config files are correct. Address any issues before pushing your changes:
 
 ```shell
-$ ./bin/configlet lint
-
-The lint command is under development.
-Please re-run this command regularly to see if your track passes the latest linting rules.
-
-Basic linting finished successfully:
-- config.json exists and is valid JSON
-- config.json has these valid fields:
-    language, slug, active, blurb, version, status, online_editor, key_features, tags
-- Every concept has the required .md files
-- Every concept has a valid links.json file
-- Every concept has a valid .meta/config.json file
-- Every concept exercise has the required .md files
-- Every concept exercise has a valid .meta/config.json file
-- Every practice exercise has the required .md files
-- Every practice exercise has a valid .meta/config.json file
-- Required track docs are present
-- Required shared exercise docs are present
+./bin/configlet lint
 ```
 
-## Adding exercises
-
-New (practice) exercises can be added via:
+Run the [`fmt` command][configlet-fmt-link] to verify if exercises and configuration files are formatted correctly. Address any issues before pushing your changes:
 
 ```shell
-bin/add-practice-exercise <exercise-slug>
-```
+./bin/configlet fmt
 
-Optionally, you can also specify the exercise's difficulty (via `-d`) and/or author's GitHub username (via `-a`):
+# check a single exercise
+./bin/configlet fmt -e <exercise-slug>
 
-```shell
-bin/add-practice-exercise -a foobar -d 3 <exercise-slug>
+# auto format files
+./bin/configlet fmt -u
 ```
+
+If you are auto formatting files, only commit the files relevant to your pull request.
+
+## Pull Requests
+
+Familiarise yourself with the Exercism [documentation][exercism-pr-docs-link] on pull requests.
+
+Make sure your work is commited on a new branch. When you are ready to submit your changes, push your changes to your forked repository and open a pull request on the language track [repository].
+
+When committing your changes to version control, ensure that only the files relevant to the current pull request are committed.
+
+More details on how to create pull requests from a fork can be found [here][github-fork-pr-link].
+
+## Feedback
+
+If you find this documentation is inaccurate or incomplete, or can be improved in any way, please don't hesitate to raise an [issue][issue-link] or submit a pull request.
+
+[ReScript]: https://rescript-lang.org/
+[ReScriptTest]: https://bloodyowl.github.io/rescript-test/
+[Node.js]: https://nodejs.org/
+[repository]: https://github.com/exercism/rescript
+[issue-link]: https://github.com/exercism/rescript/issues
+[configlet-lint-link]: https://exercism.org/docs/building/configlet/lint
+[configlet-fmt-link]: https://exercism.org/docs/building/configlet/fmt
+[github-fork-pr-link]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork
+[exercism-pr-docs-link]: https://exercism.org/docs/building/github/contributors-pull-request-guide
+[exercism-contributing-docs-link]: https://exercism.org/docs/building
+[exercism-problem-specifications-link]: https://github.com/exercism/problem-specifications
+[rescript-language-server-link]: https://www.npmjs.com/package/@rescript/language-server
+[rescript-interface-file-link]: https://rescript-lang.org/docs/manual/module#every-resi-file-is-a-signature