← Back to Featured Projects
LP

LifePage

A personal brand studio built around one product promise: take scattered public proof, shape it into a stronger story, and ship a portfolio page plus resume that feels like a real launch, not a profile form.

Status: Active build Lead: Charlie Han Public URL: lifepage.one
AI generation URL import Resume export Custom domains

⚡ What It Delivers

🕸️

Proof Import

Starts from real links and evidence instead of asking users to rewrite their life from scratch.

🧠

Narrative Generation

Shapes raw inputs into positioning, project summaries, resume bullets, and a clearer public story.

📄

Portfolio + Resume

Publishes a public-facing brand page and a dedicated resume path from the same structured profile.

🚀

Deployment Layer

Supports hosted profile URLs, custom domains, visibility controls, and a Cloudflare deployment path.

🎯 The Problem

Most portfolio builders flatten people into a template and most resumes strip away the proof. LifePage is aimed at the gap between raw evidence and a public identity that actually feels coherent.

Proof lives in too many places

Projects, docs, demos, class work, and public links are scattered across different systems.

Resumes and portfolios drift apart

People end up maintaining one story for hiring, another for school, and a third for their personal site.

Typical builders are too shallow

They publish layouts, not narrative structure, deployment controls, or evidence-aware story shaping.

🧭 How It Works

01

Import real proof

Paste websites, GitHub repos, docs, videos, Google Sites pages, or other public references into the system.

02

Extract the signal

The product crawls and reads the evidence, then organizes it into structured inputs the AI layer can reason over.

03

Shape the narrative

LifePage generates positioning, project framing, story arcs, resume bullets, and profile content from the same dataset.

04

Deploy and share

Publish to a hosted path or custom domain, choose visibility rules, and export a resume that matches the site.

👥 Who It Is For

Creators and builders

People who already have proof online but need a cleaner narrative and stronger presentation layer.

🎓

Students applying to college

Applicants who need to show initiative, growth, leadership, and work product in a format admissions teams can scan.

💼

People applying for jobs

Hiring flows that need a recruiter-friendly portfolio, impact framing, and a resume that lines up with the site.

🗂️

People documenting a life

Users who want timelines, milestones, projects, and memories organized into a shareable public record.

✨ Core Product

🔎

Evidence Import

Multiple URLs, screenshots, and public proof items feed the story engine instead of empty forms.

🌍

Deploy Anywhere

Hosted profile paths, custom-domain support, and deployment controls are part of the product, not an afterthought.

🔒

Visibility Controls

Public, link-only, and private modes let users decide how visible each launch should be.

🧳

Hiring Mode

Frames projects and impact for recruiters and hiring managers who need fast, legible signal.

🏫

Admissions Mode

Repositions the same evidence toward growth, initiative, leadership, and long-term trajectory.

📎

Resume System

Separate resume pages and PDF export keep the formal document aligned with the public site.

🎨

Portfolio Models

Supports multiple design directions so the product can move beyond one fixed portfolio template.

🧱

Narrative Outputs

Timelines, scripts, trees, and structured brand artifacts come from the same underlying evidence model.

🎬 Demo & Screenshots

Verified product capture

The screenshots below were captured from a verified local preview of the current app on March 12, 2026. That was necessary because the public domain lifepage.one is currently returning a parked GitHub Pages response instead of the product.

  • Hero: positioning plus the live preview panel that explains the product loop immediately.
  • Example portfolios: proof that the output is meant to look like a launch, not a directory profile.
  • Core product: the feature surface for import, narrative, deployment, and visibility controls.

The repo README and deployment config point toward Cloudflare Workers as the intended serving path while custom-domain routing is being reattached.

🛠️ Tech Stack / Deployment

The implementation is much closer to an application platform than a marketing page. It combines ingestion, structured generation, hosted publishing, and deployment concerns in one web product.

Stack

Next.js 16 TypeScript Prisma PostgreSQL Auth.js OpenAI Cloudflare Workers R2 Playwright
  • Ingestion: axios, cheerio, puppeteer-core, and Chromium-based screenshot capture for evidence collection.
  • Generation: OpenAI-backed structured outputs for headlines, stories, case studies, and resume bullets.
  • Publishing: public profile pages, resume pages, visibility controls, and custom-domain support.
  • Deployment path: OpenNext + Wrangler workflow for Cloudflare Workers, with R2 for asset storage.
  • Quality bar: Playwright E2E coverage for auth, billing, crawl import, public pages, and export flows.