Problem and scope
A list of projects does not explain my role or technical decisions. I built a portfolio that connects project problems, implementation evidence, and verification while distinguishing service status and next steps. It is currently running as a beta.
Implementation and decisions
I connected Nuxt/Vue multilingual responsive pages with Nitro APIs and SQLite storage for posts, contact requests, and survey responses, together with a Coolify home-server deployment.
Career and service records remain content files for Git review and translation history. Posts use SQLite and the existing Markdown renderer so publishing does not require a build. The storage boundary follows how each type of content changes.
Search and operations
Korean, English, Spanish, and Japanese pages share a content structure. Canonical links, hreflang, JSON-LD, sitemaps, and Markdown responses use that content. Contact requests are checked for same origin, stored in SQLite, and delivered by email. Analytics loads after consent; an anonymous footer survey collects NPS responses.
Verification and limits
Content checks, type checks, automated tests, and production builds verify changes. Uncollected MAU, retention, and NPS remain pending. The archive is free and non-commercial, with no advertising in use. This demonstrates connecting UI, content models, APIs, search, and operations; it is not a claim of measured audience growth or performance improvement.