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.
Each screen is one folder holding three files, all at the same level:
File
Role
DESIGN.md
The screen as a document: frontmatter, the screenshot rendered inline, then the full source in a fenced block.
code.html
The screen's source, unchanged.
screen.png
The rendered screenshot, kept separately so it can be opened directly.
The export's folder names were replaced with short, consistent ones:
Export name
Folder
noel_sabia_homepage_cv_overview
homepage
noel_sabia_overview_mobile
homepage_mobile
noel_sabia_dev_view_technical_telemetry
dev_view
noel_sabia_dev_view_mobile
dev_view_mobile
noel_sabia_life_map
life_map
noel_sabia_life_map_mobile
life_map_mobile
noel_sabia_infrastructure_ai_resilience
design_system
Why
A screen should be readable as one document without opening anything else, which
is what embedding the screenshot and the source gives. Keeping screen.png beside
the markdown as well is for looking at the picture on its own, without reading the
document around it.
The frontmatter on DESIGN.md — type, title, description, tags,
status — is also valid concept frontmatter, so these files are readable as
concepts if the mockups are ever folded into a knowledge bundle.
Notes
The export shipped DESIGN.md and nothing else for the infrastructure folder.
That folder is the design-token document, not a screen, so it deliberately has
no code.html and no screen.png.
A second, byte-identical copy of the export was deleted. Equality was checked
file by file with cmp across all 13 files before anything was removed.
Committed as docs(design): embed screenshot and source into per-screen DESIGN.md.