CASE STUDY / SOURCE PRESERVATION AND DEPLOYMENT BOUNDARIES

A website is more than its files.

01 / The problem

Evolve Still Becoming into Hello World without replacing the existing site or losing meaningful source assets.

02 / Technical environment

GitHub version control, embedded images, standalone HTML pages and Cloudflare Workers.

03 / Investigation

Trace the source history, review routing, extract the original images and compare each build against the visual direction.

04 / Tools used

Git, Python, HTML, browser inspection and Cloudflare Workers.

05 / Findings

The early layout needed stronger imagery and cleaner styling. Inline scripts and styles also made a restrictive Content Security Policy harder to apply.

06 / Implemented changes

Separated the new portfolio from the original, optimized images and moved scripts and styles into shared files. Deployed the result to my Cloudflare account.

07 / Testing and verification

Local checks cover chapter routes, image integrity, blocked source paths and response handling. Browser checks confirmed the live homepage and every chapter on ronnydonkor.com.

08 / Results and limitations

The portfolio runs on ronnydonkor.com through my own Cloudflare Worker, with the original Still Becoming project preserved separately.

09 / Lesson

Preserve first. Verify each boundary separately: source, build, hosting, DNS and live behavior.