Moaaz.

Colophon

How I Built This Site

A short tour of the stack behind moaaz.be, what powers the pages, how the content is structured, and how it gets to the public internet.

This portfolio is a small content-driven app. The home page is a one-pager that previews the most important work; every project, hackathon, and tech-and-meet write-up has its own dedicated route so it can be linked, indexed, and shared on its own.

Framework & Styling

Content Pipeline

Hosting & Version Control

How it's organised

  • src/content/posts/*.mdx: blog posts (projects, hackathons, tech-and-meet sessions, milestones).
  • src/content/projects/*.mdx: project case studies linked to from the home page.
  • src/data/*.ts: small typed data files for identity, languages, skills, and contact links.
  • src/lib/content.ts: loader that reads MDX, parses frontmatter, computes reading time, and surfaces related posts.

Tooling principles

  • Static by default. Every page is pre-rendered at build time, fast, cacheable, and cheap to host.
  • Content as files. Posts are MDX, not a database editable in any text editor, diffable in Git, no CMS lock-in.
  • Accessible defaults. Real headings, alt text on every image, focus rings, and reduced-motion respected.

Source code lives on GitHub: github.com/TwoEazy.

Deployed to Vercel on every push.