ツ When a Broken Bookmark Became an Open-Source Tool

How a broken bookmark led to building an open-source Unicode icon directory in a single day. No backend, no database, no ads — just a static site and a JSON file.

• 4 min read
ツ When a Broken Bookmark Became an Open-Source Tool cover illustration

Table of contents

The bookmark that broke

On November 18, 2026, I clicked an old bookmark to utf8icons.com — a directory I used to rely on for finding native Unicode symbols to drop into web projects as lightweight, dependency-free icons. No FontAwesome, no SVG bundles, just raw UTF-8 characters styled with CSS.

The home page loaded. Everything else didn’t. Every category link, character page, and search result returned the same thing:

“Whoops, looks like something went wrong.”

The classic Laravel 500. Every internal URL was broken.

A quick diagnostic revealed why: the server had started URL-encoding its own PHP front controller, generating paths like index%2Ephp/character/9200/alarm-clock instead of clean routes. Web server rewrite rules were misconfigured. Even manually fixing the URLs didn’t help — the Laravel app couldn’t reach its database, so every page returned 500. The home page survived only because it was cached.

Interestingly, a hyphenated twin — utf8-icons.com — was alive and redesigned, marked “BETA”. But the original, the one Google ranks, the one people have bookmarked for years, was silently dead with no redirect.


The irony

What broke utf8icons.com wasn’t a complicated failure. It was an ordinary one: PHP couldn’t talk to MySQL, and the rewrite rules drifted. For most sites that’s a bad afternoon. For this one, it was existential — because all it ever did was serve a lookup table for data that hasn’t changed in decades.

A Unicode icon directory is a uniquely static thing. The Unicode Consortium publishes its entire character database as plain text files, free and public domain. There are no users, no sessions, no writes. The whole dataset of useful symbol characters fits in a JSON file smaller than most hero images.

The original site chose a stack with five moving parts — PHP runtime, MySQL, Laravel, web server, rewrite rules — to serve what is fundamentally a read-only lookup table. Each layer was a liability. Eventually one broke.


The build

I decided to replace it. I called it Open UTF-8 Icons, published it at utf8.a3k.me, and open-sourced everything under The Unlicense (full public domain — no attribution required, no strings attached).

The stack was chosen to be the antithesis of what failed:

LayerChoice
RuntimeBun
FrameworkSvelteKit + Svelte 5
StylingTailwind CSS v4
DeploymentCloudflare Pages (static, global CDN)
PWAHand-rolled service worker

Zero runtime dependencies. The package.json has only devDependencies. The production bundle is compiled Svelte + Tailwind + a packed Unicode dataset.

One rule shaped the whole design: every UI icon must be a native UTF-8 character. The search icon is 🔍. The copy button is 📋. The theme toggle is ☀ / ☾. The logo is ツ. A Unicode icon directory that eats its own cooking.


Under the hood

Dataset: A Bun script downloads UnicodeData.txt and Scripts.txt from the Unicode Consortium, filters ~3,965 useful symbols across 22 categories, enriches each with HTML entities, CSS/JS/URL escapes, and outputs a single icons.json. The packed wire format (pipe-delimited rows, dictionary-compressed names) brings it down to ~40 KB gzipped from ~1.14 MB naive. Offline-capable after first run, retargetable to any Unicode version:

bun run generate:icons --unicode 17.0.0

Search: Pure client-side, no dependencies, no network calls. Supports exact glyph paste, name/keyword matching, code point lookups in any notation (U+2605, 0x2605, 9733), and fuzzy subsequence matching. The index builds on the first keystroke. Warm search: 2–6 ms over the full dataset.

Directory: Windowed grid with IntersectionObserver pagination, content-visibility: auto on off-screen tiles. Clicking a glyph opens a native <dialog> inspector with cross-font rendering, one-click copy in every developer format, shareable #U+XXXX permalink, and favorites/recents in localStorage.

PWA: A hand-rolled service worker precaches the full app shell and dataset. Network-first for navigations, cache-first for immutable assets, stale-while-revalidate for everything else. Versioned caches pruned on activation. Install prompt for Chromium and a Share hint for iOS.


vs. the original

utf8icons.comOpen UTF-8 Icons
StatusBroken (HTTP 500)Live at utf8.a3k.me
ArchitecturePHP + Laravel + MySQLStatic SvelteKit
SearchServer-side (broken)Client-side, instant, offline
AdsGoogle AdSense + interstitialsNone
OfflineNoneFull PWA
SourceClosedOpen source
Can break from a DB crashYes (and did)No database to crash

Sometimes the best architecture is the one with the fewest things that can break.

Open UTF-8 Icons is live at utf8.a3k.me and open-sourced at github.com/amr3k/open-utf8-icons.

Related Posts

Continue reading more articles

View all

Join the discussion