kirastreet/generative-crochet

This repository is a small, static front-end site for an MFA thesis project about generative crochet. There is no evidence of a backend, database, or build pipeline; the architecture appears to be browser-only HTML/CSS/JavaScript.

1. Entry points

The site has at least two HTML entry pages: index.html and crochetGenerator.html. These likely split the public-facing thesis/project presentation from the interactive generator experience.

2. Presentation layer

crochetProject.css and crochetProject.js appear to support the main thesis/project page. This layer likely handles layout, copy, visuals, and any page-specific interactions for the project narrative.

3. Generator layer

crochetGenerator.css and crochet.js appear to support the crochet pattern generator. This is the most likely “dynamic” part of the site, responsible for creating or updating the generative crochet output in the browser.

4. Shared client-side runtime

All behavior is likely executed directly in the browser using plain JavaScript, with no framework or compiled assets visible in the repository. That means the site is probably assembled from static files and DOM-based interactions.

5. Visual assets

There are two image directories: crochetPics and patternPics. These likely separate documentation imagery or finished crochet photos from pattern/generative reference graphics. The split suggests distinct visual roles in the site’s content model.

6. Content / media flow

A typical flow is: HTML loads CSS and JS, JS manipulates the DOM or canvas/SVG elements, and imagery from the two asset folders is displayed as supporting content. The generator page likely produces or previews crochet-like patterns while the project page presents examples and thesis context.

7. Functional boundary between pages

The repository appears organized around two concerns: a static informational thesis site and an interactive generator. That separation is reflected in the duplicated naming of paired JS/CSS files for the project and generator views.

8. Deployment model

Given the file set, this is likely deployed as a static website, probably on a standard web host. The README’s link to generativecrochet.com reinforces that this is a standalone published site rather than an app backed by services.

9. What to show in an architecture diagram

A clear diagram would show the browser as the runtime, the two HTML entry points as top-level entry nodes, the corresponding CSS/JS files attached per page, and the image folders as static asset dependencies. No server-side components are indicated by the repository contents.

10. Key boundary to preserve

The main architectural boundary is between static presentation assets and client-side generative logic. If you diagram this repo accurately, it should look like a self-contained front-end experience with page-specific scripts and styles, not a multi-tier application.