08.03 · From wireframe to website / Learn · 7 guided steps
Place the page regions
Translate a desktop wireframe into named Grid areas and flexible columns.
Activity 3 of 6 in From wireframe to website
CSS Basics / 08.03
Place the page regions
Not started
Translate a desktop wireframe into named Grid areas and flexible columns.
Your lesson progress
Empty: not started. Yellow: in progress. Green: complete. Marking the whole activity complete does not replace your test results. These circles save in this browser for this pilot.

Understand the plan
Grid layout starts on the shared parent. Its direct children become items. A named area map is a readable layout plan, but its names must also be assigned to the children with grid-area. The browser does not infer that connection from a tag or class.
Two tokens in each quoted row describe two columns. Repeating header or footer across both cells makes it span the row. A 2fr 1fr template divides the remaining width after gaps into three shares, with two assigned to main. minmax(0, ...) lets content shrink inside its track.
Explore the wireframe
This focused practice builds the wide layout. Use the 1280px preview to inspect it. The responsive module later adapts the same idea for phones.
Select a labeled region. Compare its purpose with its position. These controls change this demonstration only.
main.contentPlace the featured invitation and three event articles here.
Desktop: main and aside sit beside each other. The main column receives two shares of the available width.
Preview the finished practice
This target is a visual reference, not starter code. Use its width controls to inspect the layout. Your own code stays separate.
Build it in small steps
This focused practice builds the wide layout. Use the 1280px preview to inspect it. The responsive module later adapts the same idea for phones.
The workshop opens in a new tab. Your own code carries forward; each step has a focused check and an optional hint.
Start workshop(opens in a new tab)7 steps · Saved work · Instant feedback
Look up the property you need
You do not need to memorize every value. Use documentation to check a property, then explain what it changes in this layout.
Your turn: repair one problem
This is a separate saved challenge. The workshop completion and code remain unchanged.
The checks below assess this repair. Passing them does not complete the guided workshop.
YOUR TURN
Repair the column ratio
Work through the checklist in styles.css. Run the preview, then check your work.
- In
styles.css, find the existing rule with selector.siteoutside all media blocks. - Set its
grid-template-columnsproperty tominmax(0, 2fr) minmax(0, 1fr). - Keep the supplied page content, classes, IDs and link destinations unless a checklist item explicitly changes them.
- Keep the second track at
minmax(0, 1fr)and gap at20px.
Edit styles.css and watch the preview update after you pause typing. Open index.html to inspect its stylesheet link. Run or Check saves immediately. Word wrap is enabled.
Ready to checkRun the checks to see your results here.
Your check results
Need a nudge?
Focus on the requested rule
Change the first .site track from minmax(0, 1fr) to minmax(0, 2fr).
Compare the two preview widths
Use the Phone and Desktop preview sizes. The preview width controls the media queries; the size of your monitor does not. Keep unrelated declarations and all supplied content.
One possible solution
Your code may look different and still be correct. Compare the approach with your own.
Explain the rule you changed and compare both preview widths. Your workshop code is a separate saved project.
/* STYLE ALL ELEMENTS */
* {
box-sizing: border-box;
}
/* STYLE BODY */
body {
margin: 0;
font-family: Arial, sans-serif;
line-height: 1.6;
color: #17283c;
background-color: #eef4f8;
}
/* STYLE CLASS SITE DIRECT CHILD ALL ELEMENTS */
.site > * {
padding: 20px;
border-radius: 10px;
background-color: white;
}
/* STYLE CLASS MASTHEAD AND CLASS FOOTER */
.masthead,
.footer {
background-color: #12304a;
color: white;
}
/* STYLE A */
a {
color: #007396;
}
/* STYLE CLASS SITE */
.site {
display: grid;
gap: 20px;
}
/* STYLE CLASS SITE LATER RULE 2 */
.site {
width: 92%;
max-width: 1100px;
margin: 24px auto;
}
/* STYLE CLASS SITE LATER RULE 3 */
.site {
grid-template-areas: "header header" "nav nav" "main aside" "footer footer";
}
/* STYLE CLASS MASTHEAD */
.masthead {
grid-area: header;
}
/* STYLE CLASS NAVIGATION */
.navigation {
grid-area: nav;
}
/* STYLE CLASS CONTENT */
.content {
grid-area: main;
}
/* STYLE CLASS DATES */
.dates {
grid-area: aside;
}
/* STYLE CLASS FOOTER */
.footer {
grid-area: footer;
}
/* STYLE CLASS SITE LATER RULE 4 */
.site {
grid-template-columns: minmax(0, 2fr) minmax(0, 1fr);
}
/* STYLE CLASS CONTENT LATER RULE 2 */
.content {
min-height: 240px;
}
/* STYLE CLASS DATES LATER RULE 2 */
.dates {
align-self: start;
}Ready to try it?
Practice in your browser and see your results.
Progress details
Have a question?
Ask the Code Zone community.
Ask a question in The Code Zone (opens in a new tab)Continue learning

7 days freeTry The Code Zone
THE CODE ZONE COMMUNITY
Your next step is easier together.
Try the community free for 7 days.
No charge during your trial. Choose your plan on Skool.
- Ask questions and get support in the community
- Watch every course video walkthrough
- Find a study buddy in the 24/7 study room
Make the most of your trial with Premium.
Choose Premium on Skool to try Thursday live help sessions. Bring your questions, work through code, and get unstuck together.
Scheduled Thursdays in Eastern Time. Check the Skool calendar for your local date and time.
Have a website account? Sign in