CordNexaBrowse templates
FREE CORDNEXA TOOL · NO ACCOUNT NEEDED

Plan your Discord server
before you build it.

Choose how your server will work. Get a practical channel layout, safe role hierarchy and contextual setup plan that you can customise, copy and carry into CordNexa's focused generators.

1
ConfigureChanges update the blueprint and URL.
Server

Forum, Announcement and Stage channels require Community features.

Activity & access
Optional needs

Configuration is stored in this page's URL, ready to bookmark or share.

2

Your server blueprint

12 channels · 10 roles · 10 launch channels

Gaming50 250Community onpublic

Rename any channel, move it within its category, or remove optional channels. Launch channels stay available so the plan keeps a usable core.

START HERE

A clear entrance with only the information people need first.

3
  1. textread-onlylaunch

    What the server is for and what a new member should do first.

    Keep this short and link to rules and role selection.
  2. textread-onlylaunch

    Rules, reporting route and moderation expectations.

    Members read; staff post.
  3. announcementread-onlylaunch

    Staff updates and important changes.

    Announcement channels require Community features.

COMMUNITY

The smallest useful set of shared conversation spaces.

2
  1. textpubliclaunch

    The default place for everyday conversation.

    Keep normal member permissions here; no mass mentions.
  2. textpublicoptional

    New members introduce themselves without interrupting general chat.

    Remove it if introductions are rare.

CORE ACTIVITY

The main reason people join this gaming server.

1
  1. textpubliclaunch

    Shared game discussion before individual games need their own active spaces.

    Set access at the category level and keep the channel synced.

STRUCTURED POSTS

Questions or submissions that need their own discussion and status.

1
  1. forumpubliclaunch

    One post per session so current groups stay findable.

    Use tags and one post per topic. Forum channels require Community features.

EVENTS

Schedules and opt-in event conversation.

2
  1. textread-onlylaunch

    Upcoming sessions, meetings or launches linked to Discord Scheduled Events.

    Use an opt-in notification role instead of @everyone.
  2. textpublicoptional

    Questions and coordination for current events.

    Archive or reuse it between events rather than creating permanent event channels.

VOICE

Create only the rooms your members will actually use.

1
  1. voicepubliclaunch

    Everyday voice conversation.

    Allow Connect and Speak for members; keep voice moderation with staff.

STAFF

Private safety and operational coordination.

2
  1. textstafflaunch

    Private coordination and escalation between staff.

    Deny View Channels for @everyone; allow only the staff roles that need it.
  2. textstafflaunch

    AutoMod alerts and concise records of manual actions.

    Keep access narrow and avoid copying sensitive reports unnecessarily.
3
Continue buildingTake this structure into the focused tool you need next.
→
Plan onboardingDefault channels, questions and first steps
§
Generate rulesClosest gaming preset
◎
Customise rolesDetailed permissions and warnings
✺
Write a welcomeFirst steps for this server type
⌂
See The Gaming HubClosest complete setup kit
✦
Follow the setup guideBuild and test in the right order

Need more options? Browse Discord channel ideas or review the Discord role hierarchy guide.

PLAN THE STRUCTURE

How to plan a Discord server layout

Start with member journeys, not channel names. A newcomer needs an entrance, rules and a clear first action. A regular member needs the server's main activity and one obvious place to talk. Staff need a private place to coordinate and record actions. Everything else earns its place through repeated use.

The planner turns those jobs into a launch layout, then marks expansion channels as optional. It changes the architecture for size, access model, voice use, moderation and Community features rather than swapping a theme over the same list.

START SMALL

How many channels to create first

Launch around real activities

Create orientation, general conversation, the main activity and staff coordination. A compact server feels active because members meet in the same useful places.

Add a channel when behaviour proves it

Split a topic out when it repeatedly interrupts another channel, needs different access or benefits from its own workflow. A hypothetical future topic is not enough.

Remove quiet optional spaces

An unused channel adds navigation without adding value. The planner lets you remove optional channels while protecting the minimum launch structure.

ACCESS FOLLOWS STRUCTURE

Plan channels and roles together

Channels describe where an activity happens. Roles describe responsibility, identity or access. Give staff only the permissions their work needs, and use category or channel overrides when a member role should reveal a private area.

Cosmetic, interest and notification roles normally need no permissions. Bots belong below human staff and above only the roles they must assign. Continue into the role hierarchy guide for the reasoning, or use the Roles Generator for a permission-by-permission plan.

AVOID THESE

Common layout mistakes

  • A channel for every possible topic

    Members spread across empty spaces and cannot tell where a message belongs.

  • Community-only types without Community

    Forum, Announcement and Stage channels need Community features. Use the planner's compatible text-and-thread alternatives when it is off.

  • Permissions channel by channel

    Set the category first and keep channels synced wherever possible, so new spaces inherit the intended access.

  • Roles designed after private channels

    Decide who should see an area before creating overrides, then test the result as each role.

  • Too many empty voice rooms

    Start with one. Add activity or squad rooms only when simultaneous groups need them.

  • Confusing a blueprint with a finished server

    Rules, onboarding, moderation testing and a deliberate launch still matter. Follow the setup guide after planning.

Blueprint or complete template?

Use the planner when you want to make structural decisions yourself. Use a CordNexa template when you want a reviewed, scenario-specific kit with onboarding, moderation, rules and welcome copy already worked through.

Browse server templatesComplete setup kits for specific communities.
Discord Channel IdeasDetailed channel layouts for 12 server types.
Complete setup guideBuild, test and launch the blueprint in order.
GOOD TO KNOW

Layout planner questions

How many Discord channels should I start with?

Start with the smallest set that supports orientation, the server's main activity, everyday conversation and staff coordination. Add an optional channel when an existing channel repeatedly contains a distinct, active conversation—not because the topic might be useful one day.

Does the planner create a Discord server automatically?

No. It creates a deterministic blueprint you follow in Discord. It does not connect to Discord, create channels, store your configuration or require an account.

What happens when Community features are off?

The planner avoids Forum, Announcement and Stage channels. Where a structured discussion is useful, it recommends an ordinary text channel with one thread per topic instead.

Can I share my planner configuration?

Yes. The primary choices are saved in the URL. Copy or bookmark that URL to reopen the same configuration. Channel and role renames remain local edits and are included in the copied blueprint, not the URL.

CordNexa is independent and not affiliated with or endorsed by Discord. The planner runs entirely in your browser; nothing you enter is sent to a server or stored. Discord features change over time; this tool was last reviewed on 2026-10-02.