How to Build a Dance School Website Without Code in 2026

A dance school website without code starts with one description: your styles, your levels, your timetable. Zugo turns that text into a working site, checks it in a sandbox before handing it over, and publishes it to a live address. A simple site takes one prompt, and everything after that is plain-text edits.

This guide is written for studios rather than businesses in general, because a dance school site fails in a specific way: it looks beautiful, and a nervous adult beginner still cannot tell whether Tuesday's class is for them.

What does a dance school website need to answer first?

Three questions decide whether somebody books. Can I start here as a complete beginner? When exactly do the classes run? What does it cost, and can I try one before committing to a term?

Everything else on the page is secondary. Your teachers' credits matter, your performance photos matter, but a visitor who cannot find a Wednesday beginner class at a readable time leaves before reaching either. Put the timetable and the trial offer above the fold.

The second decision to make before writing anything: are you selling drop-in classes, class packs, or termly enrolment? That single answer changes the site more than any design choice, because a drop-in studio needs a schedule and a payment button, while a term-based school needs an enrolment form and a waiting list.

What should the prompt say for a dance studio?

Zugo builds from a description, so the description carries the details a designer would ask you for in a briefing call. This template holds the parts specific to a dance school:

Build a website for a dance school in [city].
Styles taught: [ballet / contemporary / hip hop / salsa / ballroom].
Audience: [adults, teens, children aged N to N].
Sections:
1. Hero: school name, one line on who the classes are for,
   "First class free" or "Book a trial", button to the timetable.
2. Timetable: a table by day, with time, style, level, teacher, studio room.
3. Classes: one block per style, saying who it suits and what to wear.
4. Teachers: photo, name, one paragraph of background each.
5. Pricing: drop-in, 10-class pack, monthly membership, term fee.
6. Location and FAQ: address, parking, changing rooms, first-visit advice.
Tone: encouraging, plain language, no jargon a beginner would not know.

Two additions earn their place. "Mark every class as Beginner, Improver or Advanced, and explain what each level means" removes the single biggest source of enquiry emails. "Add a short section for hen parties and corporate workshops" is worth a line if that work pays part of your rent.

If a blank prompt feels harder than a starting point, Zugo ships 25 templates, and a local-business or landing template is closer to a studio site than an empty page. The templates guide covers picking one.

How do you keep the timetable current after launch?

Ask for the timetable as a table with editable rows rather than as decorative cards. Then a term change is one edit: "in the timetable, move Tuesday Contemporary Improvers from 19:00 to 19:30 and change the teacher to Maya."

An edit costs 3 credits, so a timetable that changes twice a term costs almost nothing to maintain. The cost that actually hurts is the one nobody bills you for: a stale schedule that sends someone to a class that no longer exists.

One honest limit. The table shows your schedule, it does not know how many places are left in Thursday's beginner ballet. Live capacity means a database, a booking record per class, and a counter that decrements. Zugo can build that with Supabase behind the site, but it is a project with several rounds of edits rather than a single prompt.

Should bookings go through a form, a payment, or a booking system?

This is the decision that costs most to change later, so make it before the first build. Four honest options:

The last row is the one most studios need to hear. If you already pay for class-management software, your website's job is to sell the class and hand the visitor over, not to reimplement scheduling. Build a fast, honest site with a prominent link to your existing booking page and stop there.

If you do want payments on your own site, the mechanics are the same as any small storefront, and the Stripe payments guide covers the connector in more detail than this page does.

What does a dance school site cost to build?

Zugo bills in credits per action rather than per month of use. A single-page site build costs 6 credits. A multi-page site is billed as a platform: 12 credits covering the first three pages, then 3 for each page after that. An edit costs 3.

Hi-Fi mode costs double: 12 for a build, 6 for an edit. It is worth it on the page a paid ad points to and rarely worth it on an internal FAQ.

The Free plan gives 5 credits, which is below the 6 a single build costs, so treat it as a look around rather than a launch plan. Pro is $25 per month with 200 credits, which is where a real iteration cycle lives. Business is $99 per month. Hosting for the published site is included. The full breakdown sits in the pricing guide.

How do you handle class photos and video?

Badly chosen images are the fastest way to lose an adult beginner. Photos of competition-level dancers in performance costume tell a nervous forty-year-old that the class is not for them, even when your Tuesday beginners' hour is exactly what they want.

Shoot the actual class instead. Ordinary clothes, ordinary bodies, ordinary lighting, people laughing at a step they got wrong. Eight to twelve honest images beat one glossy set, and they are the part no builder supplies for you.

Video works best embedded rather than hosted. A thirty-second clip of a real class on YouTube or Instagram, embedded in the page, loads faster than a video file you upload and gives you a second place for the same footage to work.

What will an AI builder not do for a dance school?

Three limits worth knowing before you start, so nothing surprises you mid-term.

Live class capacity is not automatic. Showing "3 places left" needs a database and booking logic. It is buildable with Supabase, described in the Supabase connector guide, but it is several rounds of work, not a paragraph in a prompt.

There is no connector to studio management software. Mindbody, TeamUp, Momence and the rest have no integration here. You link to them; you do not sync with them.

Very specific enrolment logic takes iteration. Sibling discounts, pro-rata term joining, a waiting list that promotes automatically: all reachable through targeted edits, none describable in one sentence. Budget several rounds if that is your model.

What is the first version worth building?

One page: who the classes are for, the timetable, the prices, and a trial-class form that reaches your inbox. That is 6 credits and an evening, and it answers the three questions a visitor actually has.

Run it for a term. The missing pieces will name themselves through the emails you keep answering by hand, which is a far more accurate brief than any planning session. Then edit, one paragraph at a time. When you are ready to start, describe your studio in your own words at zugo.dev.