ePortfolio 2026

The Problem

The prior portfolio was built around university robotics. Hiring conversations needed a different public site: one that presents digital-transformation work, keeps enterprise, personal, and academic material in separate places, and can be scanned in a short recruiter pass.

A CV alone does not show how a portal is structured or how an operations workflow was designed. The site had to carry case studies, experience, and a clear next step — download the CV or get in touch — without mixing client-sensitive detail into a public page.

Purpose and use

This site is the product. A visitor lands on Selected work, opens a case study, checks Experience and Skills, optionally asks the portfolio assistant, then downloads the CV or uses Contact.

• Information architecture: Work, Experience, Skills, About, Side projects, Academic, and Contact — each section has one job so a short visit still reaches the right page.
• Enterprise case studies: Architecture and outcomes without client-identifying detail; reusable detail-page template for problem, approach, and result.
• Side projects: Personal live builds (expense tracker, cycle health, this site, the portfolio assistant) with stack and architecture shared openly.
• Academic archive: University robotics work kept off the hiring homepage so it does not compete with current professional work.

Core stack: Semantic HTML5, CSS custom properties, vanilla ES6+ (scroll-spy, tabs, lightbox, page transitions), self-hosted Inter and Font Awesome, static files on GitHub Pages with a custom domain.

The Outcome

builtbyroger.com is a single hiring-facing presence: four enterprise case studies, live personal builds, an academic archive, an on-site assistant grounded in site content, and a CV download.

Recruiters can review a project, confirm the experience timeline, and reach out without leaving the site. The same templates are reused when a new case study or side project is added.