THE METHOD / A REPRODUCTION GUIDE

Make a rule.
Find a world.

These ten websites begin with ten different ideas about what a web page can feel like. Technique follows the idea: a solar field needs a shader; a weaving archive needs crossings; an instrument needs a clock that can keep time.

01 / Start with the material

Choose the primary material before choosing a layout. Define a concept, a signature rendering method, a palette, and a typographic voice. If two sketches share all four, change one of them. The collection should read as ten places, not ten themes.

02 / Keep the delivery simple

Every experience is one index.html with embedded styles and scripts. The only external resources are Google Fonts and a pinned Three.js module for AERFORM. Each guide is also a self-contained HTML page. No package installation, bundler, or compilation is needed to serve the portfolio.

portfolio/
  index.html
  guide/index.html
  sites/01-solaris/index.html
  sites/01-solaris/guide/index.html
  …
  sites/10-observed/index.html
  sites/10-observed/guide/index.html

To preview the complete folder:

cd portfolio
python3 -m http.server 8000

Visit http://localhost:8000. Keep the directory structure intact so relative links continue to work.

03 / Review in three passes

1. Composition: open every page at desktop size; inspect hierarchy, contrast, image-free art, and console output.
2. Small screens: inspect at 375 × 812; fix overflow, crowded controls, clipped type, and unclear reading order.
3. Behavior: test real controls, keyboard interaction, reduced motion, canvas resizing, and frame timing. Sample the renderer rather than assuming it is fast.

04 / Build accessible alternatives

Keep information in semantic HTML. Treat artwork as decorative unless its content matters, then provide a description. Every animated site reads prefers-reduced-motion; explicit controls remain usable. The data room uses text, units, line patterns, and an established colorblind-safe palette together.

Inside each experiment

Publish

Upload the portfolio folder directly to a static host. On Vercel, from that folder, run the command below. The source has no build step.

npx vercel deploy --prod --yes

After deployment, open the hub, each experience, and every guide on the public hostname. The local STATUS.md records what was actually checked and any limitations.