about this build

hazynforsythe.com and hazyn.page are hand-built static sites stitched together into one garden—written in html and css inside visual studio code, pushed to github, and deployed through cloudflare pages.

stack & tools

this is a small, deliberate stack—chosen to help understand my process.

• html & css—every page is written by hand, with semantic markup and a focus on readability and accessibility.
• visual studio code—my main coding space, with a small set of extensions for formatting, linting, and git integration.
• github—two repositories, one per domain, so i can track changes, roll back experiments, and let future me see what past me was thinking.
• cloudflare pages—handles builds and hosting for hazynforsythe.com and hazyn.page, wired directly to the github branches.
• sprinkled javascript—tiny scripts like nav.js to keep navigation consistent and add quality-of-life touches without turning the site into a full app.

the goal is a cosy, understandable codebase—something i can maintain while autistic, adhd, and dyspraxic—i care about accessibility, so please let me know if you have any suggestions.

how it fits together

there are two main domains that behave like one site—different branches of the same world, connected by shared navigation and design decisions.

under the hood, each section lives in its own folder—for example, hazynforsythe/ for the author site and hazyn/ for the project pages—then cloudflare pages maps those folders to the right domains during deployment.

learning, mistakes, and doing this slowly

i am not a formally trained developer—i am a poet and roleplayer teaching myself to code for fun. this build is a snapshot of that process rather than a final, perfect thing.

• iteration over perfection—pages launch gently messy, get refactored later, and sometimes get completely rewritten once i understand a cleaner pattern.
• accessibility as a baseline—i try to include semantic headings, skip links, focus styles, and readable contrast, then correct anything i learn i have missed.
• sensory–safe design—backgrounds and motion are chosen with overstimulation in mind, and i pay attention to how the site feels to sit in for a long time.
• small reusable pieces—theme files like coder.css, poet.css, and sakura.css let me create different moods while keeping the structure stable.

there will always be things i want to improve—better responsiveness, more accessible widgets, cleaner css—the point is that this site is something i genuinely understand and can keep growing with.

a tiny colophon

fonts, textures, and little invisible helpers that make this build feel like mine.

• fonts—averia serif libre for headings and caudex for body text, both served by google fonts.
• imagery—backgrounds and icons drawn or collaged into a personal asset library at faeries.hazyn.page.
• hosting & deploys—cloudflare pages handles builds from github commits, so updating the site is as simple as pushing a change.
• helpers—tiny javascript utilities for navigation, back-to-top buttons, and accessibility tweaks, kept deliberately small so they stay understandable.

if you are reading this because you want to build your own little corner of the internet—you absolutely can. start with one plain html page, add a stylesheet, and let it grow alongside you.