Biomedical engineering and computer science
A concise origin story: education, medical and scientific interests, and the throughline connecting research, software, and lived experience.
A public front door, a chronological record of the gene therapy chapter, and a place for the work, writing, videos, and notes that make the story legible.
The site can introduce the whole person first: health, science, software, systems, storytelling, and the reasons this record exists.
A concise origin story: education, medical and scientific interests, and the throughline connecting research, software, and lived experience.
A lightweight portfolio for selected projects, demos, writing, GitHub links, papers, and anything that still feels current.
Short essays that help people understand the treatment path without turning the homepage into a medical record.
A simple beginning for visitors who want to understand what is happening, why the videos exist, and where to go next.
Keep the main narrative clear for family, friends, collaborators, and future-you, with the sensitive parts intentionally separated.
Each update can pair a video with a short written summary, dates, tags, and links to deeper context pages.
Visitors should be able to browse chronologically or jump by topic: preparation, collection, treatment, recovery, logistics, reflections.
The gene therapy timeline lives behind named passcodes. Each code can be generated, labeled, and revoked from the owner console.
Journal entries and videos are arranged chronologically after a valid passcode unlocks the page.
Each passcode has a name, status, use count, and last-used timestamp.
The admin console is intended for Cloudflare Access login with the owner email.
The static prototype shows the intended boundaries. Anything private should move behind server-side auth before real media or medical details are added.
Visible to anyone, search-friendly, and safe to share widely.
For trusted people: videos, journal entries, contextual notes, and treatment-phase organization.
Raw drafts, unedited media, feelings, and specifics that should never be protected by frontend code alone.