Introduction
Options for structuring your pages with Hubble, including global styles, required scaffolding, grid system, and more.HTML5 doctype
Hubble makes use of certain HTML elements and CSS properties that require the use of the HTML5 doctype. Include it at the beginning of all your projects.
Mobile first
Hubble employs a 100% mobile first grid system and responsive breakpoints.
Instead of adding on optional mobile styles, they're baked right into the base, so specific styles for larger screens overide the default(mobile) rather than the otherway around.
To ensure proper rendering and touch zooming, add the viewport meta tag to your <head>
.
You can disable zooming capabilities on mobile devices by adding user-scalable=no
to the viewport meta tag.
This disables zooming, meaning users are only able to scroll,
and results in your site feeling a bit more like a native application.
Overall, we don't recommend this on every site, so use caution!
CSS Reset
For improved cross-browser rendering, we use YUI CSS reset.
Containers
Containers are the most basic layout element in Hubble and are required when using our default grid system.
Choose from a responsive, fixed-width container (meaning its max-width
changes at each breakpoint)
or fluid-width (meaning it’s 100%
wide all the time).
While containers can be nested, most layouts do not require a nested container.
Use .container-fluid
for a full width container, spanning the entire width of the viewport.
Sticky footer
Hubble includes a sticky footer. A footer that always sits at the bottom of the page, even in cases where the page height is shorter than the browser.
The sticky footer is easy to setup and relies of a fixed height footer.
If your footer height is dynamic and needs to change at different browser widths, use a combination of
Hubble's breakpoint mixins with the stickyFooter
mixin.
// Medium devices (tablets, 768px and up)
@include media-breakpoint-up(md) {
@include stickyFooter(350px);
}
The default footer height is set Hubble's
_config.scss
file.
Responsive breakpoints
Since Hubble is developed to be mobile first, we use a handful of media queries to create sensible breakpoints for layouts and interfaces. These breakpoints are mostly based on minimum viewport widths and allow us to scale up elements as the viewport changes. Hubble primarily uses the following media query ranges—or breakpoints—in our source Sass files for our layout, grid system, and components.
// Extra small devices (portrait phones, less than 576px)
// No media query since this is the default in Bootstrap
// Small devices (landscape phones, 576px and up)
@media (min-width: 576px) { ... }
// Medium devices (tablets, 768px and up)
@media (min-width: 768px) { ... }
// Large devices (desktops, 992px and up)
@media (min-width: 992px) { ... }
// Extra large devices (large desktops, 1200px and up)
@media (min-width: 1200px) { ... }
Since we write our source CSS in Sass, all our media queries are available via Sass mixins:
@include media-breakpoint-up(xs) { ... }
@include media-breakpoint-up(sm) { ... }
@include media-breakpoint-up(md) { ... }
@include media-breakpoint-up(lg) { ... }
@include media-breakpoint-up(xl) { ... }
// Example usage:
@include media-breakpoint-up(sm) {
.some-class {
display: block;
}
}
We occasionally use media queries that go in the other direction (the given screen size or smaller):
// Extra small devices (portrait phones, less than 576px)
@media (max-width: 575px) { ... }
// Small devices (landscape phones, less than 768px)
@media (max-width: 767px) { ... }
// Medium devices (tablets, less than 992px)
@media (max-width: 991px) { ... }
// Large devices (desktops, less than 1200px)
@media (max-width: 1199px) { ... }
// Extra large devices (large desktops)
// No media query since the extra-large breakpoint has no upper bound on its width
Once again, these media queries are also available via Sass mixins:
@include media-breakpoint-down(xs) { ... }
@include media-breakpoint-down(sm) { ... }
@include media-breakpoint-down(md) { ... }
@include media-breakpoint-down(lg) { ... }