Which of the following best explains why custom grids give developers more control in layout design?
Think about how grids let you decide exactly where each box goes.
Custom grids let developers define exact rows and columns, controlling element placement precisely. This flexibility is not possible with fixed frameworks or automatic layouts.
What is the output CSS of this Sass mixin usage?
@mixin grid-columns($count) {
display: grid;
grid-template-columns: repeat($count, 1fr);
}
.container {
@include grid-columns(3);
}Check how the repeat function is used in CSS grid.
The mixin sets display: grid and uses repeat($count, 1fr) to create equal columns. Option A matches the correct CSS output.
Given this Sass code, what CSS selector is generated for the nested .item?
.grid {
display: grid;
& > .item {
padding: 1rem;
}
}The & symbol represents the parent selector in Sass.
The & > .item means direct child .item of .grid. So the selector is .grid > .item.
What visual effect does setting grid-gap: 2rem; have on a CSS grid container?
Think about spacing between boxes in a grid.
The grid-gap property adds space between rows and columns inside the grid container, separating the grid items visually.
Which practice improves accessibility when using custom CSS grids for page layout?
Think about how screen readers and keyboard users experience the page.
Using semantic HTML and matching keyboard navigation order to the visual grid ensures all users can understand and navigate the layout effectively.