A bilingual personal portfolio for Daniel Juyung Seo, with an English/Korean public archive and a private Firebase-backed content workspace.
?lang=en or ?lang=ko and remembered on the device.The bundled fallback portrait is stored at public/seoz.jpg. Replacing that file updates the public hero while preserving the CMS and seed-data path. The hero uses a direct impact-focused promise, a neutral editorial frame, and only the broad San Francisco Bay Area rather than a precise location. Press cards use checked-in source imagery under public/press/; their default links and bilingual labels live in src/data/press.ts and are included in the tested seed fallback. Edit the section introduction and cards from the admin Press tab; Save press publishes the changes. The mentoring and Connect sections follow the archive. Connect sits on an elevated surface to distinguish the contact call-to-action. The hero headline uses relaxed letter spacing and tighter line height for readability, with the current-focus strip below the summary. A bilingual LinkedIn link appears below the hero summary. Email contact is available in the Connect section. The portrait has no top badge. Software experience and employer tenure occupy the first row, with combined speaking engagements and open-source commits below; both rows stack on narrow screens. Header links share a compact single row with the profile name, theme toggle, and language controls on mobile.
If Firebase is temporarily unavailable, slow to connect, or has not been configured yet, the public portfolio immediately uses the included seed content instead of showing an empty archive. Live records replace the fallback as they arrive. Items with missing section metadata remain visible in a bilingual fallback group. The Archive fallback is curated from Daniel’s public profile.md: talks are grouped into compact yearly digests, while career, mentoring, open-source work, research, awards, and education retain dedicated records in English and Korean.
/admin.seojuyung@gmail.com.All other Google accounts are signed out and denied. Firebase rules independently enforce the same allowlist for every database and storage mutation.
Requirements: Node.js 22.13 or newer, a Firebase project, and a Google OAuth provider enabled in Firebase Authentication.
npm install
cp .env.example .env.local
npm run dev
Fill .env.local with the Web App configuration from the seoz-com Firebase project. Browser Firebase identifiers use NEXT_PUBLIC_ because Firebase Web SDK configuration identifies the project but does not authorize access; Firestore and Storage rules are the security boundary. Never place service-account JSON, Gemini keys, or other server credentials in a NEXT_PUBLIC_ variable.
Open the local URL printed by the development server. The default port is normally 3000.
In the Firebase console:
npm run firebase:deploy
GOOGLE_APPLICATION_CREDENTIALS when it is set and otherwise uses the account from npx firebase login:npm run seed
The seed operation is idempotent for the included document IDs. It overwrites those seed records, so run it deliberately on the intended project.
| Variable | Purpose | Exposure |
|---|---|---|
NEXT_PUBLIC_FIREBASE_API_KEY |
Firebase Web App identifier | Browser |
NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN |
OAuth redirect/auth domain | Browser |
NEXT_PUBLIC_FIREBASE_PROJECT_ID |
Firebase project | Browser |
NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET |
Portfolio image bucket | Browser |
NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID |
Firebase Web App configuration | Browser |
NEXT_PUBLIC_FIREBASE_APP_ID |
Firebase Web App identifier | Browser |
NEXT_PUBLIC_FIREBASE_DATABASE_ID |
Named Firestore database used by the web app (seozcom) |
Browser |
NEXT_PUBLIC_FIREBASE_MEASUREMENT_ID |
Optional Analytics identifier | Browser |
NEXT_PUBLIC_SITE_URL |
Canonical metadata origin | Browser/build |
FIREBASE_PROJECT_ID |
Project used by the server-side seed script | Server only |
FIREBASE_DATABASE_ID |
Named Firestore database used by the seed script (seozcom) |
Server only |
GOOGLE_APPLICATION_CREDENTIALS |
Optional local path to service-account JSON for seeding | Server only; never commit |
No Gemini integration is used. If one is added later, keep its key in Firebase Secret Manager or the hosting platform’s server-only secret store.
profile/main: bilingual identity, headline, summary, contact, portrait, social links, and optional focus with a bilingual label and up to six bilingual items (1–120 characters per language). Older profiles use the seeded focus; an empty saved list hides the strip.press/main: bilingual eyebrow, title, body, and cardIds defining the display order of up to 12 cards. press/{cardId} contains id, kind (linkedin, book, video, article), bilingual meta, title, imageAlt, image, and url. A missing or invalid configuration uses the bundled fallback; an explicitly empty card list stays empty. Save press commits the introduction, cards, order, and removals atomically. No manual reseeding is required.timeline/{id}: bilingual activity records with dates, roles, organizations, Markdown descriptions, links, labels, images, sections, and ordering. An optional bounded highlights list adds bilingual per-line notes, images, and links while preserving the Markdown description as a compatibility fallback.sections/{id}: bilingual group names, visibility, and ordering.labels/{id}: bilingual filter labels and accessible accent colors.portfolio/*: uploaded public portfolio images.npm run lint
npm run build
Security and architecture decisions are documented in DESIGN.md.
Production uses a standard Next.js static export, served by Firebase Hosting. npm run build creates out/ with separate public and admin routes. The historical Vite/Vinext/Sites files are retained for reference and are not used by the production scripts. Tailwind runs through postcss.config.mjs.
The default project in .firebaserc is seoz-com; Firestore uses the named database seozcom. Set all required NEXT_PUBLIC_FIREBASE_* values before building, and set NEXT_PUBLIC_SITE_URL=https://seoz.com. These public values are embedded in the browser build; changing them requires a rebuild. Never commit .env.local or credential JSON.
npm ci
npx firebase login
npm run deploy:hosting
deploy:hosting runs lint, builds, then deploys only Hosting. npm start serves the exported files with the Firebase Hosting emulator. Deploy backend rules separately with npm run firebase:deploy. Do not run npm run seed during deployments: it overwrites matching seeded records.
Before DNS cutover, verify https://seoz-com.web.app and /admin/, both languages, images, Google sign-in, Firestore content, image uploads, unauthorized write denial, and the bundled content fallback. Add production hostnames to Firebase Authentication’s authorized domains.
Keep domain registration and renewal at Gabia. DNS records must be edited at the authoritative nameserver provider; registration at Gabia does not by itself make Gabia authoritative. Back up the complete current DNS zone and Cafe24 files/database before retiring services. Preserve mail and verification records, including MX, SPF, DKIM, and DMARC.
If moving DNS to Gabia, first copy the full existing zone with the old website destination, then change the nameservers and verify resolution. Keep any DNSSEC delegation consistent with the new provider. Do not cancel Cafe24 if DNS or email still depends on it.
In Firebase Hosting, connect seoz.com using Advanced Setup, complete the ownership and certificate challenges, and wait for certificate readiness before changing web traffic records. Follow the current console’s exact DNS values; challenge tokens can change. Keep the ownership TXT record for renewal. Connect www.seoz.com separately and redirect it to seoz.com. Firebase manages HTTPS certificates.
Verify HTTP-to-HTTPS behavior, both hostnames, direct /admin/ navigation, sign-in, HTTPS-only assets, old URLs, and email after cutover. Keep Cafe24 and old DNS values available for rollback during propagation. Use Firebase Hosting release history to roll back application releases. Cancel old hosting only after checking its remaining DNS, mail, and file dependencies.
Run npx tsx scripts/test-press.ts to check the seed fallback and Press schema. Run npx firebase emulators:exec --only firestore --project demo-portfolio 'npx tsx scripts/test-press.ts --emulator' to verify the same payloads against Firestore rules, including public reads, card limits, safe URLs, bilingual fields, and rejected unauthorized writes. This uses a local demo project only.
Deploy the updated Firestore rules before using Save press against the live database (npm run firebase:deploy). Press text is limited to 12,000 characters per language, URLs to 2,048 characters, and card count to 12. Destination links accept HTTP(S); images accept HTTP(S), local paths, or an empty value. Image uploads reuse the existing admin-only portfolio/* Storage path and must be smaller than 5 MB. The new press collection allows public reads and restricts writes to the verified Google admin, with explicit document identity and schema validation. Storage permissions are unchanged.
The engagement counts use entries in the talks section of the existing timeline collection, which populates “Presentations, lectures & interviews.” Detailed lines take precedence over Markdown list entries, so an engagement is counted once. Records without either count as one entry. Categories are counted from detailed-line labels, with legacy parent-label fallback; categories may overlap and unlabeled entries remain unclassified. Each digest line counts once even when it describes several appearances. Counts update with Firebase snapshots and use the same calculation with seed content when Firebase is unavailable. Archive filters affect the chapter breakdown; the top statistics always reflect the full archive. Run npx tsx scripts/test-talk-metrics.ts to verify this behavior. No data schema or security rule changes are needed.
The hero uses a slightly smaller responsive headline (3.15–7.8rem) and 0.92 line height. The Press heading has a smaller responsive size. Career cards place the organization badge before the entry title, single-year badges use larger type, and generic “Various locations” / “여러 지역” labels are hidden while specific locations remain visible. Profile focus changes require deploying the updated Firestore rules; image Storage rules and paths are unchanged. Run npx tsx scripts/test-focus.ts for focus validation checks, or npx firebase emulators:exec --only firestore --project demo-portfolio 'npx tsx scripts/test-focus.ts --emulator' to include backend and identity checks.
Yearly talks entries align the year, detailed engagements, and disclosure control on the same desktop row, stacking details below on mobile. They display the year, disclosure control, and detailed engagements without repeating feature/tag badges, the yearly title, or the generic role/organization summary. These fields stay available in the CMS and continue to support filtering and search. Other archive cards retain their headings.
The public archive and its section navigator place “Presentations, lectures & interviews” directly after “Career journey” in both languages, including when live section ordering differs. Other chapters retain their configured relative order.
In Admin → Timeline, edit a speaking year to create, edit, or remove its detailed entries, then Save item. Legacy bilingual Markdown bullets are converted to editable entries on read without reseeding; Markdown links remain intact. Each entry supports bilingual title/detail, up to 12 label IDs from Labels, up to 3 links, and up to six photos (HTTP(S), local path, or image upload). Removing all entries preserves an empty year without reviving its legacy description. Years remain the public grouping; label and search filters select individual entries and recalculate the chapter metrics. Label buttons display counts across the full archive. Existing single-image entries remain compatible.
Saved speaking years use timeline/{id}.entryIds (up to 40 ordered document IDs) and an empty highlights list. Each talkEntries/{yearId}--{entryId} document contains id, yearId, and entry, with bilingual title/detail, links, optional tags, and optional images. Legacy highlights remain readable. Saving a year atomically writes its entries and removes deleted documents. Deleting a year also removes its saved entries. Individual documents keep full validation within the Firestore expression budget. Firestore validates entry identities, bilingual fields, links, label IDs, photo paths, and bounded lists. Storage continues to use verified-Google-admin-only portfolio/* writes with image MIME and 5 MB limits. Deploy updated rules with npm run firebase:deploy before saving the new fields in production. The local preview does not deploy rules. Verify with npx tsx scripts/test-talk-entries.ts and npx firebase emulators:exec --only firestore --project demo-portfolio 'npx tsx scripts/test-talk-entries.ts --emulator'.
The bundled profile has an empty headline in both languages. The hero renders its headline only when nonempty CMS content is available (or in an admin preview). Initial loading, missing profiles, and offline fallback show no default headline; the remaining seed content stays available. No schema or security rule changes are required.
Archive entry labels follow the title inline as fixed-height compact badges and wrap with the text on narrow screens. Photos occupy a separate wrapping row below the entry text and links, so gallery images never stretch label height.
The admin timeline editor starts with Section, followed by the bilingual Title fields and Date / period, before the remaining item fields.
On mobile and tablet (below the lg breakpoint), the hero portrait appears before the headline and introduction. At desktop widths, the introduction stays on the left and the portrait on the right. The portrait appears once in the document and precedes the introduction in reading order.
Header and footer name labels use Admin → Profile → Name, selecting the English or Korean field for the active language. Live profile updates and the bundled profile fallback use the same localization path; no schema or security rules change is needed.
On mobile and tablet, the location/leader line sits above the portrait and the current-role panel occupies its own row above the photo without covering it. Desktop keeps the location above the left introduction and the role overlay at the bottom of the right portrait.
The mobile header is a single 64px row containing the localized name, navigation, theme toggle, and language controls. Navigation can scroll horizontally on narrow screens without adding a second row; desktop retains the 72px header.
In the admin timeline editor, each detailed line has Move up and Move down buttons, including keyboard access and disabled boundary controls. Reordering moves the complete bilingual entry with its labels, photos, and links; Save item publishes the chosen order through the existing ordered highlights/entry IDs. The photo picker uses an Upload photo button next to Add photo URL, disabled during uploads or at the six-photo limit. Upload results follow the entry identity if a line is removed or reordered. These controls reuse the current schema and security rules.
Archive detailed-entry titles use the primary ink color, extra-bold weight, and responsive 16–18px type with 28px line height to distinguish them from descriptions and compact labels.
Markdown links within detailed-entry titles open in a new tab with noopener noreferrer, keeping the portfolio open. Titles continue to use react-markdown without raw HTML support.
The localized header name uses bold 14px type on mobile and 20px on desktop, giving the personal identity more prominence within the existing compact header.
Timeline items support up to six photos via Item photos in the timeline editor (URL or upload, with individual removal). Public item photos appear beneath the summary and open the same bilingual modal viewer as detailed-line photos. The optional timeline.images array takes precedence over the legacy imageUrl; an empty array hides photos, while records without it retain their existing thumbnail as a single-photo gallery. Saving validates the six-photo limit and HTTP(S)/local URLs, mirrored in Firestore rules. Storage uses the existing admin-only image path and 5 MB limit. Deploy Firestore rules before saving item galleries in production.
Admin Timeline groups records by section in configured section order, with bilingual section headings and item counts. Each group retains item order and supports moving records up or down within that group; boundary buttons are disabled. Unknown or missing section references remain visible under Other / unassigned (기타 / 미지정). Grouping includes hidden public sections so administrators can still manage their records. This uses the existing section and order fields without schema or security-rule changes.
The software-experience statistic keeps its duration together on one line: “30+ Years” in English and “30년 이상” in Korean, with the software-experience label right-aligned at the right edge of the cell, matching the other statistics. The label may wrap below on narrow columns while the duration stays on one line.
Korean Google and startup tenure values use “년 이상” (for example, “11년 이상” and “6년 이상”); English retains the plus suffix. Google tenure remains calculated from March 2015. Korean tenure values use responsive type in a two-column layout: Google tenure stays on the left, while Samsung and startup tenure are grouped on the right with right-aligned values and labels.
Engagement statistics use detailed-line label IDs rather than title text: lecture, presentation, talk, panel, roundtable, or interview → talks/lectures/panels/roundtables/interviews; interview or media → interviews/media; panel or roundtable → panels/roundtables; mentoring → mentoring sessions. Multiple matching labels count once per category, and categories can overlap. Each nonempty line counts once in total engagements even without a category label. Missing line tags inherit parent labels for legacy compatibility; an explicit empty list does not. Legacy Markdown and standalone items use parent labels. No schema or security-rule changes are needed. Validate with npx tsx scripts/test-talk-metrics.ts.
The public speaking metric combines talks, lectures, presentations, panels, roundtables, and interviews, counting each line once across these labels. Its English label is “Talks, lectures, panels, roundtables & interviews” and its Korean label is “발표·강연·패널·간담회·인터뷰”. The separate panel/roundtable tile is removed from both statistics areas. The archive breakdown shows only the combined speaking metric; the hero places it beside open-source commits.
The hero statistics use two columns per row: software experience and employer tenure above, combined speaking engagements and open-source commits below. The interviews/media tile is removed. On narrow screens the four cells stack in that reading order; each value keeps its localized label.
Hero statistic accent values share clamp(2rem, 3.2vw, 3rem) (32–48px with a default 16px root), including software duration, Google tenure, speaking count, and commits. Supporting labels and tenure figures use larger type for readability. Employer tenure keeps Google left and supporting experience right; cells allow wrapping where needed on narrow screens.
The combined count reads only talks timeline records. Highlights take precedence over legacy Markdown bullets; records without either count as one standalone title. Empty entries are skipped, translations count once, missing highlight tags inherit parent tags, and explicit empty tags remain unclassified. The hero uses the full timeline while the chapter uses filtered records. The chapter displays the exact computed category count without a “+” suffix; its header also displays an exact count of all nonempty engagements regardless of category in both languages. Generic media tags alone do not enter the combined count.
The Korean software-experience label (“소프트웨어 경력”) stays on one line without a fixed maximum width. The statistics cell can wrap the label below the duration on narrow screens.
Supporting English employer tenures align to the right with a compact gap between each value and label. The Korean Samsung duration includes its unit (“6년”); Korean supporting tenures retain their right-aligned stacked layout.
Timeline Save item keeps the editor open and displays saving, success, or error feedback in its footer. Close dismisses the editor. New items retain their generated document ID for subsequent saves, and saved yearly entry IDs are retained so later deletions remove the correct child records. Edits made while a save is pending stay in the draft. No schema or security-rule changes are required.