docs(okf): add Nuxt knowledge bundle in OKF v0.2
Record the design decisions behind the Nuxt site as an OKF v0.2 bundle: dev container shape, build layer order, build context filter, repository and compose layout, and the mockup layout, plus the open questions. Conformant per the spec: every concept carries a non-empty type, the reserved index and log files follow their structures, and every internal link resolves.
This commit is contained in:
1 parent
5caa3457aa
commit
8fa078707c
9 files changed
+390
No files matched your search
@@ -0,0 +1,38 @@
|
||||
---
|
||||
type: Open Questions
|
||||
title: Open questions
|
||||
description: Decisions still to make for the Nuxt site, with what needs each answer.
|
||||
tags: [decision, open]
|
||||
status: draft
|
||||
generated: { by: opencode/deepseek-v4.1-flash, at: 2026-10-18T12:41:52Z }
|
||||
---
|
||||
|
||||
| Question | Needed by | Default if nobody decides |
|
||||
|---|---|---|
|
||||
| Shape of the production image: a runnable Node server, or static `.output/public/` files for the gateway to embed | the next Dockerfile step | None. The empty `Dockerfile` stays empty. |
|
||||
| How the compose service mounts the source: the whole repository plus a volume for `node_modules`, or only the directories that get edited | finishing `Local_Development/docker-compose.yml` | None. The compose file is not yet valid. |
|
||||
| Which pnpm version the production image pins | writing the production image | The same as dev, 11.26.0. |
|
||||
| Whether these decisions stay in this bundle or fold into the sibling `OKF_CV_Website` bundle, which already describes the frontend at design level | after the production image exists | None. |
|
||||
|
||||
# The mount trade-off, in detail
|
||||
|
||||
Measured on the whole-repository mount:
|
||||
|
||||
* An anonymous volume is created once. After a dependency change the stale
|
||||
contents persist unless the volume is renewed, and the renewal command has not
|
||||
been tested.
|
||||
* Docker creates an empty, root-owned `node_modules` directory in the repository
|
||||
on the first run, unless that directory already exists.
|
||||
|
||||
The alternative — mounting only the directories that get edited — removes the
|
||||
volume, the renewal step and the root-owned directory entirely, and keeps `.nuxt`
|
||||
inside the container rather than in the working tree. It costs one compose line
|
||||
per top-level directory, so a new directory silently fails to appear in the
|
||||
container until the compose file is updated.
|
||||
|
||||
# Related
|
||||
|
||||
The Nuxt frontend is described at design level in `OKF_CV_Website`, in
|
||||
`architecture/frontend.md` and `decisions/static-nuxt-in-gateway.md`. Those
|
||||
documents state that the site is generated to static files and embedded in the
|
||||
gateway image, which is an input to the production-image question above.
|
||||
Reference in new issue
Block a user