diff --git a/README.md b/README.md
index 35d5e5a..b77371d 100644
--- a/README.md
+++ b/README.md
@@ -1,102 +1,254 @@
 # Response Area Sandbox
 
-Develop local TypeScript code to create custom response area types, and see them previewed live in the main application. When they're ready, provide your code to the Lambda Feedback team, who will consider including it in the main application after (human) review.
-
 ## Overview
 
-To create a new response area type, you'll need to:
+**Purpose:** This sandbox lets you develop a custom Response Area locally on your machine and test it live inside the real, production Lambda Feedback app — without deploying anything.
+
+![Example of a custom Response Area in Lambda Feedback](docs/images/response-area-example.png)
+
+### How it works
+
+Normally, the Lambda Feedback app loads its response area components from its own production bundle. The sandbox exploits a browser-side settings page that lets you redirect one response area type to a URL of your choice.
+
+When you run `yarn dev`, the sandbox compiles your code and serves it from a local server (e.g. `localhost:4173`). You register that URL in the app's sandbox settings — and from that point on, **only in your browser**, the production app fetches and renders your locally-served code instead of its built-in version. Every time you save a file, the server recompiles and the app picks up the new version automatically.
+
+```
+  Your machine                        Lambda Feedback (your browser)
+  ─────────────────────────           ──────────────────────────────
+  src/types/YourType/
+        │
+        │  yarn dev (compile + serve)
+        ▼
+  Local server ──── fetched every 0.5s ────▶  Production app
+  localhost:4173                              renders your Response Area
+        ▲
+        │  save a file → auto-recompile
+  Your code editor
+```
+
+No code reaches the production backend until you submit a Pull Request. The redirect is stored only in your browser's local storage, so other users are unaffected.
 
-1. **Extend the base class**: Create a new class that extends `ResponseAreaTub`
-2. **Define the expected configuration and answer types**: Set `configSchema`, and `answerSchema`
-3. **Implement components**: Create `InputComponent` (shown to students and teachers) and `WizardComponent` (for configuration)
+### Workflow summary
 
-**📚 For detailed documentation on the `ResponseAreaTub` class and component props, see the inline code comments in [response-area-tub.ts](src/types/response-area-tub.ts) and [base-props.type.ts](src/types/base-props.type.ts) (they'll also show up in your IDE's autocomplete and hover tooltips).**
+To create a new type, you'll:
 
-Find inspiration with the existing response area types in the repo - it's fine to copy/paste code between types to get started quickly.
+1. **Copy the Sandbox template** — duplicate `src/types/Sandbox/` and rename it after your type
+2. **Build your Response Area** — edit the components in your new folder to create the interface students and teachers will see
+3. **Preview it live** — the sandbox dev server injects your code into the Lambda Feedback app so you can test it in real time
+
+**📚 For detailed technical documentation, see the inline code comments in [response-area-tub.ts](src/types/response-area-tub.ts) and [base-props.type.ts](src/types/base-props.type.ts) — these will also appear in your code editor's autocomplete and hover tooltips.**
+
+The existing types in `src/types/` are good examples to learn from — it's fine to copy code from them to get started.
+
+See also: [Lambda Feedback user documentation](https://lambda-feedback.github.io/user-documentation/advanced/)
 
 ## Development
 
+### Prerequisites
+
+Before you begin, make sure you have the following:
+
+- **Basic knowledge of TypeScript or JavaScript** — you'll be writing and editing code to build your Response Area. If you're new to TypeScript, [this introduction](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) is a good starting point
+- **Git** — for downloading the code. [Install Git](https://git-scm.com/downloads)
+- **A code editor** — [Visual Studio Code](https://code.visualstudio.com/) is recommended if you don't have one
+- **A Lambda Feedback account with Teacher access** — you'll need this in Step 7. Contact [mmmeser@imperial.ac.uk](mailto:mmmeser@imperial.ac.uk) if you don't have it yet
+
 ### Setup locally
 
-##### 1. Clone this repository
+##### 1. Fork and download this repository
+
+First, you'll need a free [GitHub account](https://github.com) if you don't have one. Then fork the repository to your own GitHub account by clicking **Fork** at the top of [this page](https://github.com/lambda-feedback/response-area-sandbox).
+
+Then download your fork — choose whichever method you prefer:
+
+**Option A — GitHub Desktop** (recommended for beginners): Open [GitHub Desktop](https://desktop.github.com/), sign in, and clone your forked repository from there.
+
+**Option B — Terminal**:
+```sh
+git clone https://github.com/YOUR_USERNAME/response-area-sandbox.git
+cd response-area-sandbox
+```
+Replace `YOUR_USERNAME` with your GitHub username.
 
 ##### 2. Install Node
 
-Recommended via [Nodenv](https://github.com/nodenv/nodenv) or [NVM](https://github.com/nvm-sh/nvm)
+If you haven't used Node before, download and install the **LTS** version from [nodejs.org](https://nodejs.org).
+
+If you already manage multiple Node versions, you can use [Nodenv](https://github.com/nodenv/nodenv) or [NVM](https://github.com/nvm-sh/nvm) instead.
 
 ##### 3. Install Yarn and packages
 
+In VS Code, open a terminal via **Terminal → New Terminal** in the menu bar. Then run the following commands:
+
 ```
 npm install --global yarn
 yarn
 ```
 
-##### 4. Run the dev server
+The first command installs Yarn (a package manager). The second installs the project's dependencies.
+
+##### 4. Create your new type
+
+**a) Copy the Sandbox folder**
+
+Duplicate the folder `src/types/Sandbox/` and rename the copy after your type (e.g. `src/types/<YourType>/`). This is your starting point — all your code will live here.
+
+In VS Code, right-click the `Sandbox` folder in the Explorer panel and select **Copy**, then right-click the `types` folder and select **Paste**. Rename the pasted folder to your type name. On Mac Finder, you can right-click → **Duplicate** instead. On Windows Explorer, right-click → **Copy**, then right-click an empty area → **Paste**.
+
+**b) Point the dev server at your new folder**
+
+Open `src/sandbox-component.tsx` in your code editor and update line 2 to import from your new folder. Only change the path — leave `SandboxResponseAreaTub` as-is:
+
+```
+import { SandboxResponseAreaTub } from './types/<YourType>/index'
+```
+
+**c) Set your type's name**
+
+Open `src/types/<YourType>/index.ts` and find the line:
+
+```
+public readonly responseType = 'SANDBOX'
+```
+
+Replace `SANDBOX` with your chosen name in UPPER_CASE (e.g. `YOUR_TYPE`). This name must be unique — don't use a name already used by another type in the repo.
+
+> ⚠️ **Remember this name** — you will need to enter it exactly (including capitalisation) in Step 6.
+
+##### 5. Run the dev server
 
 ```sh
 yarn dev 
 ```
 
-This will serve your new reponse area type as a compiled IIFE bundle.
+This will serve your new Response Area as a compiled JavaScript file.
 
-Note the Local URL (it should be something like `http://localhost:4173/`).
+Once running, your terminal will show something like:
 
-##### 5. (optional) Configure your new type in the code
+```
+  ➜  Local:   http://localhost:4173/
+```
 
-Find the file at `src/types/Sandbox/index.ts` and set the value of `public readonly responseType` to the name of your type (usually in UPPER_CASE). It must be unique to the project. The default is `SANDBOX`.
+Note down the **Local** URL — you'll need it in Step 6.
 
 ##### 6. Configure the sandbox access on the app
 
-Visit [`lambdafeedback.com/settings/sandbox`](https://www.lambdafeedback.com/settings/sandbox) and configure the sandbox with:
-- **URL**: the URL found in step 4
-- **Name**: the name of your new type. It must be the same as the name chosen in the previous step. `SANDBOX` is the default.
+Log in to [lambdafeedback.com](https://www.lambdafeedback.com) first, then go to [Settings → Sandbox](https://www.lambdafeedback.com/settings/sandbox). Fill in:
+- **URL**: the Local URL from Step 5
+- **Name**: the name you set in Step 4c (default: `SANDBOX`). This must match exactly, including capitalisation.
 
-SAVE the configuration. The configuration is automatically saved in your browser.
+Click **Save**. The settings are stored in your browser.
 
-Continue if:
+You should see a **'Ready'** message — you can then move on to Step 7.
 
-- If you receive a 'Ready' message. 
+![Sandbox settings page showing a Ready message](docs/images/sandbox-settings-ready.png)
 
-Stop if you receive an error. Possible reasons:
-
-- the URL may be incorrect (check and try again)
-- the local server may not be running (return to Step 4)
-- there may be a problem with the local server (return to Step 4)
+If you see an error instead, check:
+- the URL matches what was shown in Step 5
+- the dev server from Step 5 is still running in your terminal
 
 ##### 7. Check it works, and begin developing
 
-You will need TEACHER access on the main application. Login as a TEACHER and add a response area, select the input and `SANDBOX` should be an option (or whatever you named the type to). 
+You will need Teacher access to test this — if you don't have it yet, contact [mmmeser@imperial.ac.uk](mailto:mmmeser@imperial.ac.uk).
 
-Try changing the sandbox component, for example edit the placeholder text. You should see the response area update in real time (every 0.5s) in your browser.
+1. Select a module you are a teacher on. We suggest using a teacher sandbox module — if you don't have one, let us know at [mmmeser@imperial.ac.uk](mailto:mmmeser@imperial.ac.uk)
+2. Select a question set, then a question, then click **Add Response Area**
+3. In the input type dropdown, you should see your type (the name you set in Step 4c) as an option
 
-Suggestion: find inspiration with the other types already created in the repo to get started quickly (it's fine to copy/paste code between types).
+![Input type dropdown showing SANDBOX as an option](docs/images/response-area-dropdown.png)
 
-You component will auto-refresh within the app when you edit it.
+For more guidance on navigating the Lambda Feedback interface, see the [Lambda Feedback user documentation](https://lambda-feedback.github.io/user-documentation/advanced/).
 
-_Pro tip: setup your text editor to follow the lint, formatting and type configurations set for the project._
+Try editing your Response Area — open `src/types/<YourType>/SandboxInput.component.tsx` in your code editor and make a small change, such as editing a text label. You should see it update in real time (every 0.5s) in your browser.
 
 ### Troubleshooting
 
+##### 0. How to open the browser console
+
+Press **F12** (or **Cmd+Option+J** on Mac) to open the browser developer tools, then click the **Console** tab.
+
 ##### 1. Sandbox component is not loading
 
-Inspect the browser console and make sure the iife file is found. 
+Open the browser console and check for any error messages.
 
 ##### 2. Sandbox component stopped refreshing
 
 Reload the page.
-If it keeps happening, check the browser console.
+If it keeps happening, open the browser console and check for error messages.
 
 ##### 3. A `[VOID]` component is shown
 
 The response area type isn't available. This could be because:
-- the sandbox isn't available anymore
-- the type's name was changed
+- the dev server from Step 5 has stopped — return to Step 5 and run it again
+- the type's name was changed — make sure the name in Step 4c matches the name in Step 6
 
 ##### 4. `Error: Could not extract config` or `Error: Could not extract answer`
 
-This is likely caused by a stored config/answer value in a response area that doesn't comply to the schema defined in the new response area tub class.
-This can happen if you change the config/answer schema after having created/answered response areas. This isn't allowed.
-To fix this, revert to the original schemas and delete the old response area(s) before changing the schemas.
+This happens when you change the structure of your config or answer after already creating or answering response areas using the old structure. This isn't supported.
+
+To fix this, undo your structural changes and delete any response areas created with the old structure before making the change again.
+
+## Next Steps
+
+### Understanding the code structure
+
+Your Response Area lives in `src/types/<YourType>/`. The key files are:
+
+- **`index.ts`** — defines the name of your type, the settings it exposes, and how student answers are stored. This is the *tub* class that extends `ResponseAreaTub`.
+- **`SandboxInput.component.tsx`** — the UI component that both students and teachers will see.
+
+#### The two components
+
+Every tub class defines two components — both must be implemented:
+
+| Component | Who sees it | Purpose |
+|---|---|---|
+| `InputComponent` | Students (and teachers viewing answers) | The input UI students interact with to enter their answer |
+| `WizardComponent` | Teachers (when setting up the question) | The configuration UI — often identical to `InputComponent` for simple types |
+
+In `InputComponent`, the parent component holds all state. Your component **must** call `handleChange` every time the input value changes — otherwise the parent won't know the answer has been updated.
+
+In `WizardComponent`, `handleChange` takes a slightly different shape — it must include the `responseType`:
+
+```ts
+WizardComponent = (props: BaseResponseAreaWizardProps) => {
+  return MyInput({
+    ...props,
+    handleChange: answer => {
+      props.handleChange({
+        responseType: this.responseType,  // required
+        answer,
+      })
+    },
+    answer: this.answer,
+  })
+}
+```
+
+#### The answer schema
+
+`answerSchema` is a [Zod](https://zod.dev/) schema that defines what a valid answer looks like (e.g. `z.string()`, `z.number()`). The template already validates and narrows the type for you in `InputComponent` via `safeParse` — you just need to define the schema.
+
+Start by editing `SandboxInput.component.tsx`. For full details on what you can configure, see the inline code comments in [response-area-tub.ts](src/types/response-area-tub.ts) — these explain everything available to you.
+
+The existing types in `src/types/` are good examples to learn from — it's fine to copy code between them.
+
+### Submitting your work
+
+When your Response Area is ready, open a Pull Request against the `main` branch of [this repository](https://github.com/lambda-feedback/response-area-sandbox). The Lambda Feedback team will review it and get back to you.
+
+If you're new to Pull Requests, [GitHub's guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) walks you through the process.
+
+### Getting help
+
+- For questions about the sandbox or the submission process, contact [mmmeser@imperial.ac.uk](mailto:mmmeser@imperial.ac.uk)
+- For guidance on the Lambda Feedback app, see the [Lambda Feedback user documentation](https://lambda-feedback.github.io/user-documentation/advanced/)
+
+## Platform Notes
+
+Things to be aware of when building your Response Area:
+
+1. **An answer is required** — students must provide an answer before they can submit. Make sure your Response Area always allows a value to be entered.
 
 ### Note to LLM helpers
 
diff --git a/docs/images/response-area-dropdown.png b/docs/images/response-area-dropdown.png
new file mode 100644
index 0000000..b43b6f0
Binary files /dev/null and b/docs/images/response-area-dropdown.png differ
diff --git a/docs/images/response-area-example.png b/docs/images/response-area-example.png
new file mode 100644
index 0000000..8b6c834
Binary files /dev/null and b/docs/images/response-area-example.png differ
diff --git a/docs/images/sandbox-settings-ready.png b/docs/images/sandbox-settings-ready.png
new file mode 100644
index 0000000..cfe6b84
Binary files /dev/null and b/docs/images/sandbox-settings-ready.png differ