Feature/post2020 archive display

.gitignore

@@ -4,6 +4,3 @@
 /node_modules/
 .idea/
 /coverage/
-
-# ignore alternative build configs
-*-build-config.js

README.md

@@ -27,13 +27,13 @@ Once installed **you must accept the standard terms and conditions of use**. The
 
 ### Installation
 
-There is currently an issue with one or more of the dependencies which means that to install you **must** use
+There is currently an issue with one or more of the dependencies which means that to install you **must** run `npm install` and then
 
 ```sh
 npm ci
 ```
 
-instead of `npm install`.
+instead of just `npm install`.
 
 ## Continuous build environment (single machine)
 
@@ -49,6 +49,17 @@ Build the extension continuously as you edit files:
 npm run watch
 ```
 
+### Actual real-life development:
+
+in two separate terminals, run these commands.
+
+```sh
+npm run chrome -- -- --env.file=./nyu-build-config.js --env.build=debug  --env.config=std
+npm run watch -- --env.file=./nyu-build-config.js --env.browser=chrome --env.build=debug --env.config=std
+```
+
+This starts a fresh Chrome install and also continuously monitors the code and recompiles it.
+
 ### Build output
 
 Both of the above scripts will generate eight output folders named in the format `{browser}-{config}-{build}`.
@@ -92,6 +103,22 @@ So if, for example, you create your own build config called `alt-build-config.js
 
 Any API URL you set in that file will be used as the default url, unless you specify an `--env.api` option. The `--env.api` option will override whatever you set in your copy of `build-config.js`.
 
+## NYU Release Ritual
+
+1. up the version in the build config file (`nyu-build-config.js` or `legacy-build-config.js`). Legacy is `v2.x.y`, Full is `v3.x.y`.
+2. tag a version, push tag, `git tag v3.0.2` (or whatever).
+3. build both legacy and standard
+ - legacy:
+ 	1. `npm run build -- --env.file=./legacy-build-config.js --env.build=release --env.config=std`
+ 	2. `pushd build/chrome-std-release && zip -r0 ../chrome-$(jq .version manifest.json | tr -d \").zip ./* && popd`
+ 	3. `pushd build/firefox-std-release && zip -r0 ../firefox-$(jq .version manifest.json | tr -d \").zip ./* && popd`
+ - standard: 
+ 	1. `npm run build -- --env.file=./nyu-build-config.js --env.build=release --env.config=std`
+ 	2. `pushd build/chrome-std-release && zip -r0 ../chrome-$(jq .version manifest.json | tr -d \").zip ./* && popd`
+ 	3. `pushd build/firefox-std-release && zip -r0 ../firefox-$(jq .version manifest.json | tr -d \").zip ./* && popd`
+4. download source zip for Firefox
+5. upload source zip to Firefox with msg "There are instructions for how to build the extension in the README in the extension/ folder in the archive -- you'll want to run `npm install`, then `npm ci` and then use `$ npm run build -- --env.file=./nyu-build-config.js --env.build=release --env.config=std --env.browser=firefox` to generate the same minified, production code as in the uploaded version of the extension. Be sure to check the output for sporadic network errors; I've verified that these instructions work in a clean build environment."
+
 ## Unit tests
 
 Unit tests do not require a running backend server.

TESTING.md

@@ -0,0 +1,25 @@
+in Legacy version:
+
+1. Share Sponsored Posts ON Share Ad Targeting Information ON
+
+   ensure that ads and targeting is sent ensure that public posts are NOT sent
+
+   CHECK
+
+2. Share Sponsored Posts ON Share Ad Targeting Information OFF
+
+   ensure that targeting is not sent, but ads are
+
+   CHECK
+
+3. Share Sponsored Posts OFF Share Ad Targeting Information ON
+
+   ensure that nothing is sent.
+
+   CHECK
+
+in both versions:
+
+Share My Language
+
+CHECK