Rename docs back to website

- I'm not constrained to the folder name "docs" if I'm deploying using
  the gh-pages npm package, copying files to the gh-pages branch.
- Had to run `npm i` twice for the package-lock.json changes to
  make any sense. And it's still leaving `extraneous` entries around.

Author: 1j01

README.md

@@ -40,21 +40,19 @@ To test the Eye Gaze Mode properly, I needed a facial mouse, but eye trackers ar
 
 ## Software Architecture
 
-This is a monorepo containing npm workspaces for the library (`core`), the desktop app (`desktop-app`), and the website (`docs`).
+This is a monorepo containing npm workspaces for the library (`core`), the desktop app (`desktop-app`), and the website (`website`).
 
 ### Website
 
 The website uses symlinks to reference the library (`core`) and shared resources (`images`) during development.
 
-When deploying with `npm run deploy -w docs`, the symlinks are dereferenced using `cp -rL`.
+When deploying with `npm run deploy -w website`, the symlinks are dereferenced using `cp -rL`.
 
 The website is deployed to GitHub Pages using the [`gh-pages`](https://www.npmjs.com/package/gh-pages) npm package.
 
-GitHub Pages supports symlinks, but not to paths outside of `docs` when deploying `docs` as the site root, unfortunately,
+(GitHub Pages supports symlinks, but not to paths outside of `docs` when deploying `docs` as the site root, unfortunately,
 hence I can't use symlinks to reference the library and avoid a deployment script, while keeping a clean repository structure.
-I would have to have the website files at the root of the repository, which I don't want.
-
-Since I'm using `gh-pages`, I no longer need to name the folder `docs` at least though... I can change it back to `website`...
+I would have to have the website files at the root of the repository.)
 
 ### Desktop App
 
@@ -104,7 +102,7 @@ MIT-licensed, see [LICENSE.txt](./LICENSE.txt)
 - Open up a command prompt / terminal in the project directory.
 - Run `npm install`
 - Run `npm -w core install` (`-w` is short for `--workspace`, and can be used with many npm commands to target a workspace)
-- Run `npm -w docs start` to start a web server that will automatically reload when files change.
+- Run `npm -w website start` to start a web server that will automatically reload when files change.
 - For the electron app:
 	- Then `npm -w desktop-app install`
 

package-lock.json

@@ -6,7 +6,7 @@
 	"workspaces": [
 		"core",
 		"desktop-app",
-		"docs"
+		"website"
 	],
 	"scripts": {
 		"lint": "cspell-cli lint . && eslint"