alikoker.com.tr
My personal website, developed and maintained as a long-running software project that connects technical writing, projects, education, professional experience, academic outputs and open-source work in one information architecture.
alikoker.com.tr is the personal website project I have developed through successive versions since 2007. It began as a single place to publish my work, but over time it became a technical archive that connects articles, projects, education, professional experience, an engineering Wiki, academic publications and open-source outputs.
alikoker.com.tr is a long-lived web application in which content modeling, URL continuity, search, bilingual publishing, references and preservation of historical records are software-design concerns alongside the visual interface.
Content Model and Information Architecture
Different content types serve different purposes. A project page records work I actually built. A technical note develops theory and implementation details. An experience page provides the professional context in which a technology or engineering constraint was used. The Wiki provides shared terminology across those pages.
Keeping these roles separate reduces the need to repeat the same generic explanation everywhere and makes it possible to build a real topic graph. A performance article can connect to an architectural concept, which can then connect to a project or professional context where that concept became concrete.
Turkish and English Publishing
The Turkish and English corpora share the same technical facts, while terminology and exposition are written naturally for each language rather than copied mechanically.
Explicit translation relationships in the data model also make the pairing between the two versions unambiguous.
Technical Sources and Provenance
Where appropriate, content is connected to primary documentation, standards, academic publications, source repositories and DOI records. The purpose is not to add references for their own sake, but to keep a verifiable technical claim, software artifact or academic output connected to its source.
Historical publication dates are also kept distinct from later revisions. A page originally published years ago and technically reviewed in 2026 carries two different pieces of provenance.
Search and Internal Linking
As the archive grows, navigation menus are no longer sufficient. Search, topic relations and contextual links become part of the information architecture.
Internal links connect a technical discussion to the concept, project or broader reference that naturally continues it, particularly across long course notes, focused engineering articles and Wiki concepts.
Interface and Usability
Responsive layout, keyboard usability, readable typography, information density and reliable client behavior are part of maintaining the site as software. I discuss those principles separately in UI/UX Engineering in Web Applications.
The Site as a Long-Lived Software Project
alikoker.com.tr is not a one-time website build. Its data model and content structure continue to evolve as my engineering work, academic output and technical writing change.
I therefore maintain the site itself as an engineering artifact: preserve existing behavior, add new requirements without breaking old URLs, reduce technical debt and keep content connected to evidence rather than rewriting history.
