Why Taxonomy Is More Than Structure: Building Digital Community Spaces
I recently had the pleasure of designing a hierarchical taxonomy on a local Discord server for the pagan community of a small Pacific Northwest city. Collaborating with subject matter experts—tech designers, former software project managers, and community organizers—the project became a rewarding blend of technical rigor and culturally-informed design.

Starting With Purpose: The Kickoff Meeting
It began with a kickoff meeting to define the scope and purpose of the server. Before touching any channels, we needed clarity on intent: What questions would this server answer? Who were we serving? What engagement patterns mattered most? These questions helped shape the functional architecture of the community. We assessed what kinds of content categories would support these goals—what functionality was needed and what subject channels would be required to deliver on them.
Academic Training and Cultural Context
My formal education in religion, anthropology, and folklore shaped how I approached cultural nuance, shared vernacular, and inclusive categorization. I studied religions, anthropology, and folklore—especially pertaining to Europe and Asia. Before that, I grew up in the SF Bay Area and came of age playing table top RPGs like D&D with the children of 60’s era founders of many local neo-pagan paths as well as organizations like the Society for Creative Anachronism. Through these friendships as well as my own reading, thanks to growing up in Berkeley, supplemented with marvelous bookstores like Shambhala Books and Moe’s Books – I gained an education in pre-Christian and non-Western religions, mysticism, and mythologies. This foundation informed every layer of the taxonomy design.
Learning From Existing Communities
I started with conducting a comparative analysis of other similar servers from overlapping communities. I examined their functional hierarchy, their core administrative and technical categories and channels—from Announcements, Event directories, to FAQs. I knew that we needed channels for Event planning as well as spaces for people to have discussions about many different groups of traditions and crafts. We also needed an off-topic area for people to share pet photos, memes, or to talk about non-spiritual hobbies. Comparative analysis showed me what worked elsewhere and what didn’t; structures like these exist for reasons.
Terminology as a Negotiation
In a shared spreadsheet I developed my recommendations which I ran past top SMEs for review of terminology. Once I gathered their preferred candidate terms I reviewed all against core Taxonomy standards and delivered recommendations to the broader group to discuss and vote on. The spreadsheet became a site of discussion where we tested terms against standards, gathered SME preferences, and voted on final candidates.
Navigating Scope and Ownership Concerns
The review session diverged into a discussion of the need to develop moderation and rules, which was deferred to a later content development stage. However, it was the critique of the scope, purpose, and ownership of the overall project that threatened to derail the timeline or cost us members. Thankfully, the project manager adeptly smoothed concerns, and compromises were agreed upon. A clearly delineated schedule was developed for review of the taxonomy, implementation, and then delivery of a prototype.
The Prototype and Its Reception
After a week of further taxonomy analysis, restructuring, and polishing of terminology, I implemented the prototype with additional engineering assistance for internal testing and feedback. Reception overall was enthusiastic and positive.
What Classification Reveals About Community
Working with varied subject matter experts—it was an enjoyable blend of technical expertise and creative content. What struck me most was how classification, often seen as dry or mechanical, became a vessel for connection, identity, and shared meaning in this shared digital commons.










