Back to Projects

Personal System Site

resume-log-site

A personal site for project case studies, engineering notes, and a focused hiring view, with content maintained in the repository.

Role: Solo Developer

Highlights

Next.jsReactTypeScriptTailwind CSSshadcn/uiVercel
  • Built shared project pages around problems, implementation choices, results, and lessons.
  • Kept projects, notes, and current focus in a typed local content model.
  • Created a separate hiring view with work history, grouped skills, and selected project evidence.
  • Reused theme tokens and shared components for typography, surfaces, and responsive layouts.

Problem

A short portfolio summary can show what was built while losing the constraints and decisions behind it.

The site needs to support hiring without making every project and note read like a CV entry.

Approach

Keep project case studies, short notes, and the hiring view as distinct ways to browse the same work.

Store published content alongside the code so changes can be reviewed without a separate content backend.

Use shared typography and surface styles so the interface supports reading without adding competing visual layers.

Result

The site provides project write-ups, short engineering notes, and a hiring page through shared local content and reusable UI components.

Implementation

Content and navigation

  • Built Home, Projects, and Notes with Work as a secondary hiring entry.
  • Defined shared project and note types backed by an en-AU JSON content file.
  • Rendered project details around problems, approaches, implementation, results, and lessons.

Interface and hiring view

  • Used Next.js, Tailwind, and shared UI components with theme-based colours and surfaces.
  • Added an internally scrollable Journey timeline with reduced-motion support.
  • Grouped hiring-page skills by area, selected representative projects, and made longer role descriptions expandable.

Publishing and maintenance

  • Kept project links outbound and removed runtime GitHub statistics and external note loading.
  • Added local sharing images, page metadata, analytics, and performance insights.
  • Used the same content source for home-page summaries, project pages, and the hiring view.

Lessons

  • Local content removes service dependencies but still needs deliberate editorial maintenance.
  • A useful case study explains constraints and implementation choices rather than relying on a long technology list.
  • A hiring page can be concise without replacing the broader identity of the site.