diff --git a/OKF_Nuxt/backend-endpoints.md b/OKF_Nuxt/backend-endpoints.md index 2649937..2963580 100644 --- a/OKF_Nuxt/backend-endpoints.md +++ b/OKF_Nuxt/backend-endpoints.md @@ -13,6 +13,9 @@ sources: - id: gateway-design resource: ../../OKF_CV_Website/architecture/gateway.md title: Gateway architecture (sibling bundle, design level) + - id: profile-export + resource: https://www.linkedin.com/in/noel-sabia-9738a4339/ + title: LinkedIn profile (exported to Profile.pdf, 2026-10-23) --- # Decision @@ -38,28 +41,65 @@ one boolean-ish answer: is the system up right now. * The gateway computes this from the cluster (are the chapter pods running). * The frontend polls this (mockup says `watch --interval=5s`; 5-10 s is fine). -## 2. `GET /api/chapters` — terminal rows and their footer counters +## 2. `GET /api/chapters` — the chapter rows The terminal lists one row per life chapter: `chapter=… status=… uptime=…% self_healed=…x`. ```json [ - { "name": "prezero", "status": "active", "uptime": 99.98, "selfHealed": 14 }, - { "name": "dreambit", "status": "active", "uptime": 99.95, "selfHealed": 8 }, - { "name": "ongoing-studies", "status": "active", "uptime": 99.91, "selfHealed": 5 }, - { "name": "42-school", "status": "finished", "uptime": 100.0, "graduated": 2023 }, - { "name": "apprenticeship", "status": "finished", "uptime": 100.0, "certified": 2021 } + { "name": "prezero", "context": "Enterprise", "status": "active", "uptime": 99.98, "selfHealed": 14 }, + { "name": "defifort", "context": "Web3 startup", "status": "finished", "uptime": 100.0, "outcome": { "label": "completed", "value": "2025" } }, + { "name": "alignerr", "context": "AI Developer", "status": "finished", "uptime": 100.0, "outcome": { "label": "completed", "value": "2025" } }, + { "name": "outlier", "context": "AI Developer", "status": "finished", "uptime": 100.0, "outcome": { "label": "completed", "value": "2024" } }, + { "name": "freelance", "context": "Freelance", "status": "finished", "uptime": 100.0, "outcome": { "label": "completed", "value": "2024" } }, + { "name": "42-school", "context": "Education", "status": "finished", "uptime": 100.0, "outcome": { "label": "graduated", "value": "2024" } } ] ``` * One chapter = one row. `status` is `active` or `finished`. +* `context` is a short display label (`Enterprise`, `Web3 startup`, + `AI Developer`, `Freelance`, `Education`), not a status and not an + endpoint. * Active chapters map to real workloads; finished ones are history entries. -* "3 Systems Active", "2 Sealed Archetypes", "Cumulative Rebounds: 27" - are **not** endpoints: count `status === "active"`, count the finished - ones, sum `selfHealed` in the frontend. +* The terminal footer totals come from `GET /api/metrics` below, not + from counting this response in the browser. -## 3. `POST /api/fall/{chapter}` — the knockdown button (later route) +## 3. `GET /api/metrics` — the terminal's numbers in one response + +The homepage terminal shows one row per chapter and a footer with three +totals. Today the chapter list lives in `app/data/chapters.ts` (from +`Profile.pdf`), while `uptime` and `rebounds` are still mock values. The +gateway must own all of it once it exists, because uptime and recovery +counts are measurements, not copy. + +```json +{ + "chapters": [ + { "name": "prezero", "context": "Enterprise", "status": "active", "uptime": 99.98, "selfHealed": 14 }, + { "name": "42-school", "context": "Education", "status": "finished", "uptime": 100.0, "outcome": { "label": "graduated", "value": "2024" } } + ], + "totals": { "active": 1, "sealed": 5, "rebounds": 14 } +} +``` + +The array above is abridged; the totals describe all six rows. + +* `chapters` uses the same row shape as `/api/chapters`. The page maps + the response into the existing `Chapter` type in one place, so + `HomeChapterRow` does not know where the data came from. +* `totals.active`, `totals.sealed` and `totals.rebounds` are computed by + the gateway from the same rows the response carries. The footer must + not recompute them client-side, or the rows and the footer can + disagree after a partial update. +* `totals.sealed` counts chapters with `status: "finished"`; + `totals.rebounds` is the sum of `selfHealed`. +* Finished chapters carry `outcome` (`graduated`, `certified`, …) + instead of `selfHealed`. +* Poll it on the same 5-10 s interval as `/api/health`; the SSE stream + below replaces both later. + +## 4. `POST /api/fall/{chapter}` — the knockdown button (later route) The core feature on the life-map page: a visitor presses "push", the chapter pod dies and recovers. @@ -70,18 +110,20 @@ chapter pod dies and recovers. * Unauthenticated by design, but rate-limited and restricted to the gateway by NetworkPolicy (sibling bundle, trust boundaries). -## 4. `GET /api/events` — live stream (later route, when it hurts) +## 5. `GET /api/events` — live stream (later route, when it hurts) Dev View and live recovery times on the life map need push updates (SSE, per the sibling-bundle design). **Deliberately not in the first -version:** polling `/api/health` and `/api/chapters` every few seconds is +version:** polling `/api/health` and `/api/metrics` every few seconds is enough for the homepage; add SSE when the dev view is actually built. # Not endpoints * Hero content (name, quote, contact bar, CV button) — static frontend content. The copy buttons read from local clipboard, no server call. -* Aggregated counters (see above) — computed in the browser. +* Per-row presentation (the `chapter=…` labels, colours, the + `self_healed=Nx` suffix) — the browser formats the numbers the API + returns; there is no endpoint per field. # Related diff --git a/OKF_Nuxt/index.md b/OKF_Nuxt/index.md index ad586d4..dbe2c05 100644 --- a/OKF_Nuxt/index.md +++ b/OKF_Nuxt/index.md @@ -9,7 +9,8 @@ released, and what was learned getting there. It is the "why" behind the config files — the configs say what, these documents say why. * [Open questions](open-questions.md) - What is still undecided for the Nuxt site. -* [Backend endpoints](backend-endpoints.md) - The smallest API the frontend needs from the Go gateway: health, chapters, knockdown, events. +* [Backend endpoints](backend-endpoints.md) - The smallest API the frontend needs from the Go gateway: health, chapters, metrics, knockdown, events. +* [Profile data](profile.md) - The LinkedIn export behind the terminal chapters, what is real vs mock, and how to refresh it. * [Future updates](future-updates.md) - Pipeline improvement backlog with effort estimates, not yet decided. * [Update log](log.md) - History of changes to this bundle. diff --git a/OKF_Nuxt/log.md b/OKF_Nuxt/log.md index f247d1d..4f41000 100644 --- a/OKF_Nuxt/log.md +++ b/OKF_Nuxt/log.md @@ -1,5 +1,12 @@ # Update Log +## 2026-10-23 (profile data in the terminal) +* **Creation**: [Profile data](profile.md) - imported the LinkedIn export `Profile.pdf` into `app/data/chapters.ts`: PreZero active; Defifort, Alignerr, Outlier, freelance and 42 finished. Each row carries a context label (Enterprise, Web3 startup, AI Developer, Freelance, Education). The terminal now shows 1 active / 5 sealed / 14 rebounds; the export has no entry for `dreambit`, `ongoing-studies` or `apprenticeship`, so those rows are gone. `uptime` and `rebounds` remain mock. +* **Update**: [backend endpoints](backend-endpoints.md) - examples and totals now match the real six-chapter list; the source frontmatter points at the export. + +## 2026-10-23 (homepage metrics contract) +* **Update**: [backend endpoints](backend-endpoints.md) - added `GET /api/metrics`: the chapter rows plus the terminal footer totals (`active`, `sealed`, `rebounds`) in one response. The homepage terminal is meant to show measurements, not mockup copy, so the gateway should own them; `/api/chapters` stays the row list for the life map. The old note that the counters are computed in the browser is gone. + ## 2026-10-20 (cheaper review model, cached installs, merged checks) * **Update**: [pr-checker.yml](../.gitea/workflows/pr-checker.yml) - the review model is now `opencode-go/claude-haiku-5-5#medium`: cheap per token and, unlike `deepseek-v4.1-flash`, it has a real `#medium` effort level (flash exposes only low/high/max). ESLint and typecheck are merged into one `checks` job with a single `pnpm install`, and the pnpm store plus the opencode binary are restored with `actions/cache@v4.1.0` (v1 cache API, so it also works on a v1-only runner). Cache keys are built from `sha256sum pnpm-lock.yaml`, the pnpm store layout (`v11`) and the opencode version in shell steps, because `hashFiles()` evaluates empty in this act runner. See [AI review setup](decisions/ai-review-setup.md) and [PR pipeline layering](decisions/pr-pipeline-layering.md). diff --git a/OKF_Nuxt/profile.md b/OKF_Nuxt/profile.md new file mode 100644 index 0000000..b8990db --- /dev/null +++ b/OKF_Nuxt/profile.md @@ -0,0 +1,82 @@ +--- +type: Data Source +title: Profile data behind the homepage +description: The LinkedIn export used for the terminal chapters, what is real and what is still mock, and how to refresh it. +tags: [profile, linkedin, chapters, data] +status: draft +generated: { by: opencode-go/deepseek-v4.1-flash, at: 2026-10-23T00:00:00Z } +verified: { by: human:noel, at: not yet } +sources: + - id: linkedin-profile + resource: https://www.linkedin.com/in/noel-sabia-9738a4339/ + title: LinkedIn profile (exported to Profile.pdf, 2026-10-23) +--- + +# Decision + +The homepage terminal is driven by `app/data/chapters.ts`. The chapter +names, statuses and outcome years in that file come from the LinkedIn +export `Profile.pdf`; the telemetry values (`uptime`, `rebounds`) are +still mock numbers until `GET /api/metrics` exists. + +# Profile facts the site uses + +* Name: Noel Sabia +* Location: Heilbronn, Baden-Württemberg, Germany +* Email: noel.sabia.05@gmail.com +* LinkedIn: +* Current headline: Working for Schwarz Group +* Current role: PreZero Deutschland, Full Stack Developer (September 2025 – present) +* Education: 42 Heilbronn (2023 – 2025) + +The hero's `System Architect · Programmer` line, the pill and the quote +are positioning copy chosen by Noel, not LinkedIn fields. The three +cards are soft skills, also not from the export. + +# Chapter mapping + +| Chapter | Context | Export entry | Terminal status | Terminal detail | +|---|---|---|---|---| +| `prezero` | Enterprise | PreZero Deutschland, Full Stack Developer, 09/2025 – present | active | `self_healed=14x` (mock) | +| `defifort` | Web3 startup | Defifort, Software Developer, 04/2025 – 07/2025 | finished | `completed=2025` | +| `alignerr` | AI Developer | Alignerr, AI Trainer, 10/2024 – 03/2025 | finished | `completed=2025` | +| `outlier` | AI Developer | Outlier, Remote Coding Expert / Freelance Writer, 03/2024 – 09/2024 | finished | `completed=2024` | +| `freelance` | Freelance | Freelance Software Engineer, 06/2023 – 03/2024 | finished | `completed=2024` | +| `42-school` | Education | 42 Heilbronn, 2023 – 2025 | finished | `graduated=2024` | + +The `context` labels are Noel's wording for the terminal, not fields in +the export. + +The terminal derives its footer from this list: **1 active**, **5 sealed**, +**14 rebounds**. The rebound count is the mock value on `prezero`; the +finished rows carry no rebound number. + +The export has no entry for `dreambit`, `ongoing-studies` or +`apprenticeship`, so those rows were removed from the terminal. It also +has no entry before 2023; if the apprenticeship belongs on the life map, +add it back deliberately instead of restoring the mockup text. + +# 42 graduation year + +The export's education range is **2023 – 2025**. The terminal shows +`graduated=2024` because Noel stated 2024 explicitly. If the export is +right, change the value in `app/data/chapters.ts` to `2025`; this is the +one open discrepancy in the mapping. + +# Not imported + +The export also contains the summary, the per-role descriptions, top +skills (Docker, Python, Go), languages (German native, English +professional) and the ETHGlobal Prague 3rd place. The homepage does not +show them yet; the life map and the CV can reuse them later. + +# Refresh + +1. Download a fresh `Profile.pdf` from LinkedIn (More → Save to PDF). +2. Update the table above and `app/data/chapters.ts`; keep the chapter + handles stable so the life-map links do not break. +3. Replace `uptime` and `rebounds` with `GET /api/metrics` when the + gateway exists; the chapter list then comes from the same endpoint. + +The PDF export is not committed; only the derived chapter data belongs +in the repository. diff --git a/app/components/home/ChapterRow.vue b/app/components/home/ChapterRow.vue index ed09914..818d1b6 100644 --- a/app/components/home/ChapterRow.vue +++ b/app/components/home/ChapterRow.vue @@ -13,13 +13,16 @@ const detail = computed(() => (isActive.value