About eight months ago I decided that the cybersecurity site I run needed a proper glossary. Not a static page with 50 definitions, but a real searchable knowledge base — terms organized by category, each with a proper definition, related terms, difficulty level, and a clean URL.
We're now at 500+ terms across 8 categories: Active Directory (102 terms), General Security (101), AI Security (working toward 100), Hacking (working toward 100), Compliance, Cloud Security, DevSecOps, Forensics, and OT/ICS. The backend is MySQL, the frontend uses Meilisearch for full-text search, and the whole thing is part of a Go Fiber application.
Here's what I actually learned building it — not the "knowledge bases are great for SEO" takes, but the technical and editorial problems I didn't anticipate.
Slug uniqueness is harder than you think
Every glossary term gets a URL slug. Simple enough. The problem is that cybersecurity is full of acronyms, and acronyms collide.
