Why it exists
Portfolio sites that are static files and stale within a month
A portfolio built as hardcoded pages stops being accurate the moment anything changes, and updating it means a code change and a deploy. Most also ship as client-rendered apps, so search engines and answer engines receive an empty page and index nothing worth reading.
- Content baked into source, so every edit is a code change
- Client-side rendering leaving crawlers and answer engines with an empty shell
- No structured data, so nothing machine-readable about who the site is about
- Chat widgets bolted on that cannot answer anything specific
What it does
A portfolio that runs like a product
The site you are reading. Every piece of content is served from Postgres through an admin console I built, rendered on the server so crawlers get the real thing, and described with structured data. The assistant in the corner answers questions about my work using tool calling against the same database.
Admin console over Postgres
Profile, projects, posts, skills and per-page SEO all editable without touching code
Server-rendered content
Content is loaded on the server, so crawlers and answer engines receive the real page
AI assistant with tool calling
Answers questions about my work by querying the live data, with fallback across models
Structured data and llms.txt
Schema.org output plus a generated plain-text summary for language models
Visitor recommendations
Anyone can leave one without an account, with a server-enforced fifteen-minute edit window
Instant publishing
Saving in the admin console revalidates the affected pages straight away
Screens
Built with
- TypeScript
- Next.js
- React
- Tailwind CSS
- PostgreSQL
- Supabase
- Mistral AI
- Vercel
Outcome
Every profile detail, project and post on this site is edited from one admin console and rendered on the server, so search engines and answer engines read the real content.