Naming & Ecosystem Proposal
Platform identity, application naming, and terminology — built around the personal .me philosophy.
1 The .me Philosophy
"xandeum.me is not the Xandeum community. It is YOUR window into the Xandeum ecosystem. Everything here is built around you — your assets, your voice, your connections, your experience."
The .me top-level domain is not accidental. It signals ownership, personalization, and individual perspective. Every feature on this platform should feel like the user's personal command center for everything Xandeum.
This reframes the entire platform:
- It's not "a community site" — it's your personal interface to the Xandeum ecosystem
- It's not "a news page" — it's your incoming broadcast feed
- It's not "a member directory" — it's your network of contacts
- It's not "a forum" — it's your transmission channel
The naming convention we choose should use signal, transmission, and broadcast language — reinforcing the idea that users are tuned in, connected, and broadcasting through the Xandeum ecosystem.
2 Platform Name — 5 Proposals
Each name leans into the signal/broadcast metaphor and the personal .me identity.
A signal is personal — it's YOUR voice broadcasting into the network. It's also what you receive: signals from others, from governance, from the ecosystem. The word perfectly bridges the transmission/broadcast language with the personal .me identity.
A relay receives, amplifies, and passes signals forward. You're not just consuming — you're an active relay point in the network. Every transmission you make strengthens the signal. It implies participation, not passive observation.
A beacon broadcasts continuously — a persistent signal that says "I'm here." Your profile is your beacon. Your posts radiate outward. Others can find you by following your signal. It's a lighthouse metaphor that implies visibility, guidance, and presence.
"On the wire" means you're connected, you're in the loop, you're receiving live intel. It's short, punchy, and immediately evokes a hardwired connection. The wire is always on — a constant stream of information. "Did you catch that on the wire?" becomes natural language.
Every user has their own frequency — their unique channel. You tune in, you broadcast, you receive. Frequencies can be shared (categories) or personal (profiles). "What's happening on your frequency?" The word is deeply personal and fits the .me domain perfectly — this is YOUR frequency.
3 Application & Section Names
Each section of the ecosystem gets its own identity. These names work across any of the 5 brand options above. Existing applications are marked; future builds are indicated.
4 Complete Terminology Map
Every label across the platform, mapped from generic to themed.
| Current Term | New Term | Context |
|---|---|---|
| Community | The Network | Overall platform reference |
| Community Feed | Transmissions | Main content feed page |
| Create Post | New Transmission | Post creation button/page |
| Blog / Update / Discussion | Signal / Dispatch / Thread | Post types |
| News | Broadcasts | Admin-published content |
| Members | The Roster | Member directory page |
| Member / User | Operator | Individual user reference |
| Profile | Callsign | Personal profile page |
| Complete your profile | Set up your callsign | Onboarding prompt |
| Categories | Channels | Content categorization |
| Comments | Replies | Post responses |
| Likes | Boosts | Engagement action |
| Featured / Pinned | Priority Signal | Highlighted content |
| Notifications | Pings | Alert system |
| Admin Panel | Control Room | Administration area |
| Dashboard | Command Center | Admin overview page |
| Asset Hub | The Vault | Token/asset management |
| Join the community | Connect to the network | Registration CTA |
| Log In | Authenticate / Log In | Keep familiar or theme it |
| Sign Up | Register / Request Access | Registration action |
| View count | Intercepts | How many saw it |
| Member since | Online since | Join date display |
| Community-Driven | Operator-Driven | Platform description |
5 Subdomain Architecture
How the full ecosystem maps across xandeum.me subdomains:
| Subdomain | Application | Status | Description |
|---|---|---|---|
xandeum.me | Splash / Landing | Live | Gateway — login, register, overview of the ecosystem |
[brand].xandeum.me | The Network | Live | Transmissions, Broadcasts, Roster, Callsigns |
vault.xandeum.me | The Vault | Live | Asset management (currently hub.xandeum.me) |
council.xandeum.me | The Council | Planned | Governance, proposals, voting |
scanner.xandeum.me | The Scanner | Planned | Analytics, token tracking, chain monitoring |
forge.xandeum.me | The Forge | Planned | Developer tools, APIs, documentation |
exchange.xandeum.me | The Exchange | Planned | Marketplace, trading |
archive.xandeum.me | The Archive | Planned | Knowledge base, tutorials, guides |
6 Revised Disclaimer
[XAND Signal / Relay / Beacon / Wire / Frequency] is an independent, operator-built platform for participants in the Xandeum ecosystem. It is not affiliated with, endorsed by, or officially connected to Xandeum, the Xandeum Foundation, or its core development team. XANDEUM and XAND are trademarks of their respective owners. All content, transmissions, and opinions expressed on this platform are those of individual operators and do not represent the views of the Xandeum project.
7 Decision Points
Once a brand name is selected, the following actions cascade:
- Set up
[brand].xandeum.mesubdomain - Move network application from xandeum.me to the subdomain
- Rebuild xandeum.me as a themed splash/gateway page
- Apply terminology map across all pages and templates
- Update
config.php—SITE_NAME,SITE_TAGLINE, labels - Update navigation, buttons, headings, and footer wording
- Rename
hub.xandeum.metovault.xandeum.me(optional, phased) - Update all cross-references between applications