Course Course Codes The Week Competition Assignment
Sign In Get Started →
Home  /  Frontend Development  /  Week 3
📐 Layout Week · Flex, Grid & Going Public

Week 3 —
Lay It Out

Last week you made a page look like something. This week you decide exactly where every element sits, make it hold together on any screen size, and add motion that makes it feel alive. Then your pod turns the camera around — every member on record, building in public.

6
Active days
7
Sessions
3
Kemi sessions
2
Live with Okwe
1
Career class
1
Pod competition
1
Assignment
11,788–13,858
Skill Points on offer
0 of 7 done

Every session carries a code.

The colour on the left of each session tells you what kind of class it is before you read a word of it. Tick a session off once you have done it — your progress is saved on this device.

FOR102
Virtual Class
Kemi · AI-guided, solo
9AM · Tue, Thu & Fri
FOR101
Core Frontend Dev
Mr. Okwe · Live
7:30PM · Monday & Wednesday
FOR103
Career Readiness
Mr. Joshua · Live
7:30PM · Friday
PODS
Public Building Week
35 pods · Saturday
Bonus SP for every member

The full week.

Tap a day above, use the arrows, or swipe left and right. Every day shows exactly what you walk out able to do, why it matters, how many Skill Points are on the table, and what to post so your pod sees you building.

👉 Swipe or use ← → keys
01Mon
Position It. Display It.Live with Mr. Okwe
Live
🧭
Why today matters

You spent Week 2 spacing things with padding, margin, and border. Today you learn how to actually place an element exactly where you want it — pinned to the top of the screen, layered over another element, or locked to the corner of the page. This is also your first look at Flexbox and Grid, the two layout tools the rest of this week is built around.

Skill Points available today
1,000 SP
CHALLENGEPublic Building — Day 1 task+1,000

Live classes don't award SP automatically. Today's guaranteed points come from today's Public Building task — the rest of the week's SP is unlocked through the virtual sessions, the assignment, and your pod's video.

FOR101
7:30PM
Mr. Okwe
Core Frontend Dev
Positioning and Display

How to control exactly where an element sits — and what it sits next to.

What you leave able to do
  • Control displayblock, inline, inline-block, and none, and how each changes what an element does and doesn't respect about the box model.
  • Control positionstatic, relative, absolute, fixed, and sticky, and what each one actually anchors to.
  • Understand stacking — a first working sense of z-index and why two positioned elements sometimes fight for the same space.
  • See where this is going — a first look at display: flex and display: grid, just enough to recognise them before Tuesday and Thursday's deep dives.
Prep issuedAssignment 3: Rebuild the Layout — full brief given today, peer-review required, due for pod review by Friday.
Pod task droppedMeet Your Pod — this week's public-building video brief goes out today. Roles get assigned inside each pod before class ends.
🎥

Meet Your Pod

Brief dropped Monday · Runs all week · Submission Friday · Results Saturday

35 pods. One video, made together, that introduces every single person in the pod to the rest of the cohort — name, specialty, and what they've actually learned and lived through so far. Not a corporate intro. A real one.

Every pod must submit, by Friday
1One video — any length, any format: a phone reel, a multi-cut edit, a chain of talking-head clips. It introduces every member of the pod.
2Each member's segment covers three things — their name, their specialty or focus in the course, and one thing they've learned or experienced so far.
3Every member appears on camera or is heard on mic at least once — nobody's part of the pod's story gets skipped.
4Submitted as one link — YouTube, Drive, Instagram, TikTok, whatever the pod actually used — posted by the pod lead before 11:59 PM Friday.
Winning condition

Judged Saturday by the instructor team on two things — creativity and completeness, meaning every single member actually shows up in the video. The most polished edit with one confident face and four silent members loses to the pod where everyone, however awkwardly, said their own name on camera.

This isn't a video-editing contest. It's practice at exactly what Friday's career class covers — being visible, showing your work, and getting comfortable putting yourself and your team in front of an audience. The habit matters more than the polish.

Prize — SP per member, not per pod
🥇1st place pod10,000 SP each
🥈2nd place pod5,000 SP each
🥉3rd place pod3,000 SP each
Every other pod that submits2,000 SP each
Every day this week also carries its own 1,000 SP Public Building task — a classroom screenshot, a progress shot, a shoutout to a teammate, a peek at what you built. These are posted inside each day's card above and stack independently of the video project — showing up daily earns SP whether or not your pod wins Saturday.

Rebuild the Layout

Take the page you styled in Week 2 and rebuild how it's arranged — using Flexbox and/or Grid instead of plain block stacking, positioned deliberately in at least one place, and responsive across screen sizes. Same repo, new commits. Nothing counts as officially submitted until two people from your own pod have checked it and approved it.

1Rebuild your page's overall layout using Flexbox and/or CSS Grid — no more relying on default block stacking alone.
2Use at least one deliberate position — a sticky nav, a fixed "back to top" button, or an absolutely-positioned badge or label.
3Make the page responsive — at least one media query breakpoint where the layout visibly changes for a smaller screen.
4Add at least one transition — a hover effect on a button, link, or card that changes smoothly, not instantly.
5Keep the semantic structure, styling, and form from Week 2 intact — this is layout added on top of what you already built.
6Commit history should show the layout evolving — same repo, new commits, not a rebuild from scratch.
How you submit

Built locally in VS Code, pushed to the same GitHub repository from Weeks 1 and 2, submitted as a repo link — and posted, along with a screenshot of the responsive view, into your pod's review thread by Friday.

🔒 Peer Review Required — how the 5,000 SP is unlocked
1Post your repo link and a screenshot of the mobile/responsive view in your pod's review thread by Friday.
2Two different members of your pod review it against the six requirements above and each give it their approval — one approval isn't enough, and nobody approves their own work.
3Once both approvals are in, your submission locks in as officially approved and 5,000 SP is credited to your dashboard.
⚠ Layout skill and peer accountability, together

This week deliberately pairs the most technically dense stretch of the course so far — positioning, Flexbox, Grid, responsive design, transitions — with the first peer-gated assignment. Nothing is marked complete until two people from your own pod have actually looked at it. That's on purpose: reviewing a teammate's layout teaches you almost as much as building your own.

Two things to hold the line on. A review is a real check against the six requirements, not a rubber stamp — approving something you haven't actually looked at defeats the point of the exercise and the SP attached to it. And Meet Your Pod is judged on whether every member shows up, not on production quality — a pod where everyone, however awkwardly, said their name on camera beats a pod with one confident face carrying four silent members.

Ready for Week 3?

Layout Week builds directly on your Week 2 page — make sure your repo is pushed and up to date, and that your pod knows who's reviewing what, before Monday's live class.

Continue to Week 3 → Back to Course