This repo powers the GitHub Pages version of my portfolio. I wanted something light, easy to update, and structured enough that projects and writing did not blur into one stream.
At a glance
- Stack: Jekyll, Liquid, Sass, kramdown, Rouge
- Type: Static portfolio site
- Use: Case studies, blog posts, and contact information
- Status: Ongoing
What it does
The site separates case studies from blog posts, keeps layouts reusable, and stays easy to host because everything is generated ahead of time. That makes it a good fit for a portfolio that changes in bursts rather than every day.
How it is organised
Content lives in _posts and _casestudies. Layouts and includes handle the shared markup, while _config.yml defines the collection and the site settings. It is a fairly standard Jekyll setup, which is part of why it remains easy to work on.
Why it still works
- Keeping case studies separate from blog posts makes the site easier to scan.
- The static build keeps pages quick and uncomplicated.
- Code highlighting and Markdown support are enough for technical writing without much ceremony.
What I would improve
- Clearer landing-page copy.
- Better front matter for sharing and search.
- Stronger navigation between related case studies.
