Portfo — this site
Hiring-facing site: Astro 5, RU/EN on physical routes, GitHub heatmap from the API, structured data, open source.
- Astro 5
- TypeScript
- GitHub API
- SEO
Portfo: the site as a product
This site is my proof-of-work and the only public repo among the projects shown. I built it myself and keep iterating — copy, cases, architecture.
The class of problem
Most portfolios go stale in a month: GitHub activity doesn’t update, SEO is broken, projects are a list of names without context. I wanted a site that stays current on its own and gives a hiring manager enough depth to see how I think, without opening 10 different links.
What’s inside
- Bilingual on physical routes.
/ru/and/en/are fully indexable, not JS-swapped content. - Live GitHub activity. GitHub API with build-time cache, the heatmap and repo metadata refresh on every build.
- Structured cases. MDX lets cases be product pages, not markdown blobs.
- Structured data. JSON-LD for Person and ProfilePage, sitemap, robots, llms.txt.
Stack
Astro 5, TypeScript, MDX, GitHub Actions, GitHub Pages.
What this case shows about me
The site is itself the case study. The repo is open: RebSem/portfo. You can see how I structure data, separate content from logic, and organize CI/CD. If something on the site raises a question, most answers are in the repository.