Work · Open source · 11
This website
Can a portfolio prove its claims instead of asking you to trust them?
In 30 seconds
- Problem
- Portfolio sites tend to show screenshots and adjectives. A reviewer cannot tell which numbers were measured.
- Result
- A static site where every number carries an evidence tag and a source; Lighthouse 100 on accessibility, performance and SEO.
- My role
- Design direction, writing, build and deployment.
- measured 100 Lighthouse accessibility, performance and SEO on the home page
- measured ~100 kB total download for the home page, fonts included
- measured 0 cookies and third-party requests; analytics are cookieless and first-party
- measured 1 file holds every number on the site, each with its evidence level
- Type
- Open source
- When
- November 2026
- Role
- Design direction, content, build and deployment
- Built with
- Astro, plain CSS, Vercel
- Status
- Live · milestone 4 of 4
01In plain language
Most portfolios ask the reader to believe them. This one tries to make checking easy: every number links to the case study it comes from, every case study links to the code, and every number carries a small tag saying how it was measured.
The site follows the same idea as the projects on it. When something has not been measured yet, it says pending instead of guessing.
02The question
A recruiter gives a portfolio well under a minute. Can the first screen prove something, and can the second click show where the proof comes from?
03What I took from where
| Reference | Taken | Left out |
|---|---|---|
| An AI engineer's portfolio from my own M.Sc. cohort | Visitor router, metric cards that link to proof, a fixed case-study structure, a page for recruiters | His wording and section names |
| A Swiss architecture studio | One font, one accent, visible grid lines, numbered sections, a giant wordmark | A 34,000-pixel scroll and heavy WebGL |
| A Tokyo creative studio | A plain, dated, one-line-per-project index | A homepage drawn entirely on a canvas, unreadable to screen readers |
| A UX designer's portfolio | One contact button, repeated; a calm, friendly tone | Case studies without numbers |
04Thought process
- 01
Study
- Four reference sites
- Structure, links, psychology
- Fonts and colours measured
Learn the pattern, not the look.
- 02
Design
- Mock-ups in Google Stitch
- Layout kept, text thrown away
- Tokens: one font, one accent
Design tools invent facts. Words come from repos.
- 03
Evidence
- One data file for all numbers
- measured / synthetic / pending
- Source written next to each
No number without a file behind it.
- 04
Build
- Astro, static HTML
- Plain CSS, light and dark
- Works without JavaScript
Fast on a recruiter's work laptop.
- 05
Ship
- Push to main, live in a minute
- Lighthouse after every milestone
- Four milestones, in series
Live first, then better.
05Decisions, and what they cost
Every page is plain HTML built once. About 100 kB for the home page, fonts included.
Nothing on this site needs a server or a client-side app.
No request goes to Google, so no cookie banner is needed. Visitor statistics use a daily hash, not cookies.
In Germany, embedding Google Fonts has been ruled a data-protection problem. A banner would be the first thing a recruiter sees.
Each project has a ready flag. Until its case study is written, links point to the project's row instead.
A dead end is read as carelessness. There are no broken links on the site.
The Impressum stays offline while the postal address is missing. If it were switched on without one, the build would fail instead of publishing a blank legal page.
A legal page that looks complete but is not is worse than none.
06What broke
The design tool made up my results
The first mock-ups looked right and were full of numbers I never measured: an accuracy of 96.8% for a system that has never been scored, a model I never used, a "cost reduction" that does not exist. All the layout was kept. None of the text was.
Writing a case study found bugs in the project
Checking the Guidance Reconciliation Engine's results by hand for its case study turned up three items the engine should never have produced. They are now on that page, under "What broke".
The CV did not match the evidence
Putting the CV online meant checking every line against the code. Three claims had drifted, and the file held a street address and a photo that should not be in a public download. The published CV is the fixed version.
Small text failed contrast
The first teal was too light for 11-pixel labels. It is now darker, and accessibility scores 100.
07Still open
- An Events page: hackathons, career fairs and company visits.
- The FinBERT fusion case study, once the labelling process is confirmed.
- The Impressum, once a postal address is available.
08Reproduce it
Every number on this page comes from these commands, run in the repository.
git clone https://github.com/omkar-k0/portfolio && cd portfolio
npm install
npm run build # fails on purpose if the Impressum address is missing
npx astro preview
npx lighthouse http://localhost:4321 --only-categories=performance,accessibility,seo | File | What it holds |
|---|---|
| src/data/projects.ts | Every number on the site, with evidence level and source |
| src/config.ts | Name, availability, links and contact details |