Do you need a WoW guild website? (And how to build one with AI)

Let's be honest: do you need a guild website? You probably don't. But would it look cool to have one? It sure would.

AI can build a website. So why do they all look the same?

It's 2026 and AI is everywhere. Anyone can build a working website now, and I'm sure that by 2027 it will only get faster and better, from less and less information.

But just because everyone can prompt a working website doesn't mean every website will look, run and feel good. Over the past year, close to a hundred agencies have pitched me a website design. About 90 of them sent me an AI-built website as a showcase of what they could do for me, and guess what: they all looked and felt the same.

Even when an AI website avoids looking generic, it still feels like AI made it, with no human input beyond the first prompt. Here are the tells:

As much as it hurts me to say it, most of this doesn't matter to the general public. If someone ends up on your website, they won't care about any of it. But will they end up there? Unless you send them the link, probably not. Your site will be one more vibe-coded website in a sea of millions, with no real care or input behind it.

So the goal isn't to have a website. The goal is to have one that looks and feels like your guild, and to put the link everywhere your guild shows up: your recruitment posts, your Discord and your in-game messages.

What it actually costs

I'm not saying you need to invest thousands of dollars in a WoW guild website. And I'm not saying you can't build one with AI. You can. Here's what that looks like:

That's roughly $40 to $100, plus your time. You can have the site done and running in less than a week. Prices change and first-year domain deals often cost more at renewal, so check before you buy.

A word on time: don't listen to the Instagram gurus who say they built a website in 10 minutes. They got a rough prototype in 10 minutes. After that, you still have to go through the whole site, fix and tweak things, and do a lot of cleaning up. Even if AI does all of that for you, it's hours of work, with usage limits on top. Setting up your domain and hosting and getting everything to work is doable with AI, but it also takes time. Before you know it, you'll have 20 hours and around $100 invested.

Too busy for all this? If you'd rather have someone else build it, I build guild websites. It's what I do, I have the experience, and I'll save you a lot of time. See services

If you want to take it on as a side project, learn something new and have fun, and you don't mind investing some time and money, keep reading.

Before you start: decide these things

Where will you host it, and what domain will you use? Check that the domain is available before you fall in love with it. Once you've decided, put it in your first prompt, so your AI knows. It matters.

What kind of site is it? An app, or a static website? A WoW guild website usually needs no database and offers fairly simple things, so a static HTML, CSS and JavaScript website is more than enough. Add that to your prompt too.

What pages do you need? One page with everything on a landing page, or several pages? Some options:

• About Us (about the guild)
• Meet Us (your guild members)
• Our Philosophy (can be merged with About Us: your goal, how you play and so on)
• Loot Rules (add a Loot History page if you want to be fully transparent)
• Raid Progression
• Recruitment Needs
• Contact
• Apply
• Privacy Policy

There's a lot to choose from, so think it through and write down a list before you start.

What links do you want? Your Warcraft Logs profile, your Discord invite, your WoW Armory? Again, there are loads of options.

How to build it with AI, step by step

The method that works best has two stages. In the first chat, you plan: Claude interviews you and writes a spec file. In the second, fresh chat, it builds from that spec. Planning first stops the AI from guessing, and a fresh chat starts with a clean context.

I use the Claude desktop app for this. It's far friendlier than a terminal, and you won't have to open one.

Step 1: Get Claude Code in the desktop app

Claude Code is Anthropic's coding tool, and it's built into the Claude desktop app, in a tab called Code. Download the app for Mac or Windows, install it and sign in. You need a paid plan (Pro is $20 a month at the time of writing, and the free plan doesn't include Claude Code). On Windows, you may need to install Git for Windows the first time you open the Code tab.

Prefer the terminal? There's a command line version too, but you don't need it for this guide.

Step 2: Make a project folder and start a session

1. Create an empty folder on your computer, for example my-guild-site.
2. In the Code tab, choose Local, click Select folder and pick that folder.
3. Start with the mode where Claude asks before it changes anything (called Ask permissions or Manual, depending on your version). Once you trust the process, you can switch to Auto accept edits to move faster.

Each conversation in the Code tab is its own session, with its own history, folder and changes. That's exactly what the two-chat method needs.

Step 3: Install the skills

Skills are folders of instructions that Claude loads when it needs them. Two free, open-source skills work very well for a website. Both are MIT licensed, but skills can run code on your computer, so skim anything before you install it.

UI UX Pro Max. This skill gives Claude design intelligence: it picks a style, color palette, font pairing and page layout that suit your kind of site, and checks the result for common mistakes like low contrast, missing focus states and emoji used as icons. It needs Python 3 installed on your computer. That's a free download from python.org, and the skill won't install it for you.

To install it, click the + next to the prompt box and choose Plugins, then add the marketplace nextlevelbuilder/ui-ux-pro-max-skill and install ui-ux-pro-max. You can also type these two commands in a Claude Code session:

/plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill
/plugin install ui-ux-pro-max@ui-ux-pro-max-skill

Emil Kowalski's skills. Emil is a designer and engineer who has worked at companies like Vercel and Linear, and his skills teach Claude the small details that make an interface feel polished: animation timing, phone quirks and how to stress-test a layout. Four are useful for a guild website:

His official install is a terminal command, npx skills@latest add emilkowalski/skillsCopy npx skills@latest add emilkowalski/skills, which needs Node.js. Without a terminal, download the repository from GitHub as a ZIP, then copy the folders you want from its skills folder into a folder called .claude/skills inside your project folder.

After installing, start a new session so the skills load. You use a skill by mentioning it by name in your prompt.

Step 4: Chat 1, the planning chat

Switch the mode selector next to the send button to Plan. In plan mode, Claude reads and plans, but doesn't edit your files until you approve. Then paste a prompt like this and fill in the parts in brackets:

I want to build a website for my World of Warcraft guild.

Before writing any code, interview me in small batches (3 to 5
questions at a time) until you have everything you need. Then
create two files in this folder:
1. SPEC.md, the full plan for the site.
2. A design system file, generated with the ui-ux-pro-max skill.

About the guild:
- Name: [name]
- Faction, server and type: [for example Horde, EU PvE, casual raiding]
- Vibe: [for example friendly and casual, or bold and hardcore]

Brand:
- Colors: [hex codes]
- Fonts: [names]
- Logo file: [filename]

Technical:
- Static HTML, CSS and JavaScript only. No framework, no database,
  no build step.
- Hosting: [Hostinger or Vercel]. Domain: [yourguild.com]

Pages: [your list]
Links: [Discord invite, Warcraft Logs, Armory]

How I want you to work:
- Placeholders are fine while we build, for things I don't have
  yet, like a link, an email address or an image. Mark each one
  clearly, keep a running list in TODO.md, and remind me which
  placeholders are still open at the end of every reply.
- Write draft copy where you can, in a natural, specific tone.
  Mark anything you made up so I can rewrite it.
- Define the menu and footer once in SPEC.md, so every page
  uses exactly the same ones.

Answer its questions honestly. When it finishes, read SPEC.md and fix anything that's wrong. A good spec covers:

• Your guild, your audience and the feeling you want
• Every page, and what goes on it
• The menu and footer (more on those below)
• Your colors, fonts and logo
• Your content and links
• Your tech, hosting and domain
• A list of placeholders that still need real information
• What "finished" means

This file is the most valuable thing you'll make, because everything is built from it.

Step 5: Chat 2, the build chat

Close the planning session and start a new one in the same folder. A fresh chat starts without the clutter of the interview. You can switch the mode to Auto accept edits now if you're comfortable. Then paste:

Read SPEC.md, TODO.md and the design system file first.
Use the ui-ux-pro-max skill for design decisions, and the
emil-design-eng and mobile-native skills for polish and phone
behavior.
Build the shared menu and footer first, then the homepage, and
stop so I can review.
After I approve, build the other pages one at a time.
Keep TODO.md up to date, and at the end of every reply, remind
me which placeholders are still open.

Build in stages, not all at once. It keeps quality higher, makes mistakes easier to catch, and helps with usage limits. To check your work, open index.html in your browser and refresh after each change. If you want to be able to undo mistakes, ask Claude to set up Git and commit after each approved page.

Step 6: Get the menu and footer right

Every page shows the same menu at the top and the same footer at the bottom. On a static site, that code can end up copied onto every page. Then changing one link means editing every page, and forgetting one is a classic mistake. Decide how to handle it in your spec:

For a small guild site, I'd lean toward the shared script, because it's easier to maintain. Whichever you pick, ask Claude to tell you which one it used, and to check that every page matches.

Decide these in the spec too:

• Menu: which pages, in what order, and whether one item (like Apply) stands out as a button
• Mobile menu: it must open, close and work with a thumb
• Current page: the menu should show which page you're on
• Footer: guild name and logo, your Discord, Warcraft Logs and Armory links, a contact email, a privacy policy link, the year, and a line saying the site isn't affiliated with Blizzard Entertainment

Step 7: Handle placeholders on purpose

Placeholders are fine while you build. Your Discord invite might not exist yet, and you might not have a photo or a contact email. The danger is forgetting them, so you let Claude help:

• It keeps a list in TODO.md of every placeholder: links, text, images and emails.
• At the end of every reply, it reminds you which ones are still open.
• Before launch, you run a final check (see the next step), and nothing ships with a placeholder left.

Step 8: The clean-up pass

This is where most people stop too early, and it's what separates a good site from an AI-looking one. Go through the table of tells above, and ask Claude to run a launch check:

Do a launch check on the whole site. List what you find, but
don't fix anything yet:
1. Every placeholder still left (links that go to "#", example.com
   addresses, sample text, missing images), from TODO.md and from
   searching the code.
2. Every form, and whether it really works.
3. Any menu or footer that differs between pages.
4. Repeated phrases, tiny labels above headings (eyebrows), and
   text that sounds generic.
5. Images without alt text, and anything hard to read or use on
   a phone.

Then use the break-ui skill to stress-test the layout:

Use the break-ui skill to try to break the layout with long
member names, empty sections and very long text, and fix what
breaks.

Go through the lists and rewrite the copy in your own words. This is where your guild's voice comes in. Use your real logo, your real screenshots and your real members.

Step 9: Test it

Open it on your phone, click every link, fill in every form, and ask a friend from the guild to try it. Check that the page title, description and a preview image are set, so it looks good when someone shares the link in Discord.

Step 10: Put it online

Upload the site to your host, or deploy it on a free option like Vercel, then connect your domain. Both have step-by-step help, and Claude can walk you through it. Don't paste your hosting password or any secret keys into the chat. Do that part yourself. For the full walkthrough, see How to put your guild website onlineComing soon.

A word on forms: a static website has no server to receive form messages. The simplest options are a link to your Discord invite, or your Discord application and ticket system (see Discord bots: build or buy?). Otherwise, use a form service that sends submissions to your email.

Don't forget

• A favicon and a preview image. The tiny icon in the browser tab, and the picture that appears when someone shares your link.
• Blizzard. Include the "not affiliated with Blizzard Entertainment" line in your footer, and use your own icons and artwork, not Blizzard's.
• Privacy. If your site has an application form or analytics, add a short privacy policy that says what you collect. If you have visitors from the EU, keep tracking to a minimum. This isn't legal advice.
• Member photos and names. Ask people before you put them on a Meet Us page.
• Content that changes. Recruitment needs, raid times and progression go out of date fast. Ask Claude to keep them in one small, easy-to-edit place, so you can update them in minutes.
• A 404 page. What visitors see when a link is wrong.
• Accessibility. Readable contrast, alt text on images, a visible keyboard focus and respect for reduced motion. UI UX Pro Max checks for these.
• Speed. Compress your images before you upload them.
• Backups and future edits. Keep SPEC.md, TODO.md and the design system file in your folder. Next time you want a change, start a new session and tell Claude to read them first.

Next steps

Decide your hosting, your domain and your page list first. Then try the two-chat method. And if it's too much, you know where to find me.

FAQ

Do I need a website for my WoW guild?

No. But it makes your guild look more serious and gives recruits a home beyond Discord.

How much does a guild website cost?

Around $40 to $100 if you build it yourself with AI, plus 10 to 20 or more hours of your time.

Can I make a guild website for free?

Mostly. You can use free hosting like Vercel and a very cheap domain, but you'll still pay for your time and for a coding AI plan.

What kind of website should a guild have?

A static HTML, CSS and JavaScript site is enough for most guilds, since they don't need a database.

What pages does a guild website need?

At least About, Recruitment, Apply and Contact. Add Raid Progression, Loot Rules and Meet Us as you grow.