Quick answer: Changelog categories drift over time. A small fixed taxonomy (5-7 categories) with clear definitions beats infinite tags - players scan; categories let them scan fast.

Categories that grow get unreadable. Categories that stay stable build muscle memory; players know what to expect.

5-7 categories max

New Features, Improvements, Bug Fixes, Balance Changes, Performance, Known Issues. Add a 7th if you ship live ops content.

Definitions per category

'Improvements: changes to existing features that aren't bug fixes.' Without definitions, contributors guess; categories drift.

Order matters

Most player-facing first. New Features at the top; Performance and Known Issues at the bottom. Reading attention follows order.

Lock the taxonomy

Once set, only update at major versions. Mid-release additions break reader habits.

“Changelog taxonomy is a UX decision. Make it once; keep it.”

Add a 'changelog style guide' to your wiki. New release captains will need it; veterans will rely on it.