Portfolio Engineering Log: Current Technical Snapshot

This entry captures the exact state of the portfolio codebase as of 14-02-2026. The app is in active mid-stage development: core pages are usable, content flow is stable, and several planned features are intentionally postponed.

1) Stack and runtime choices

• Framework: Next.js 16.1.6 with App Router
• UI runtime: React 19.2.3 + React DOM 19.2.3
• Language/tooling: TypeScript (strict mode), ESLint 9 with next/core-web-vitals + next/typescript
• Styling: Tailwind CSS v4 via @tailwindcss/postcss
• Optimization: next/font (Geist + Geist Mono), next/image for photos
• Next config enables reactCompiler: true

The project keeps dependencies intentionally light. There is no CMS, no database, and no external API integration yet; most content is compiled in TypeScript files for predictable static-first behavior.

2) Architecture and routing

The app uses a simple route-per-page layout under src/app with a global layout wrapper, sticky header navigation, and route-level page components. Main implemented routes are /, /about, /projects, /blog, /blog/post, and /contact.

The blog detail page currently resolves content by search params (slug query string), then renders typed block nodes (heading, paragraph, quote, list, code). This keeps rendering deterministic without MDX parsing complexity.

1type BlogBlock =
2  | { type: 'heading'; text: string }
3  | { type: 'paragraph'; text: string }
4  | { type: 'quote'; text: string }
5  | { type: 'list'; items: string[] }
6  | { type: 'code'; language: string; code: string };

3) Content model and data flow

Homepage content is centralized in src/app/content.ts with typed structures and locale-aware selection. The locale model exists (en/sk), but both locales currently map to the same English content object.

• Home page consumes getHomeContent(defaultLocale)
• Blog metadata and post blocks live in src/content/blog
• Posts are sorted by date in-memory
• No markdown pipeline yet; blog content is authored directly in TypeScript

4) UX system and component strategy

Styling is built around reusable class primitives in globals.css (page-shell, section-card, section-title, button-primary, button-secondary, pill). The visual language is clean card-based UI with blue accents and subtle motion.

1const navItems = [
2  { label: 'Projects', href: '/projects' },
3  { label: 'Blog', href: '/blog' },
4  { label: 'About', href: '/about' },
5  { label: 'Contact', href: '/contact' },
6];

The one interactive client component is PhotoGallery (modal-style expanded image view, escape key handling, click-outside close). Most other routes remain server-rendered components with static content.

5) What is complete vs under construction

• Complete: global layout/nav, homepage sections, about page, projects page, blog list/detail flow, and contact UI
• Complete: typed blog block renderer including code and quote blocks
• Partial: i18n structure exists, but localized content is not separated yet
• Partial: photo modal works, full slideshow behavior is still planned
• Not implemented: contact form backend (currently UI-only with action='#')
• Not implemented: dedicated /now and /technologies pages (folders exist but are empty)

6) Intent and next engineering steps

The current direction is static-first, maintainable, and intentionally low-ops: ship clean UX and clear writing first, then add selective dynamic pieces only where they provide obvious value.

• Wire contact form through a server action or API route with validation + spam protection
• Either add a dedicated dynamic segment route (/blog/[slug]) or keep query-based routing and harden link consistency
• Split en/sk content sources and introduce language switch behavior
• Decide whether long-form writing should remain TypeScript blocks or migrate to MDX
• Add deployment and performance checks (build, lint, lighthouse) as repeatable release gates