From GitHub Pages to a Next.js Portfolio

Zhejian.github.io represents an earlier stage of the personal site. It is small, static, and focused on presenting personal information and project work.

Looking at it beside the current homepage shows a useful progression: from a simple static page to a portfolio system with multiple routes, MDX writing, contact handling, and richer project storytelling.

What Changed

The early GitHub Pages style is good for speed and simplicity. It is easy to host and easy to understand.

The newer Next.js version adds structure. Routes separate homepage, about, blog, and contact. MDX turns project learning into articles. The contact page can send messages instead of only displaying links.

Product Growth

This is the natural path for many developer portfolios. The first version proves identity. Later versions need to support storytelling, case studies, writing, and hiring or collaboration workflows.

The key is not adding technology for its own sake. The technology should support clearer communication.

Knowledge Points

• GitHub Pages is excellent for simple static publishing.
• Next.js is useful when the portfolio needs routing, metadata, dynamic behavior, and content systems.
• A portfolio can evolve from a page into a personal knowledge base.
• Blog posts make projects easier to understand because they explain decisions, not only outcomes.
• Contact flows reduce friction for collaborators and recruiters.
• Design iteration should preserve speed, readability, and maintainability.
• Migrating old pages can become a chance to rethink personal branding and information architecture.

Takeaway

This repo is a snapshot of growth. It shows where the personal site started, while the current homepage shows how the same idea became a more complete technical portfolio.