Journal · 2 June 2026
Naming events so editors can read them
A taxonomy editors understand beats a perfect schema nobody opens.
If your event names only make sense to engineers, content decisions stall. Editors need verbs they recognize: opened tip, finished lesson, dismissed banner, shared guide.
Keep properties human: content_id, format, topic_cluster, placement. Avoid packing five meanings into one overloaded field.
Document each event with a one-line purpose and an example question it answers. That sheet becomes the bridge between analytics and editorial standup.
When naming drifts after a redesign, schedule a short rename window rather than living with aliases forever.