Complete wipeout and greenfield sveltekit app for CI/CD development

.gitignore

@@ -6,4 +6,10 @@ yarn-error.log
 /__sapper__/
 /.cache/
 .vercel
-.env
+.env
+/build
+/.svelte-kit
+/package
+.env
+.env.*
+!.env.example

README.md

@@ -1,126 +1,40 @@
-# nikolas.ws
+# create-svelte
 
-## ToDo Items:
+Everything you need to build a Svelte project, powered by [`create-svelte`](https://github.com/sveltejs/kit/tree/master/packages/create-svelte).
 
-- [x] Add sitemap.xml
-- [ ] Better Alt texts for all images
-- [x] Metadata and JSON-LD
-- [x] Add RSS feed
-- [x] Migrate remaining images to SmugMug
-- [ ] Write up missing project texts
-- [ ] Cypress tests around nav UI 
-- [ ] Cypress tests w. AxE
-- [x] Add bibliography section
-- [x] Add resources section
-- [x] Add Visual Art section
-- [ ] Add music section
-- [x] Add session-based analytics
-- [ ] Syntax highlighting colors
-- [ ] Typeset goodies (small caps?)
+## Creating a project
 
-
-### Texts
-
-- [ ] transcribe talks with recordings
-	- [x] Cartography Symposium (https://vimeo.com/291928620, http://good-maps.nikolas.ws/#1)
-	- [ ] PCC Lectures (http://web-mapping.nikolas.ws/#1)
-- [ ] How Why Done Reports
-- [ ] Rebuild: Session Based Tracking
-- [ ] Rebuild: Using Sapper
-- [ ] Design Systems in 2020
-- [x] Ethical Web Development / The Ethical Internet
-- [ ] Setting type: letterpress style
-- [ ] Aperiodic tiling & CSS
-	- [ ] https://users.csc.calpoly.edu/~zwood/teaching/csc572/final12/kowen/
-
-### Projects
-
-- [ ] Toba Capital
-- [ ] Hansel from Basel
-- [ ] Evidation
-- [ ] SmugMug
-- [ ] Dicegraph
-- [ ] Department Press Estimator: http://estimator.department.press/
-- [ ] Cooking Papa: cooking-papa.nikolas.ws
-
-## Getting started
-
-### Running the project
+If you're seeing this, you've probably already done this step. Congrats!
 
 ```bash
-npm install
-npm run dev
-```
-
-Open up [localhost:3000](http://localhost:3000) and start clicking around.
-
-## Structure
-
-Sapper expects to find two directories in the root of your project —  `src` and `static`.
-
-### src
-
-The [src](src) directory contains the entry points for your app — `client.js`, `server.js` and (optionally) a `service-worker.js` — along with a `template.html` file and a `routes` directory.
-
-
-#### src/routes
-
-This is the heart of your Sapper app. There are two kinds of routes — *pages*, and *server routes*.
-
-**Pages** are Svelte components written in `.svelte` files. When a user first visits the application, they will be served a server-rendered version of the route in question, plus some JavaScript that 'hydrates' the page and initialises a client-side router. From that point forward, navigating to other pages is handled entirely on the client for a fast, app-like feel. (Sapper will preload and cache the code for these subsequent pages, so that navigation is instantaneous.)
+# create a new project in the current directory
+npm init svelte@next
 
-**Server routes** are modules written in `.js` files, that export functions corresponding to HTTP methods. Each function receives Express `request` and `response` objects as arguments, plus a `next` function. This is useful for creating a JSON API, for example.
-
-There are three simple rules for naming the files that define your routes:
-
-* A file called `src/routes/about.svelte` corresponds to the `/about` route. A file called `src/routes/blog/[slug].svelte` corresponds to the `/blog/:slug` route, in which case `params.slug` is available to the route
-* The file `src/routes/index.svelte` (or `src/routes/index.js`) corresponds to the root of your app. `src/routes/about/index.svelte` is treated the same as `src/routes/about.svelte`.
-* Files and directories with a leading underscore do *not* create routes. This allows you to colocate helper modules and components with the routes that depend on them — for example you could have a file called `src/routes/_helpers/datetime.js` and it would *not* create a `/_helpers/datetime` route
-
-### static
-
-The [static](static) directory contains any static assets that should be available. These are served using [sirv](https://github.com/lukeed/sirv).
-
-In your [service-worker.js](src/service-worker.js) file, you can import these as `files` from the generated manifest...
-
-```js
-import { files } from '@sapper/service-worker';
+# create a new project in my-app
+npm init svelte@next my-app
 ```
 
-...so that you can cache them (though you can choose not to, for example if you don't want to cache very large files).
-
-### content
-
-Thie folder of markdown files gets parsed into JSON at `src/data` for consumption and rendering by the application.
-
-## Bundler config
+> Note: the `@next` is temporary
 
-Sapper uses Rollup or webpack to provide code-splitting and dynamic imports, as well as compiling your Svelte components. With webpack, it also provides hot module reloading. As long as you don't do anything daft, you can edit the configuration files to add whatever plugins you'd like.
+## Developing
 
-## Production mode and deployment
-
-To start a production version of your app, run `npm run build && npm start`. This will disable live reloading, and activate the appropriate bundler plugins.
-
-Deploy explicitly with vercel:
+Once you've created a project and installed dependencies with `npm install` (or `pnpm install` or `yarn`), start a development server:
 
 ```bash
-vercel --prod
-```
-
-Or just push to master for the automated CI pipeline.
+npm run dev
 
-## Using external components
+# or start the server and open the app in a new browser tab
+npm run dev -- --open
+```
 
-When using Svelte components installed from npm, such as [@sveltejs/svelte-virtual-list](https://github.com/sveltejs/svelte-virtual-list), Svelte needs the original component source (rather than any precompiled JavaScript that ships with the component). This allows the component to be rendered server-side, and also keeps your client-side app smaller.
+## Building
 
-Because of that, it's essential that the bundler doesn't treat the package as an *external dependency*. You can either modify the `external` option under `server` in [rollup.config.js](rollup.config.js) or the `externals` option in [webpack.config.js](webpack.config.js), or simply install the package to `devDependencies` rather than `dependencies`, which will cause it to get bundled (and therefore compiled) with your app:
+To create a production version of your app:
 
 ```bash
-npm install -D @sveltejs/svelte-virtual-list
+npm run build
 ```
 
+You can preview the production build with `npm run preview`.
 
-## Bugs and feedback
-
-Sapper is in early development, and may have the odd rough edge here and there. Please be vocal over on the [Sapper issue tracker](https://github.com/sveltejs/sapper/issues).
-
+> To deploy your app, you may need to install an [adapter](https://kit.svelte.dev/docs/adapters) for your target environment.