Typography v2: Tektur, fluid type, and pixel craft
A catalog of 51,000 servers is a wall of text. We rebuilt the type system around a display font with Cyrillic support, fluid sizing, and a consistent pixel-art language.
A directory site lives or dies by its type. Ours had drifted into a zoo of text-4xl sm:text-6xl one-offs. We rebuilt it.
Tektur for display
Headings now use Tektur — a geometric display face with real Cyrillic coverage, which matters for a bilingual (EN/RU) product. Body stays on a clean sans; mono falls back to JetBrains Mono on Cyrillic where the pixel mono lacks glyphs.
Fluid type, not breakpoint soup
Heading sizes are fluid tokens built on clamp() — text-display-hero, text-display-xl, text-display-lg. One token scales smoothly from phone to ultrawide instead of jumping at breakpoints. We also stopped using ultra-tight line-height on headings (it made multi-line titles collide) and settled on a readable 1.05.
A pixel language
The brand is a pixel aesthetic, so the supporting art should be too. Feature icons, the mascot, and decorative elements are generated pixel art with a consistent palette (neon magenta / cyan / lime), bold outlines, and crisp image-rendering: pixelated. Open Graph images got the same treatment so shared links look intentional.
Why bother
Trust. A catalog asks you to install code into your AI assistant's session. If the page looks sloppy, you do not trust the listing. Consistent type and art are not decoration here — they are part of the security story.
Browse it at unyly.org.