I’ve laid pages out many difÂferÂent ways, but my favorite is using CSS grid along with a few othÂer tricks. The examÂple below is vanilÂla HTML/CSS; howÂevÂer, the conÂcept can be adaptÂed to any SPA framework.
Before going into the full examÂple, I’ll point out a few interÂestÂing tidbits.
body {
min-height: 100vh;
margin: 0;
display: grid;
}
This ensures the body occuÂpies the full screen height, allowÂing us to stick the page footÂer to the botÂtom if the conÂtent isn’t tall enough to push it offÂscreen. The vh
unit is ​“view height” and 100vh
means ​“100% of the view height.”
.app {
display: grid;
grid-template-rows:
[header-start]
min-content
[header-end content-start side-start]
1fr
[content-end side-end footer-start]
min-content
[footer-end];
grid-template-columns:
[header-start content-start footer-start]
auto
[content-end side-start]
300px
[side-end header-end footer-end];
}
The above sets up the page with a grid, namÂing each line of the grid (names fall niceÂly between the [ ]
brackÂets). In the full examÂple, you will see how we restrucÂture the grid through media queries. As long as all of our line names are present, the page will reflow seamÂlessÂly, offerÂing a clean entry point into high-levÂel, responÂsive design.
.header {
// ...
grid-row: header-start / header-end;
grid-column: header-start / header-end;
// ...
}
The above allows us to define what part of the grid the headÂer should occuÂpy using the named lines from the grid definition.
.header {
// ...
position: sticky;
top: 0;
// ...
}
The above approach allows the headÂer to remain at the top of the page when scrolling. You can choose a difÂferÂent valÂue for top to get it to stick to a difÂferÂent point. The benÂeÂfit of position: sticky
over fixed or absolute is that it allows the headÂer to conÂtinÂue to be a part of the layÂout of the grid. With someÂthing like position: fixed
you would need to add some top marÂgin to the conÂtent to comÂpenÂsate for the height of the headÂer. Less than ideal.
.content {
padding: 20px;
grid-row: content-start / content-end;
grid-column: content-start / content-end;
background: green;
display: grid;
grid-template-columns: repeat(auto-fill, 500px);
grid-template-rows: 300px;
grid-auto-columns: 500px;
grid-auto-rows: 300px;
grid-auto-flow: dense;
grid-row-gap: 20px;
grid-column-gap: 20px;
justify-content: center;
}
The above is simÂply a way to lay out the boxÂes to give the conÂtent the necÂesÂsary height.
And, finalÂly, the full examÂple is here.
Phone
Wide Screen
NarÂrow Screen
Looking for more like this?
Sign up for our monthly newsletter to receive helpful articles, case studies, and stories from our team.
When to “shape up” versus be more “agile”
May 30, 2024Should you develop your new software using the Agile or Shape Up method? Here’s how to decide.
Read moreLessons Learned from our Associate Developer
September 13, 2023One of our Associate Software Developers, Rohit, reflects on his time at MichiganLabs working on a short-term project, what he learned about real-world development, and the software consultancy business model.
Read moreA 3-part framework for getting your software project approved internally
September 25, 2024Explore this strategic approach to securing internal buy-in for your custom software projects. The framework emphasizes starting with a lean business case, engaging key stakeholders across the organization to align economic, operational, and technical considerations, and embracing an iterative learning process to make informed decisions.
Read more