{"id":98042,"date":"2026-10-08T05:26:00","date_gmt":"2026-10-08T09:26:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=98042"},"modified":"2026-09-29T07:58:37","modified_gmt":"2026-09-29T11:58:37","slug":"custom-taxonomies-emdash-cms-98042","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/custom-taxonomies-emdash-cms-98042\/","title":{"rendered":"How to Build Custom Taxonomies in EmDash CMS"},"content":{"rendered":"

EmDash CMS<\/a> treats taxonomies differently than WordPress. Instead of a freeform system where you create categories and tags as loose terms, EmDash makes every taxonomy part of a content type’s schema. You define the structure first, then assign content to it. That shift changes how you organize content\u2014and it eliminates the mess of orphaned terms and inconsistent tagging that plagues most WordPress sites after a few years.<\/p>\n

This guide walks through creating custom taxonomies in EmDash, explains why the schema-first approach wins for data integrity, and addresses the one real objection: “But WordPress taxonomies are simpler for non-technical users.”<\/p>\n

What Makes EmDash Taxonomies Different<\/h2>\n

WordPress has two built-in taxonomies: categories and tags. You can register custom taxonomies via register_taxonomy()<\/code>codecodecode in PHP. Terms are stored in a separate table (wp_terms<\/code>codecodecode) and linked to posts via wp_term_relationships<\/code>codecodecode. There’s no enforced schema\u2014a term is just a name and slug. You rely on plugins like Advanced Custom Fields to add metadata to terms.<\/p>\n

EmDash inverts this model. Every “taxonomy” is actually a field on a content type. You create a content type (e.g., “Product”), then add a field of type “Select” or “Relationship” that points to another content type (e.g., “Category”). The category itself is a content type with its own fields\u2014description, image, SEO meta. This means:<\/p>\n