Personal site / journey log

Akash Chaurasia

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.

Public
Background, work, selected writing
Journey
Vlog-first updates by phase and date
Private
Raw journal and sensitive notes later

Public homepage

The site can introduce the whole person first: health, science, software, systems, storytelling, and the reasons this record exists.

Background

Biomedical engineering and computer science

A concise origin story: education, medical and scientific interests, and the throughline connecting research, software, and lived experience.

Work

Research, projects, and software

A lightweight portfolio for selected projects, demos, writing, GitHub links, papers, and anything that still feels current.

Writing

Plain-language context

Short essays that help people understand the treatment path without turning the homepage into a medical record.

Start here

A simple beginning for visitors who want to understand what is happening, why the videos exist, and where to go next.

Why

Make the story easier to follow

Keep the main narrative clear for family, friends, collaborators, and future-you, with the sensitive parts intentionally separated.

Format

Vlogs first, summaries beside them

Each update can pair a video with a short written summary, dates, tags, and links to deeper context pages.

Structure

Phase, date, and theme

Visitors should be able to browse chronologically or jump by topic: preparation, collection, treatment, recovery, logistics, reflections.

GT timeline

The gene therapy timeline lives behind named passcodes. Each code can be generated, labeled, and revoked from the owner console.

Timeline

/gt/

Journal entries and videos are arranged chronologically after a valid passcode unlocks the page.

Passcodes

One code per person or group

Each passcode has a name, status, use count, and last-used timestamp.

Owner

/admin/

The admin console is intended for Cloudflare Access login with the owner email.

Access layers

The static prototype shows the intended boundaries. Anything private should move behind server-side auth before real media or medical details are added.

Public

Homepage and edited writing

Visible to anyone, search-friendly, and safe to share widely.

  • Bio, work, writing, selected overview
  • Carefully edited summaries
  • No raw private medical details
Shared

GT timeline

For trusted people: videos, journal entries, contextual notes, and treatment-phase organization.

  • GT timeline route
  • Named passcodes managed from the owner console
  • Organized by phase and date
  • Video hosting can be added cleanly
Owner

Private journal

Raw drafts, unedited media, feelings, and specifics that should never be protected by frontend code alone.

  • Requires real account auth
  • Separate from guest access
  • Not rendered for public visitors