Type to search. Arrow keys to move, Enter to open, Esc to close.

All projects
Live, maintained (2026)2026

Portfolio Site

A bilingual, searchable knowledge portfolio

A static Astro site in English and Hungarian that presents projects, technology notes and research together with their connections, with client-side search and a knowledge graph, without a server or third-party services.

languages
2
content collections
4
third-party services
0
Lighthouse CI categories checked
4
Goal
Show not only finished projects but the knowledge behind them: which technologies a project uses, which language implements them and what research informed the decisions, in two languages and on free static hosting.
Solution
Content lives in JSON content collections validated by schemas; every entry has both language versions. Each page is one shared view with two thin route wrappers. A search index is generated per language at build time and loaded on first use, and the knowledge graph is built from the same collections. GitHub Actions deploys the site and runs Lighthouse CI.
Result
A live site where adding one content file updates the list pages, the detail page, the knowledge graph and the search index. Search works without accents, with typos and with Hungarian suffixes.
  • Schema-validated content: a broken entry fails the build instead of rendering empty fields
  • Global search (Ctrl/Cmd+K) and per-section search from one prebuilt index per language
  • Knowledge graph generated from content relations, with search highlighting and reduced-motion support
  • hreflang pairs, JSON-LD, sitemap and a language suggestion banner that never redirects
  • Lighthouse CI on every push and pull request

How it works

Projects, technologies, research and certificates are content collections. Relations are stored as identifiers, so a project points to the technology notes it uses and a research note points to its project. The list pages, detail pages, search index and knowledge graph are all generated from these relations at build time.

Quality checks

The build validates every content file against its schema. A key-parity check keeps the English and Hungarian strings in sync, and Lighthouse CI checks performance, accessibility, best practices and SEO against fixed thresholds.

Technology nodes

Related research