This is an attempt by Nina Paley (art) and Atul Varma (code) to tinker with procedural art.
 
 
 
Go to file
Atul Varma ea7673f70e
Split up CSS into multiple files and use CSS imports (#206)
This splits up our `styles.css` file into multiple CSS files that sit alongside the TSX files that use their classes.  All "generic" CSS that isn't used by any one particular component, such as our `thingy` class, is currently being put into `page.css`.

The CSS files are imported via `import` statements in their associated TSX files. As such, this fixes #164.

This also starts formatting our CSS using Prettier.

It also moves some of our `<head>` tags back into `index.html`, reverting a tiny bit of #205, to ensure that some of the metadata can be recognized by browsers, and start loading asynchronously, independently of the page's JavaScript (I see no reason why any of those elements need to change dynamically based on the app's state, so there don't seem to be any downsides to this).
2021-07-11 15:59:37 -04:00
.github/workflows Use eslint. (#133) 2021-05-28 10:17:45 -04:00
.vscode Split up CSS into multiple files and use CSS imports (#206) 2021-07-11 15:59:37 -04:00
__mocks__ Split up CSS into multiple files and use CSS imports (#206) 2021-07-11 15:59:37 -04:00
assets added gradients to hearts 2021-07-10 09:08:53 -05:00
dist Split up CSS into multiple files and use CSS imports (#206) 2021-07-11 15:59:37 -04:00
lib Split up CSS into multiple files and use CSS imports (#206) 2021-07-11 15:59:37 -04:00
vendor Add a 'disable gradients' toggle. (#148) 2021-06-06 17:49:49 -04:00
.babelrc Always permalink to Mandalas. (#99) 2021-04-24 08:46:32 -04:00
.eslintrc Use eslint. (#133) 2021-05-28 10:17:45 -04:00
.gitattributes #56 Add logo and favicon (#205) 2021-07-11 12:04:10 -04:00
.gitignore Split up CSS into multiple files and use CSS imports (#206) 2021-07-11 15:59:37 -04:00
.prettierignore Run prettier during CI. (#85) 2021-04-07 19:39:55 -04:00
CODE_OF_CONDUCT.md Convert code of conduct to markdown. 2021-05-25 15:00:31 -04:00
LICENSE.md Clarify some license stuff. 2021-04-25 09:41:02 -04:00
README.md Add documentation on symbols. (#166) 2021-06-12 08:53:32 -07:00
build-avro-typescript.js Always permalink to Mandalas. (#99) 2021-04-24 08:46:32 -04:00
build-vocabulary.js Always permalink to Mandalas. (#99) 2021-04-24 08:46:32 -04:00
package-lock.json randHue color algorithm (#194) 2021-07-03 09:34:30 -04:00
package.json Split up CSS into multiple files and use CSS imports (#206) 2021-07-11 15:59:37 -04:00
tsconfig.json Use esbuild instead of Parcel. (#131) 2021-05-28 07:34:17 -04:00

README.md

This is an attempt by Nina Paley (art) and Atul Varma (code) to tinker with procedural art.

Right now there is no particular goal other than to explore various ideas. The project consists of a web site with multiple pages, each of which is an experiment of some kind.

It can be viewed online or iterated on locally using the instructions below.

Quick start

This requires NodeJS. It was started with NodeJS 14.15.4, but hopefully it should work with any recent version.

After cloning the repository and entering it, run:

npm run watch

then visit http://localhost:1234.

Adding symbols

Documentation for adding and changing symbols can be found in assets/symbols/_instructions.md.

Running tests

To run tests interactively, run:

npm run test:watch

Type checking

To make sure that everything type-checks okay, run:

npm run typecheck

Note that you may want to install a TypeScript plugin for your favorite editor. Aside from telling you what type errors you have in real-time, editor integration also provides code autocompletion and other affordances that can greatly improve your productivity. For more details, see Atul's Fun with TypeScript series of videos.

Code style

All code styling is managed by Prettier.

To format the code automatically, run:

npm run prettier:fix

You can alternatively install a Prettier extension for your editor; see its website for more details.

Deployment

To deploy the project to GitHub Pages, run:

npm run deploy