Site Maker teaching notes

For teachers, co-op leaders and parents. One period of about forty-five minutes ends with every student holding a link to a web page they made, checked for the things that matter on the real web. A second period reads the page's real HTML and CSS. Each part says what to say, what students do, what their screens should show, what usually goes wrong, and a question to ask. You do not need to know HTML.

Using this with a class? Make a free class and add your students yourself: each gets a username and password, with no email or Google account needed. Or give them one join code. Using Google Classroom? Post the link there; with a free class, the link also puts each student in your class, so you see their work. mytekDev is also available from the Google Workspace Marketplace, so your school's Google admin can install it for everyone.A first lesson: Open See the code and give it to a partner. One student taps a part on the page; the other finds its lines in the code and reads them out. Then swap: one taps a line in the code, the other says which part of the page lit up and what the tag is called.

Set up a free class Share to Google Classroom
Put this on your class site

Students can use Site Maker right on your page, with no account. What they make stays on that page; to keep their work, they make a free account.

Google Sites: Insert, then Embed, then By URL, and paste this address.

https://mytekdev.com/try/sitemaker?embed=1

Canvas, a blog, or any page that takes HTML: paste this code where you edit the page as HTML.

<iframe src="https://mytekdev.com/try/sitemaker?embed=1" width="100%" height="640" style="border:0" allow="fullscreen" title="Site Maker demo from mytekDev"></iframe>

About these lessons

Period 1 has three parts: change the starter page, make it about your own topic, then check it and publish it. Period 2 reads the code with a partner and fixes the page for everyone who will read it.

Everything you are asked to say or point at is written here in the words on the screen. The box at the top right is called Ready to publish?. A red line in it must be fixed before publishing; an orange line makes the page better.

Before you start. Publishing needs students signed in to the site, and your class must allow sharing links (a class set to share inside the class only cannot publish). Decide the topic first: an animal, a state, a book, a club. Tell students a published page is public, and that first names only go on it.

How to read this guide

  1. Say what to tell the class, in a sentence or two. Use your own words if you like.
  2. Students do the steps, in order. Read them out or put them on the board.
  3. Screens should show what you see when you walk round the room and the step worked.
  4. What goes wrong the usual problems, and the fix.
  5. Ask one question to check the idea, not the clicking.

Period 1, part 1: change the starter page (10 minutes)

  1. Say A web page is parts, one under another: headings, words, pictures, buttons and lists. This one is about sea turtles. Change it, and watch what moves.
  2. Students do Drag the turtle picture to the left side of the page and let go. Double-click the first paragraph and type a sentence at the end, then press Esc. Press Phone under the page, then Laptop.
  3. Screens should show The turtle on the left with the words wrapping on its right. Their sentence at the end of the paragraph. On Phone, the turtle in the middle above the words.
  4. What goes wrong A drag moves the picture up or down instead of across: drag straight sideways. Typing does not start: double-click the words, or click them once and then again.
  5. Ask Why does the turtle move to the middle on a phone?

Period 1, part 2: make it about your topic (20 minutes)

  1. Say Now it is your page. Change the big heading to your topic, and every part after it. Every picture needs words for people who cannot see it.
  2. Students do Click the big heading, then click it again and type your topic. Change or take off each part: click it, then Take it off on the right. Drag a Words or a Picture part from the left onto the page. For a picture, write what it shows in Words for people who cannot see it. Pick a look on the right with nothing picked.
  3. Screens should show A page with their topic as the big heading, the name at the top left of Site Maker following it, at least one picture, and words of their own.
  4. What goes wrong An orange line "This picture needs words for people who cannot see it.": click the picture and fill in the box. A part landed in the wrong place: drag it up or down, or press Undo.
  5. Ask Read me your picture's words. Would someone who cannot see it know what it shows?

Period 1, part 3: check it and publish it (15 minutes)

  1. Say A published page is public: anyone with the link can read it. Ready to publish? checks it first. Fix every red line, then try to fix the orange ones.
  2. Students do Read Ready to publish? at the top right. Click each line to read why. Fix them. Then press Publish, then Publish my page. Scan the square with a phone, or open the link in a new tab.
  3. Screens should show "Ready to publish." at the top right, then a link and a square code in the Publish window, and the page open in a new tab with "Made by a student on" the site at the bottom.
  4. What goes wrong A red line about personal information: take out a phone number, an email, an address or a full name; a first name is fine. Publishing says the class shares inside the class only: that is your class setting. Publishing says a full name of someone in the class is on the page: the site checks names the app cannot see, so take it out.
  5. Ask Who can read your page now? What did you leave off it, and why?

Period 2: read the code (45 minutes)

See the code shows the page's real HTML, with its CSS at the top. It is exactly what was published. Students read it; they do not type in it. A picture's data is shortened in the view.

  1. Say Every part of your page is written in HTML. Tap a part and its code lights up. Your partner's job is to read the tag out loud.
  2. Students do Press See the code. In pairs: one taps a part on the page, the other reads its lit lines and says the tag (h1, p, img, a, ul, li). Swap. Then find the picture's alt words in the code, and the CSS rule with max-width: 480px.
  3. Screens should show A dark pane beside the page, the picked part's lines lit. The img line with alt="" holding the words they wrote.
  4. What goes wrong The code pane covers the panel: that is how it works; press Close to get the panel back. A student wants to type in the code: that is the next step, Open in Code Editor, which makes a copy they can change by hand.
  5. Ask Which tag makes the page's main heading? How many h1 tags does your page have, and why only one?
Going further. Open in Code Editor carries the page into the Code Editor as a new project. Change one word in the HTML and one color in the CSS, press Run, and see the page change.

More help

Is something on this page wrong or not clear? Write to us.

Page last reviewed November 2026.
Google, Google Classroom and Chromebook are trademarks of Google LLC.