Hook + finish line
Say what the lesson is about and what "done" looks like.
Goal settingTry another way to build: snap together HTML, CSS and behavior blocks, change their fields, and watch your website update. Start with this lesson’s project or try a code example below.
Click anything to select it. Click ✏️ Type to edit the words. Drag the green dot to resize it. Drag ⠿ to move it up or down.
This is where you build your own page for mrscandrett.github.io. Turn on Design mode in the preview to click, drag, and type right on your page — just like Wix. Prefer code? Add ready-made pieces, load a full example, or type it yourself. Everything updates live, and the Code Coach helps if something breaks.
Say what the lesson is about and what "done" looks like.
Goal settingConnect the new idea to something you already understand.
RecallShow a finished example and explain why it works.
NoticingTake it step by step, with a clear checkpoint along the way.
Break it downTest it, find one problem, then fix it.
DebuggingExplain what changed, what worked, and what's next.
Think back8 short guides · open one at a time
Stuck on something? Open the tutorial list below and pick the one guide you need. You don't have to read all eight before you start building.
Before you write any code, answer three questions in one sentence each: Who is this page for? What will they learn about you? What should they click or try? Turn your answers into a short introduction.
These tags mark the "rooms" of your page, so people — and screen readers — can find their way around. <header> introduces the page. <main> holds the important stuff. Each <section> covers one idea. <footer> wraps it up.
<header class="hero">...</header> <main> <section id="about">...</section> <section id="lab">...</section> <section id="games">...</section> </main> <footer>Made by ...</footer>
Every project section should do the same four things: name the idea, explain it in plain words, show proof it's true, then give the reader something to click. Use that pattern for each project you show off.
<section class="lesson-card"> <p class="eyebrow">Rocket Lab · Week 5</p> <h2>How fin angle changed my flight</h2> <p>I predicted... My evidence showed...</p> <img src="https://example.com/rocket.jpg" alt="My rocket at launch"> <a href="#data">Inspect my results →</a> </section>
Good-looking pages reuse the same few colors and shapes everywhere. A CSS variable stores a choice — like your favorite color — one time, under a name you pick. Reuse that name anywhere instead of retyping the color.
:root {
--page: #0c0f14;
--card: #151b24;
--text: #e8ecf2;
--muted: #aab6c3;
--accent: #50c8aa;
--space: 1rem;
--radius: 14px;
} Start with one column, like a phone screen. Only add more columns once there's enough room. This "phone-first" habit keeps your cards from getting squished or forcing people to scroll sideways.
.project-grid {
display: grid;
grid-template-columns: 1fr;
gap: var(--space);
}
.lesson-card {
background: var(--card);
border-radius: var(--radius);
padding: var(--space);
}
@media (min-width: 720px) {
.project-grid { grid-template-columns: repeat(2, 1fr); }
} Every interaction follows three moves: find the button, listen for a click, then change something on the page. Add aria-live to the result so a screen reader reads the answer out loud automatically.
<button id="reveal-btn" type="button">Reveal my prediction</button>
<p id="result" aria-live="polite"></p>
var button = document.getElementById('reveal-btn');
var result = document.getElementById('result');
button.addEventListener('click', function () {
result.textContent = 'I predicted the 12° fins would fly farthest.';
}); Pick one: A block adds a little code without erasing anything. A bundle replaces all three files — but it always asks first.
Drag a block into the editor. On a tablet, Chromebook, or keyboard, press Add.
Each bundle is a complete, working page. Comments inside tell you exactly what to change.
Nothing added yet. Your saved work stays put until you choose a block or bundle.
Checks all three files and the live preview, then explains the smallest useful fix.
Reading your code…
Auto-saved in this browser — close the tab, come back tomorrow, and your page will be here. Use ⧉ Download in the side panel to take a copy with you or hand it in.
Lab entry · robotics evidence
After the Arduino bumper robot build, add a robotics entry to the Lab section of your student page. A visitor should be able to understand what the robot sensed, what state changed, and what you learned from testing.
Show DRIVE → BACK_UP → TURN → DRIVE. Label the arrows “bumper pressed,” “450 ms,” and “500 ms.” Add a sentence about what each motor does in each state.
Show a short, readable excerpt with the State names and one transition from your actual sketch. Explain why that event changes the state. Link or attach the full sketch if your class uses a code repository.
Add your own clear photo or short video of a test, with a caption and descriptive alt text for a photo. Report successes out of at least ten trials, one failure condition, and the change you made afterward. Ask permission before posting anyone else's face or voice.
Page check: Can a classmate identify the sensor, controller, and motors, follow the labeled state changes, read the code excerpt, and see evidence of a real test? Keep your media file with the page when publishing so its relative link works.
Definition of done · exit ticket
Complete the self-grading code checks above, then answer these three prompts with a partner or in your learning journal.
Point to your intro, your example, your practice section, your checkpoint, and your reflection. What job does each part do?
Pick one HTML, CSS, or JavaScript choice you made. What problem does it solve for a visitor?
Name one piece of feedback you got, and the exact change you made because of it.