Warm-Up: Grid Detective

Open a well-designed website.

Can you find the grid?
How many columns?
Where are the margins?

Screenshot and annotate with your grid overlay guesses.

Prayer

Mira, will you pray for us today?

Grid Systems

Grids are invisible scaffolding — they create consistency and speed up every design decision.

Today

Grid Detective Warm-Up
Two-Phase Framework + Practice
Grid Systems + Practice
Work Session: Wireframes

The Two-Phase Framework

A structure for learning anything with AI.

Phase 1: Taking In (Acquisition)

Use when learning something new

Scope First

Break down the topic into sub-topics. Get the map.

Why First

Why does this matter? Where does it fit?

Chunk It

One piece at a time. Don't move on until you get it.

Translate

Ask for analogies, examples, different explanations.

Verify

Cross-check facts. AI can be confident and wrong.

Phase 2: Strengthening (Retrieval)

Use when you have some knowledge to work with

Teach Back

Explain it to AI in your own words. Ask for feedback.

Quiz Me

Ask AI to quiz you. Answer BEFORE seeing feedback.

Minimum Hint

Ask for the smallest possible hint — not the answer.

Socratic Mode

Ask AI to guide you with questions, not explanations.

Let's Practice

I do / We do / You do

I do: Watch Me Learn

Topic: Visual Rhythm and Spacing

"I want to learn about visual rhythm in design. Watch how I use AI."

I do: Acquisition Practices Live

  1. Scope First: "I want to learn about visual rhythm and spacing in design. Can you break this topic down into the main sub-topics I should understand?"
  2. Chunk It: "Let's start with just one of those. Explain [first sub-topic] to me."
  3. Translate: "Can you give me an analogy for how visual rhythm works? Something from everyday life?"

Notice: I'm actively directing the conversation, not just absorbing.

We do: Your Turn to Choose

We'll continue learning about visual rhythm together.

What practice should we use next?

More Acquisition?

Chunk It (learn another piece)
Translate (ask for examples)
Why First (understand importance)

Try Strengthening?

Teach Back (explain what we learned)
Quiz Me (test ourselves)

You're practicing CHOOSING practices, not just watching.

You do: Pairs Practice

Same topic: visual rhythm

Partner A: Acquisition

Try Chunk It or Translate — learn something new about visual rhythm using AI.

Partner B: Strengthening

Try Teach Back — explain what you've learned so far to AI and ask it to check your understanding.

Swap roles after 4 minutes.

Debrief: What felt different about taking in vs. strengthening?

Grid Systems

The invisible structure behind every good design

Without grids, you're guessing.
Every spacing decision becomes a debate with yourself.

Grids reduce decision-making.
That's how professionals work fast without sacrificing quality.

By the End of Today

Grid Fundamentals

Box model, auto-layout, 4px spacing system

Figma Grids

Mobile 4-column, desktop 12-column

Responsive Thinking

Same content adapts across breakpoints

Every Element is a Box

Content
Padding
Border
Margin

Total width = content + padding + border
Margin is spacing between boxes, not part of the box itself

Developers use debug borders to visualize boxes — you can think this way too.

When to Use Which?

Different Backgrounds

Use both — margin creates gap, padding creates internal space

Same Backgrounds

Consolidate into padding

Auto-Layout ≠ Box Model

Figma auto-layout is NOT the CSS box model.
It's closer to CSS Flexbox.

Gap vs. Margin

Margin

Space on ALL sides of each element (including outer edges)

Gap

Space only BETWEEN siblings (not on outer edges)

To add space around an auto-layout frame, wrap it in a parent and use padding.

Two Types of Grid

Explicit Grid

Columns, gutters, margins — the visible structure you set up

Implicit Grid

The spacing rhythm between all elements — what creates the "clean" feel

4, 8, 12, 16, 20, 24, 32, 40, 48...

Use 4px increments for all spacing.

Why 4px? Divides evenly, aligns with browser defaults.
Avoid 5px or 10px increments.

"The grid is an attitude."— Massimo Vignelli

Common Grid Patterns

Mobile: 4 Columns

375px frame width

Desktop: 12 Columns

1440px frame width

Same content, different column spans.

I DO

Demo: Setting Up Grids

  1. Create desktop frame (1440px) with 12-column grid
  2. Create mobile frame (375px) with 4-column grid
  3. See how same content aligns to different grids

WE DO

Build a Product Card

Create a simple card with these elements:

  1. Image placeholder (gray rectangle)
  2. Product title
  3. Price
Product Title
$49.99

Mobile example →

WE DO

Place Your Card on Both Grids

Experiment with placement:

Desktop (12-col)

Try spanning 3 or 4 columns. How does it feel?

Mobile (4-col)

Try full width or 2 columns side-by-side.

What changed? What stayed the same?

YOU DO

Set Up Grids on Your PDP Frames

5 minutes

  1. Create or select your desktop frame (1440px)
  2. Add a 12-column layout grid
  3. Create or select your mobile frame (375px)
  4. Add a 4-column layout grid

What Makes a Good Wireframe?

Clarity

Can someone understand the layout at a glance?

Hierarchy

Is it obvious what's most important?

No Distracting Details

Use boxes and text labels, not real content

Wireframes separate structure decisions from visual decisions.

Cluttered vs. Clear

Before

Too much detail, real images, actual text — distracts from layout decisions

After

Simple boxes, placeholder labels — lets you focus on structure

C3: Mobile + Desktop Wireframes

Due: Wednesday, Feb 18 @ 11:59pm

  1. Simple wireframes for both mobile AND desktop PDP
  2. Show: product title + details, image placements, button placements, page layout
  3. Focus on structure, not visual polish

These wireframes become the foundation for your high-fidelity work.

Same content, different arrangement — let the grid guide you.

What's Due / Next Up

Due before class:

C2: Type Hierarchy

Due Wed @ 11:59pm:

C3: Mobile + Desktop Wireframes

Next Up:

  • Work session: Set up grids, then start C3 wireframes
  • Get feedback on grid setup and content alignment
  • Think about thumb-zone navigation for mobile

Homework:

  • C3: Mobile + Desktop Wireframes (due Wed @ 11:59pm)
  • Begin high-fidelity PDP designs
1 /