Guides / About Kodebloc

Kodebloc for teachers

Use Kodebloc in class: lesson ideas, what students learn, and how to keep it safe.

Kodebloc turns a plain-language description into a working website. For a class, that means students see a real result within minutes, and then have something concrete to study, take apart and improve. Every website Kodebloc builds is ordinary HTML and CSS, the same code the rest of the web is made of. This page collects lesson ideas, what students practice, and what to know about age rules and safety before you start.

What students learn

• Writing a clear brief. A vague request gives a vague website. Students learn to say who a page is for, what it must contain and how it should feel.
• How web pages are built. Headings, paragraphs, links, images and forms in HTML, and colors, fonts and layout in CSS.
• Design for everyone. Accessibility, readable contrast and pages that work on a phone as well as a laptop.
• Judging AI output. The AI writes sample text and can get facts wrong. Students learn to check, correct and take ownership of what they publish.
• Being careful online. What it means to publish something public, what to leave out, and why photos need credit.

Lesson ideas

1. Build it, then look inside

Each student builds a simple website on a topic they know well. Then they choose Download from the website's menu in the builder, which saves the page as one HTML file, and open it in a text editor. Ask them to find the main heading, a link, an image and its description, and the place where a color is set. Pair this with What is HTML? and CSS basics.

2. Weak request, strong request

Give the class a deliberately vague request, then have students rewrite it with an audience, sections and a mood. They build both and compare. A good follow-up: two students submit the exact same request. Kodebloc picks a different design direction for each new website, so the results usually differ, which opens a talk about how the AI makes choices. Our guide on writing a good request has before and after examples.

3. Accessibility audit

Students swap websites with a partner and check them against a short list: Is there one clear main heading? Do photos have descriptions? Is the text easy to read against its background? Do links say where they go? They then fix what they find, by chat or by hand. Our accessibility guide works as the checklist.

4. Fact check the AI

Students build a website on a topic from your current unit, then mark every claim on the page as checked, wrong or unsupported, using class materials. They replace the wrong ones and add sources. It is a direct way to practice reading AI text critically.

5. A class project website

Students present a report or science fair entry as a website instead of a poster. The school project template lists the sections to include and has requests ready to build. Students can share the published link with you to hand it in.

6. Phone check

Open each published website on a phone and on a laptop. What moved? What got hard to use? This leads into responsive design.

Age rules and accounts

Building with Kodebloc needs an account. Our Terms of Service say:

You must be at least 13 years old to create an account. If you are under 18, you represent that you have your parent or guardian's permission to use the platform.

Our Privacy Policy adds:

Our platform is intended for users aged 13 and older. We do not knowingly collect personal information from children under 13.

So students under 13 should not sign up. With a younger class, you can build on a shared screen with your own account while students suggest what to ask for.

Each student uses their own account. Kodebloc does not have classroom accounts, a teacher dashboard or school licenses, so you can't see or manage students' projects from your account. Ask students to share their published links with you instead.

Keeping it safe

• Published websites are public. Anyone with the link can open one. Teach students to leave out full names, school names, addresses, phone numbers and photos of themselves.
• The community gallery is optional. When publishing, students can untick Show in the community gallery. The website is then left out of the gallery, but it is not private: anyone with the link can still open it.
• Requests go to an AI service. What students type is sent to the AI provider that builds the page, as our Privacy Policy explains. Nothing private or confidential belongs in a request.
• Pages are checked before they go online. A page that asks visitors for a password or card number, or that looks like a fake sign-in page, can't be published.
• Anyone can report a website. Every published website has a Report link. A website reported by several different visitors goes offline until we have looked at it. Read more on our safety page.
• Review what the AI writes. Our Terms of Service are clear that AI content may contain errors and should be checked before it is published.

Cost and limits

The website builder is free while in beta. Each free account gets 10 builds and changes a day, up to 50 a month, with 5 websites online at a time and 30 saved websites. Free builds also come from one shared daily pool, so on a very busy day they can run out for everyone until the next day.

Tell us how it goes

We would love to hear how you use Kodebloc in class, what worked and what got in the way. Send us a note through the contact page. You can read more about who we are on the about page.