49 lines
1.5 KiB
Markdown
49 lines
1.5 KiB
Markdown
---
|
|
type: Frontend
|
|
title: Frontend
|
|
description: Nuxt site generated to static files and served by the gateway, with three audience layers fed by one SSE stream.
|
|
tags: [architecture, nuxt, design]
|
|
status: stable
|
|
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-11T12:15:30Z }
|
|
---
|
|
|
|
# Build
|
|
|
|
`nuxt generate` produces static, prerendered files. A multi-stage Docker build
|
|
runs it in a Node stage and copies the output into the gateway's Go stage for
|
|
`go:embed`. No Node process runs in the cluster.
|
|
|
|
# Layers
|
|
|
|
| Layer | Audience | Content | Needs live cluster |
|
|
|---|---|---|---|
|
|
| 0: First screen | HR | Name, role, contact, PDF CV download | No |
|
|
| 1: Life map | Non-technical | Chapters in plain words, "Push this chapter", story cards | Yes, degrades to static |
|
|
| 2: Dev view | Developers | Raw SSE events in a `<pre>` | Yes |
|
|
|
|
# Content
|
|
|
|
Chapter text (title, dates, story, setback, recovery, lesson) lives in the
|
|
Nuxt repo as one data file. The key is the chapter name, the same value as the
|
|
pod label `cv.noelsabia.dev/chapter`. The gateway knows nothing about stories.
|
|
|
|
# Behavior without the live stream
|
|
|
|
If `/api/events` fails, the life map renders from the data file with a small
|
|
"live cluster offline" note. No error page.
|
|
|
|
# Plain-word states
|
|
|
|
| State | Shown as |
|
|
|---|---|
|
|
| Completed | finished |
|
|
| Running, Ready | active |
|
|
| Running, NotReady | unfinished |
|
|
| CrashLoopBackOff | failed, lesson learned |
|
|
| Restarting after a push | recovering |
|
|
|
|
# Design
|
|
|
|
Terminal feel, navy `#1A3D64` and white, logo with a "broken pieces" look.
|
|
Drafted with Stitch prompts.
|