Personal Portfolio Platform (`hyunwook.tech`)

# Personal Portfolio Platform (hyunwook.tech)

AI Summary

Purpose:

• Capture durable knowledge about hyunwook.tech, the personal portfolio,

tech blog, wiki, docs, and API monorepo under ~/hw/project.

Key points:

• The repository README describes hyunwook.tech as a personal portfolio +

wiki + document system monorepo.

• It contains multiple Next.js apps (hw-web, hw-portfolio, hw-wiki,

hw-docs), a Go backend API (portfolio-api), shared packages, and Docker Compose infrastructure.

• The project is relevant as both a portfolio item and the personal platform

that hosts or informs portfolio/wiki/docs workflows.

• Live production URLs confirmed by owner (2026-06-12): portfolio.hshouse.xyz

(hw-portfolio), docs.hshouse.xyz (hw-docs), wiki.hshouse.xyz (hw-wiki), tech.hshouse.xyz (hw-web). Traffic, user count, and production metrics are still Needs confirmation.

Relevant when:

• Generating personal project portfolio material.
• Working on personal portfolio/wiki/docs architecture.
• Comparing llm-wiki static outputs with the richer hyunwook.tech platform.

Do not read full document unless:

• You need exact app ports, command details, or service boundaries.

Linked documents:

• ai/repo-notes/hyunwook-tech.md
• ai/workspace/repos.md
• ai/wiki/projects/index.md

Open Questions

• ~~Public production URL and deployment state~~ — resolved 2026-06-12: live at

portfolio/docs/wiki/tech.hshouse.xyz (owner-confirmed).

• Whether hw-docs or llm-wiki is the current primary documentation surface:

Needs confirmation.

• Actual usage metrics, traffic, uptime, and user-facing impact: Needs

confirmation.

Details

Project role

hyunwook.tech is a personal platform monorepo. The README lists separate surfaces for a tech blog, portfolio, wiki, docs system, Go backend API, and infrastructure services. For portfolio wording, this should be framed as a personal knowledge/portfolio operations platform rather than as the same static human/portfolio output in llm-wiki.

Architecture

• apps/hw-web: Next.js tech blog.
• apps/hw-portfolio: Next.js portfolio app.
• apps/hw-wiki: Next.js wiki app.
• apps/hw-docs: Next.js document system with Tiptap-related editor

dependencies.

• apps/portfolio-api: Go backend API using PostgreSQL, Redis, MongoDB, JWT,

YAML, and crypto-related dependencies.

• apps/shared: shared exports for auth, wiki, and portfolio modules.
• infrastructure: local DB, Redis, MongoDB, and Nginx configuration.

Commands and verification

Known commands from repo metadata:

npm run lint
npm run smoke
npm --workspace=apps/hw-web run dev
npm --workspace=apps/hw-portfolio run dev
npm --workspace=apps/hw-docs run dev
npm --workspace=apps/hw-wiki run dev
docker compose up -d

scripts/smoke-test.sh validates gateway host routing and optional login-cookie behavior. Some checks require local services and host resolution.

Portfolio positioning

Suggested Korean portfolio angle:

• "개인 포트폴리오·위키·문서 운영 플랫폼"
• Highlight monorepo structure, multiple Next.js surfaces, Go API, and local

infrastructure.

• Public URLs and deployment are owner-verified (see AI Summary). Mark period

and usage metrics as Needs confirmation unless the user verifies them.