Skip to content
evolve.tt
Course progress 0 of 11 complete
Phone first, then wider, then a deliberate break test.
Infographic A missing image is a state you design for. Drawn for evolve.tt.

Copy is in. This lesson tries to break the pages on purpose so a visitor does not find the break first.

In browser developer tools, or by dragging the window:

  1. ~320–390px wide (phone)
  2. ~768px (tablet-ish)
  3. ~1200px (desktop)

You are not collecting analytics. You are asking: can I read this, tap this, and move to Contact?

  • Long word — add a long email or URL; ensure it wraps (overflow-wrap: anywhere on body or links).
  • Missing image — if you added an image, remove the file temporarily; the alt text should still explain it.
  • Empty offer — hide one list item; the layout should not leave a strange gap that looks like a bug.
  • Zoom — increase page zoom to 200%. Text should reflow, not clip.

Perfect pixel match across every device brand is out of scope. So is a hamburger menu animation. Three visible links and a stable column are enough success for version one.

Break-test the site 30 minutes
  1. Walk Home → Services → Contact at phone width. Fix any nav or spacing issue.
  2. Repeat at desktop width. Confirm your grid choices still match notes.md.
  3. Force a long contact string and fix wrapping if the page scrolls sideways.
  4. List three fixes you made in notes.md under “Responsive checks”.
  5. Optional: ask an assistant for other failure cases, then try only one that fits a three-page static site.
Before you continue

You are ready for Developer handoff when:

  • phone and desktop widths both work for all three pages
  • at least one failure state was tested
  • responsive notes exist outside the chat

Mark this lesson complete when those three are true.