A portfolio platform that turns journalism, shipped apps, interactive case studies, and supporting media into one coherent editorial product.
Executive Summary
Anıl Karaca is a portfolio website designed as an editorial product system, not a brochure. The project had to reconcile several modes of work at once, making apps, journalism, investigations, and documentary material feel like one body of work instead of separate identities stitched together in the nav.
Role
Information architecture, content modeling, visual direction, Astro implementation
Impact
Turns a broad body of work into a portfolio people can scan, understand, and trust quickly.
Core system
Portfolio platform
Built as a durable content system instead of a static personal homepage.
Content model
Multi-collection
Projects, articles, and videos all live inside one structured archive.
Rendering model
Astro + islands
Mostly static output with React used only where interactivity adds value.
Distribution layer
SEO + OG
Structured metadata, social cards, and content-specific routes are built into the system.
Context & Problem Space
Personal portfolios often collapse under mixed disciplines. A site that includes reporting, civic analysis, consumer apps, and case studies can easily become fragmented, repetitive, or difficult to navigate. This project was built to solve that problem by giving the work a shared architecture, consistent visual language, and a content model that makes different formats feel related rather than forced together.
Reporting Workflow
Article & Visual Analysis
This project is less about a single landing page and more about portfolio architecture. The site had to behave like a flexible editorial system while still presenting apps and product case studies with enough clarity to feel commercial and current.
The central decision was to avoid splitting the work into disconnected mini-portfolios. Instead, the site treats journalism, apps, investigations, and documentary material as related proof of one way of working: framing complex problems, designing an interface around them, and shipping the result with enough structure to last.
Astro and MDX make the content layer manageable, while typed collections protect the structure of projects, articles, and videos. Shared layouts let new work inherit the same rhythm instead of forcing every addition into a fresh page design. That is what keeps the archive coherent even as the subject matter changes.
This case study matters because the site is also a product in its own right. It demonstrates content architecture, frontend system design, editorial judgment, and the ability to turn a complicated professional story into a navigable digital experience.
Selected adjacent work that extends the same problem space from a different angle.
Project case study
Mar 20, 2026
A database-backed restaurant website that combines premium brand presentation with multilingual, maintainable menu management.
Role: Product direction, UI implementation, Next.js architecture, database-backed menu system
Impact: Turns a visually refined restaurant site into an operational product the team can update without rebuilding the frontend each time.
Project case study
Mar 26, 2026
A specialist healthcare website that blends service discovery, patient-friendly content, and appointment-oriented navigation.
Role: Website structure, service architecture, patient-facing UX framing, digital delivery
Impact: Turns specialist expertise into a clearer and more trustworthy online entry point for patients.