Web Pages
The group’s public and internal web properties at a glance
| Site | Role |
|---|---|
sbalci.github.io |
Personal / group landing |
drozlembalci.github.io |
Co-lead’s personal site |
MemorialPath.github.io |
Memorial Pathology public site |
| Site | URL | Source |
|---|---|---|
| Personal / group landing | https://serdarbalci.com | sbalci.github.io |
| Research portal (this site) | https://research.serdarbalci.com | research |
| Memorial Pathology | — | MemorialPath.github.io |
| Patoloji Atlası | https://patolojiatlasi.github.io | patolojiatlasi.github.io |
| Dr. Özlem Balcı | — | drozlembalci.github.io |
| Who Writes Who | — | whowriteswho.github.io |
Turkish-language content repositories
patoloji-hakkinda— pathology explainers.patoloji-ve-bilisim— pathology and informatics.rutinde-dijital-patoloji— digital pathology in routine practice.patoloji-bilgi-yonetim-sistemi— LIS / information-system notes.konsultasyon— consultation tracking site.
Outreach
Technical conventions
- All public sites use Quarto (or Jekyll for the oldest properties).
- Source lives in the repo; the built
_site/is published by CI. - Do not commit sensitive patient-identifiable content — these sites are public.
- Cross-link by role, not by URL — if a URL moves, only one entry in this table needs updating.
Decision flow: where should a new public page live?
- Research update, methods note, technical writeup → this portal (
research). - Teaching case with images →
patolojiatlasi.github.io(see atlas.qmd). - Longer Turkish-language explainer →
patoloji-hakkindaorrutinde-dijital-patoloji. - Informatics essay / LIS writeup →
patoloji-ve-bilisim. - Personal landing / CV →
sbalci.github.io.
Never start a new public site before checking whether an existing one already covers the audience.