- {/*
- A named candidate rather than an abstract "you". Aarav is invented,
- and is the same person on the sample resume rendered in the 3D
- scenes, so the two surfaces describe one coherent story.
- */}
Aarav, 2026 batch. Three projects, one hackathon,
no internship yet. He has a resume he is proud of and forty applications he has heard
diff --git a/packages/frontend/src/components/ui/button.tsx b/packages/frontend/src/components/ui/button.tsx
index faebd80..e1dca45 100644
--- a/packages/frontend/src/components/ui/button.tsx
+++ b/packages/frontend/src/components/ui/button.tsx
@@ -24,12 +24,6 @@ const base = cn(
type CommonProps = { variant?: Variant; size?: Size; className?: string };
-/**
- * Renders a Next `Link` when given an `href`, a `button` otherwise.
- *
- * Cheaper than an `asChild` slot for a marketing surface, where every action is
- * either navigation or a plain button.
- */
export function Button({
href,
variant = "primary",
diff --git a/packages/frontend/src/hooks/use-media-query.ts b/packages/frontend/src/hooks/use-media-query.ts
index c51c266..a77d275 100644
--- a/packages/frontend/src/hooks/use-media-query.ts
+++ b/packages/frontend/src/hooks/use-media-query.ts
@@ -2,13 +2,6 @@
import { useCallback, useSyncExternalStore } from "react";
-/**
- * Subscribes to a CSS media query.
- *
- * `useSyncExternalStore` rather than an effect writing state: it reads the
- * browser's value at render time and avoids the cascading render that
- * setState-in-an-effect causes.
- */
export function useMediaQuery(query: string, serverFallback = false): boolean {
const subscribe = useCallback(
(onChange: () => void) => {
diff --git a/packages/styles/globals.css b/packages/styles/globals.css
index 27a138f..f8b2c0b 100644
--- a/packages/styles/globals.css
+++ b/packages/styles/globals.css
@@ -1,12 +1,5 @@
@import "tailwindcss";
-/* ---------------------------------------------------------------------------
- Milo design tokens
-
- One committed theme: deep warm ink, sand/clay neutrals for paper and copy,
- a single signal green reserved for "tracked" moments. Green never appears
- as decoration, if something is green, it represents a recorded signal.
---------------------------------------------------------------------------- */
@theme {
--color-ink-950: #060807;
--color-ink-900: #0a0d0c;
@@ -49,10 +42,8 @@
}
}
- /* A sent application leaving the laptop. Used by the story illustration. */
--animate-send-off: send-off 1.1s cubic-bezier(0.22, 1, 0.36, 1) both;
- /* Story illustration: a working bob, and a slower resting breath. */
--animate-typing-bob: typing-bob 1.6s ease-in-out infinite;
--animate-breathe: breathe 5s ease-in-out infinite;
@@ -150,7 +141,6 @@
text-wrap: balance;
}
-/* Warm grain overlay, keeps large flat ink areas from banding. */
@utility grain {
position: relative;
diff --git a/packages/ui/src/shipping-log/data.ts b/packages/ui/src/shipping-log/data.ts
index 551395a..9091b81 100644
--- a/packages/ui/src/shipping-log/data.ts
+++ b/packages/ui/src/shipping-log/data.ts
@@ -1,19 +1,6 @@
-/**
- * The public build log behind /path.
- *
- * Every entry is something that actually shipped, dated the day it shipped.
- * The page derives day numbers, totals and cadence from this array, so adding a
- * feature means adding one entry here and nothing else.
- *
- * Write these for an engineer reading over your shoulder. Name the decision and
- * the constraint, not the marketing outcome. Keep it honest: the value of
- * publishing a dated log is entirely that the dates are real.
- */
-
export type ShipStatus = "shipped" | "building";
export type ShipEntry = {
- /** ISO date, YYYY-MM-DD. The day the work actually landed. */
date: string;
title: string;
description: string;
@@ -21,8 +8,23 @@ export type ShipEntry = {
status: ShipStatus;
};
-/** Newest first. The page groups these by date for display. */
export const shippingLog: readonly ShipEntry[] = [
+ {
+ date: "2026-09-15",
+ title: "Accounts, and a signup that proves you own the address",
+ description:
+ "Register, verify by one-time code, login, refresh, logout and a current-user endpoint, layered routes to service to dao so the rules stay testable with no database and no running app. Codes are HMAC hashed with a server-side pepper before they reach Mongo, and the row keeps only a user id: an email copy and a stored expiry are both facts the users collection already owns, so expiry is derived from last sent, which is the same field the TTL index deletes on. Tokens carry a type claim that decoding checks, so a refresh token cannot be replayed as an access token, and they only ever travel in httpOnly cookies. Passwords are argon2id and deliberately never trimmed, since trimming one silently changes the credential someone typed.",
+ tags: ["Auth", "FastAPI", "MongoDB", "Security"],
+ status: "shipped",
+ },
+ {
+ date: "2026-09-15",
+ title: "Mail that refuses to fail quietly",
+ description:
+ "SMTP delivery derives from the environment: console in development, where the whole message lands in the log so signup works with no mail server, and real delivery in production, which refuses to start on console mode, a local mail catcher host, missing TLS, absent credentials, or a missing code pepper. That last check is not cosmetic, without a shared pepper every worker hashes codes differently and verification fails at random. Rate limiting surfaced its own trap: with headers enabled a limited route must also accept the response object, or it raises on the first request rather than at import.",
+ tags: ["Email", "Configuration", "Reliability"],
+ status: "shipped",
+ },
{
date: "2026-08-13",
title: "Product app, and the design system underneath it",
@@ -70,7 +72,6 @@ export type ShipDay = {
entries: readonly ShipEntry[];
};
-/** Groups the log by date, preserving the newest-first order. */
export function groupByDay(entries: readonly ShipEntry[]): ShipDay[] {
const days = new Map();
@@ -92,7 +93,6 @@ export function formatDate(iso: string): string {
});
}
-/** Stats shown at the top of /path, all derived rather than hardcoded. */
export function summarise(entries: readonly ShipEntry[]) {
const dates = entries.map((entry) => entry.date).sort();
const first = dates[0];
@@ -114,14 +114,6 @@ export function summarise(entries: readonly ShipEntry[]) {
};
}
-/**
- * What is coming, deliberately without dates.
- *
- * The whole value of a dated log is that the dates are real, so nothing here
- * claims a day. "Next" is what is actively being picked up, "soon" is queued,
- * "later" is wanted but unscheduled. A missed promise on this page would cost
- * more credibility than the promise ever bought.
- */
export type PlannedWhen = "next" | "soon" | "later";
export type PlannedEntry = {
@@ -133,11 +125,11 @@ export type PlannedEntry = {
export const upcomingWork: readonly PlannedEntry[] = [
{
- title: "Accounts and sessions",
+ title: "Sessions in the product app",
description:
- "Sign up, log in, log out, with authorisation checks on every protected route so no account can reach another's resumes by changing an id.",
+ "The auth API exists, the app does not use it yet. Session state, the verification screen the register flow already expects, and a guard that keeps signed-out visitors out of the dashboard and signed-in ones out of the login page.",
when: "next",
- tags: ["Auth", "Backend"],
+ tags: ["Frontend", "Auth"],
},
{
title: "Create a tracking link",
diff --git a/packages/ui/src/shipping-log/shipping-log.tsx b/packages/ui/src/shipping-log/shipping-log.tsx
index f1f6de7..d996820 100644
--- a/packages/ui/src/shipping-log/shipping-log.tsx
+++ b/packages/ui/src/shipping-log/shipping-log.tsx
@@ -11,23 +11,13 @@ import {
type Props = {
entries: readonly ShipEntry[];
- /**
- * `full` is the dedicated /path page: stats header and every entry.
- * `compact` is an embed, for a landing-page section that links onward.
- */
+
variant?: "full" | "compact";
- /** Caps how many entries render. Useful for the compact embed. */
+
limit?: number;
className?: string;
};
-/**
- * Public build log: what shipped, on which day.
- *
- * Presentational only. It derives every number from the entries it is given, so
- * there is no count to forget to update, and both apps render an identical
- * timeline from the same data.
- */
export function ShippingLog({ entries, variant = "full", limit, className }: Props) {
const visible = typeof limit === "number" ? entries.slice(0, limit) : entries;
const days = groupByDay(visible);
@@ -123,14 +113,6 @@ const whenStyles: Record = {
later: "border-sand-300/12 bg-ink-850/40 text-sand-500",
};
-/**
- * What is planned, with no dates attached.
- *
- * Sits above the shipped timeline so the page answers both questions a reader
- * has: what exists, and what is being worked on. Buckets rather than dates,
- * because a missed date on this page would undo the credibility the dated
- * entries below it are there to build.
- */
export function UpcomingWork({
entries,
className,