Darasa Hub - Learning Lions
Dira Portal Safety and Welfare ICT Support
SCS2.2

Layout That Responds

Level 2 · BootCampSCS2 Business OnlineTaught week 3 Wednesday morning

Start the Lesson

By the end your bio page bends: the viewport line, flexible units, images that fit, one flexbox row that wraps, the palette as variables in one block, and one media query at a width you can defend from your own content. It has passed the four checks on a real phone and the laptop at 200 percent zoom, by the route your site uses. It has been heard with Narrator, keyed through and measured with the colour picker, and every barrier found is gone, one barrier per commit with the barrier named. The two AI asks of the day, the CSS draft and the junior auditor, are on a receipt, every line read and every finding reproduced on the real page or struck through.

Start the lesson 69 moves in 11 parts. You need: your SCS2.1 bio page in ~/scs/projects/bio-page, committed and pushed · your copy of the SCS2.2 folder, copied down from Mufasa the evening before · your own phone, or a partner's or a coach's, named on the card · the AI tool and account your coach names, or the by-hand path · your notebook, for the pass log, the protocol card, the audit sheet and the receipt

Submit Your Work

What You Turn In

  1. Repo link: your responsive bio page
    1. Viewport line, flexible units, images that fit, one wrapping flexbox row, the palette as variables, one media query you can defend
  2. Phone and laptop screenshots, and a photo of the protocol card
    1. No sideways scroll and no pinch-zoom on a real phone; both devices and the route named; coach's initials
  3. Photo of the five-point audit sheet fill in on the hub
    1. A specific finding or an evidenced pass on every line; the keyboard pass shown, or the break named with its fix
  4. Commit history
    1. The pass in steps with why-messages, then one barrier per commit with the barrier named
  5. AI receipt, both asks fill in on the hub
    1. Spec, prompt, what was kept, what was deleted, where it was verified; label 'AI-assisted — directed by me'
  6. check-scs2.2 receipt fill in on the hub
    1. Every automatic line PASS, or each NOT YET on your fault list with its planned fix
  7. Local-sites sheet and method note fill in on the hub
    1. One local site through the four checks, in the owner's words; six lines, the sixth 'what I might be wrong about, and how I would find out'

Stuck, or want to check your thinking? Paste this card into your own AI and ask it to question you, not answer for you.

How

  1. Asha, by Saturday's update.
Done when
  1. Responsive bio page in the repo: Viewport line, flexible units, images that fit, one wrapping flexbox row, palette as variables, one defended media query
  2. Phone and laptop screenshots + protocol card: No sideways scroll, no pinch-zoom on a real phone; both devices and the route named
  3. Five-point audit sheet: A specific finding or an evidenced pass on every line; keyboard pass shown or the break named with its fix
  4. Commit history as audit trail: Pass in steps with why-messages; then one barrier per commit, barrier named
  5. AI receipt, two asks: CSS draft and auditor ask: spec, prompt, kept, deleted, verified where; label
  6. check-scs2.2 receipt: Every automatic line PASS, or each NOT YET on the fault list with its fix
  7. Local-sites sheet + method note: One site through the four checks, in the owner's words; six lines, the sixth honest

Counts toward: the SCS2.2 badge, 1 to 3 stars · the portfolio (the bio page) · attendance for the Taught and SGL (Self Guided Learning) blocks · LP (Lion Points) for accepted badge work.

Fill in the worksheet Submit work for SCS2.2