From 68788737e82c80510b1fb042d529222931ecf60a Mon Sep 17 00:00:00 2001 From: Chris Hunt Date: Wed, 11 Jan 2023 12:23:30 +0000 Subject: [PATCH] Update readme --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 0c2778e..67dbc17 100644 --- a/README.md +++ b/README.md @@ -32,6 +32,7 @@ If a new schema version comes out, this is what you will need to do. 1. Create a new branch with the schema version as the branch name (for example, 1.1) 1. Open `site/package.json` and append the version to the output directory `"deploy": "next build && next export -o ../public/1.1/ && touch ../public/.nojekyll",`. It should NOT be added to the second one (`touch ../public/.nojekyll"`) as the .nojekyll needs to be in the root to work +1. Open `processing/processjson.js` and append the version number to the `dir` variable on line 6 `var dir = "./public/1.1";` 1. Open `site/next.config.js` and change `env.schema` to match the version number, add the version number to the `env.listUrl` and append the version number to the `basePath` as well. ## Discovery