Personal Portfolio Platform

Problem

The engineering problem

A personal site can become a pile of disconnected pages quickly. The goal here is to create a system that presents engineering work clearly while staying fast, maintainable, and easy to extend.

Approach

Technical approach

• Use Astro for fast static pages and a low-JavaScript baseline.
• Use MDX for technical writing so articles can include reusable components and richer content blocks.
• Keep visual language consistent across home, blog, about, project index, and case-study pages.

Architecture

System shape

• Astro owns page routing, static generation, content rendering, and optimized assets.
• Tailwind and shared CSS tokens provide the site-level design system.
• The deployment path is shaped for a VPS workflow with repeatable builds and clear operational ownership.

Delivery

Delivery notes

• The site is structured around small page modules and shared data where content appears in multiple places.
• Build verification catches routing, content, and image issues before deployment.
• The design evolves through reusable page patterns rather than one-off page-specific styling.

Outcome

What this demonstrates

• A cohesive personal platform for projects, technical writing, and professional positioning.
• A practical Astro reference for MDX, open graph output, RSS, sitemap, and static delivery.
• A foundation for future project writeups, newsletter flows, and richer engineering notes.

Next

Next steps

• Add more project screenshots or architecture diagrams as each project matures.
• Connect newsletter or subscription flows when the writing cadence is stable.
• Expand project detail pages with metrics, demos, and deployment notes.