\n\nzoetrope is a tool for building CSS demos.\nImagine something like Codepen, except:\n\n* It runs locally on your own computer\n* You use your normal text editor\n* You can't add any HTML or JS. Only CSS.\n\nThat last one is super important.\nCSS demos that depend on JavaScript or lots of little helper `` elements\nare great, but I think it's also fun to try without that stuff, and get\ncreative within the boundaries of what CSS can do all on its own.\nWorking with [PICO-8] taught me how platform constraints can actually inspire\ncreativity rather than stifle it.\nzoetrope is a way for me to bridge the gap and try to bring some of that\nthinking into the stuff I do on the web.\n\nThis is more of a personal tool, and not really intended for widespread public\nadoption.\nIt's open source because it might as well be, and it has this\ndocumentation because I don't like open sourcing things without any.\nYou're more than welcome to give it a try, and I'd be really excited if anybody\ndid.\nBut that's not really the goal here!\n\n## Installation\n\n```\nyarn add -D @hendotcat/zoetrope\n```\n\n## Usage\n\n```\n zoetrope \n\n Commands\n help print this help text\n build build static site\n server run development server\n```\n\nI wanted to optimize out as much tooling boilerplate as possible from my\nworkflow, so zoetrope pulls all the metadata it needs to build a demo from\n`package.json`.\nCheck out the [`package.json` for my doomfire demo][doomfire] for example.\nMost of the values in there are actually used in the built version of the demo\nat https://hen.cat/doomfire.\nI'm not going to document the setup process in detail, but if you do want to\ntry out zoetrope for yourself then go and browse around that repository for a\nmoment.\n\n## Contributing\n\n