Over a dozen reusable components built to provide iconography, dropdowns, input groups, navigation, alerts, and much more.
Alerts
Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages.
Examples
Wrap any text and an optional dismiss button in .alert and one of the four contextual classes (e.g., .alert-success) for basic alert messages.
No default class
Alerts don't have default classes, only base and modifier classes. A default gray alert doesn't make too much sense, so you're required to specify a type via contextual class. Choose from success, info, warning, or danger.
Well done! You successfully read this important alert message.
Heads up! This alert needs your attention, but it's not super important.
Warning! Better check yourself, you're not looking too good.
Oh snap! Change a few things up and try submitting again.
Adding an icon
Place the <i class="icon icon-warning" aria-hidden="true"></i> before the strong tag, switching out .icon-warning to match the correct icon to alert.
Well done! You successfully read this important alert message.
Heads up! This alert needs your attention, but it's not super important.
Warning! Better check yourself, you're not looking too good.
Oh snap! Change a few things up and try submitting again.
Dismissible alerts
Build on any alert by adding an optional .alert-dismissible and close button.
Group a series of buttons together on a single line with the button group. Add on optional JavaScript radio and checkbox style behavior with our buttons plugin.
Tooltips & popovers in button groups require special setting
When using tooltips or popovers on elements within a .btn-group, you'll have to specify the option container: 'body' to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the tooltip or popover is triggered).
Ensure correct role and provide a label
In order for assistive technologies – such as screen readers – to convey that a series of buttons is grouped, an appropriate role attribute needs to be provided. For button groups, this would be role="group", while toolbars should have a role="toolbar".
One exception are groups which only contain a single control (for instance the justified button groups with <button> elements) or a dropdown.
In addition, groups and toolbars should be given an explicit label, as most assistive technologies will otherwise not announce them, despite the presence of the correct role attribute. In the examples provided here, we use aria-label, but alternatives such as aria-labelledby can also be used.
Basic example
Wrap a series of buttons with .btn in .btn-group.
Button toolbar
Combine sets of <div class="btn-group"> into a <div class="btn-toolbar"> for more complex components.
Sizing
Instead of applying button sizing classes to every button in a group, just add .btn-group-* to each .btn-group, including when nesting multiple groups.
Nesting
Place a .btn-group within another .btn-group when you want dropdown menus mixed with a series of buttons.
Make a group of buttons stretch at equal sizes to span the entire width of its parent. Also works with button dropdowns within the button group.
Handling borders
Due to the specific HTML and CSS used to justify buttons (namely display: table-cell), the borders between them are doubled. In regular button groups, margin-left: -1px is used to stack the borders instead of removing them. However, margin doesn't work with display: table-cell. As a result, depending on your customizations to Bootstrap, you may wish to remove or re-color the borders.
IE8 and borders
Internet Explorer 8 doesn't render borders on buttons in a justified button group, whether it's on <a> or <button> elements. To get around that, wrap each button in another .btn-group.
If the <a> elements are used to act as buttons – triggering in-page functionality, rather than navigating to another document or section within the current page – they should also be given an appropriate role="button".
With <button> elements
To use justified button groups with <button> elements, you must wrap each button in a button group. Most browsers don't properly apply our CSS for justification to <button> elements, but since we support button dropdowns, we can work around that.
Call-outs
Default call out boxes have both top and bottom shadows. To make a call out box add the base class
.call-out-box to any block level element.
Call outs can be positioned using grids, and can contain other components.
Default
Success story
No Top Border
You can remove the top shadow by adding the modifier class Deprecated:.call-out-box--no-topExpected:.call-out-box .no-topNew:.call-out-body this
class helps give a starting baseline for an inner contents of the call-out.
Look, I'm in a call-out!
No Bottom Border
You can remove the bottom shadow by adding the modifier class Deprecated:.call-out-box--no-bottomExpected:.call-out-box .no-bottom
Look, I'm in a call-out!
Cartridge colors
For a quicker load time, use the CSS styles instead of image files when showing cartridge colors.
Individual color symbols
Color printer symbol
Place .cartridge-cmyk after each color class to arrange the colors inline with one another. The colors must be written in the order shown below for the layering to work.
Mono printer symbol
Place .cartridge-mono after each color class to arrange the colors inline with one another. The colors must be written in the order shown below for the layering to work.
Dot-matrix printer symbol
Use .cartridge-dot-matrix to create this symbol.
Sizing and alignment
The default alignment is left-aligned. You can change the alignment by wrapping the group of colors in a div with the following class options: .cartridge-center, .cartridge-right and .cartridge-left. If it's a color, mono or dot-matrix printer symbol, you will need to add .cartridge-cmyk, .cartridge-mono or .cartridge-dot-matrix after the alignment class for correct spacing. If you need to create a block element, change the .cartridge to .cartridge-block. You can also make the color dots smaller by changing the .cartridge to .cartridge-sm.
Dropdowns
Toggleable, contextual menu for displaying lists of links. Made interactive with the dropdown JavaScript plugin.
Example
Wrap the dropdown's trigger and the dropdown menu within .dropdown, or another element that declares position: relative;. Then add the menu's HTML.
By default, a dropdown menu is automatically positioned 100% from the top and along the left side of its parent. Add .dropdown-menu-right to a .dropdown-menu to right align the dropdown menu.
May require additional positioning
Dropdowns are automatically positioned via CSS within the normal flow of the document. This means dropdowns may be cropped by parents with certain overflow properties or appear out of bounds of the viewport. Address these issues on your own as they arise.
Deprecated .pull-right alignment
As of v3.1.0, we've deprecated .pull-right on dropdown menus. To right-align a menu, use .dropdown-menu-right. Right-aligned nav components in the navbar use a mixin version of this class to automatically align the menu. To override it, use .dropdown-menu-left.
Headers
Add a header to label sections of actions in any dropdown menu.
The default text color is n6 on a white background. For light backgrounds (recommended brand colors: n1-n4, b8), text should be black. For dark backgrounds (recommended brand colors: n6-n9, b7, black), text should be white.
Basic
Optional
Usage notes
Optional rule can be used when additional visual separation is need from content blocks. Same color recommendations apply as the basic figure caption.
Input groups
Extend form controls by adding text or buttons before, after, or on both sides of any text-based <input>. Use .input-group with an .input-group-addon or .input-group-btn to prepend or append elements to a single .form-control.
Textual <input>s only
Avoid using <select> elements here as they cannot be fully styled in WebKit browsers.
Avoid using <textarea> elements here as their rows attribute will not be respected in some cases.
Tooltips & popovers in input groups require special setting
When using tooltips or popovers on elements within an .input-group, you'll have to specify the option container: 'body' to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the tooltip or popover is triggered).
Don't mix with other components
Do not mix form groups or grid column classes directly with input groups. Instead, nest the input group inside of the form group or grid-related element.
Always add labels
Screen readers will have trouble with your forms if you don't include a label for every input. For these input groups, ensure that any additional label or functionality is conveyed to assistive technologies.
The exact technique to be used (visible <label> elements, <label> elements hidden using the .sr-only class, or use of the aria-label, aria-labelledby, aria-describedby, title or placeholder attribute) and what additional information will need to be conveyed will vary depending on the exact type of interface widget you're implementing. The examples in this section provide a few suggested, case-specific approaches.
Basic example
Place one add-on or button on either side of an input. You may also place one on both sides of an input.
We do not support multiple add-ons (.input-group-addon or .input-group-btn) on a single side.
We do not support multiple form-controls in a single input group.
Transparency & Input Group Focus (Search Bar)
Using a combination of border helper classes, the .bg-transparent class, and the .input-group-focus class, one can create a search bar. The .input-group-focus class removes the border of all interior child elements, removes the :hover and :focus styling for any child input tags, and resets the :hover and :focus to occur on the element with the .input-group-focus.
Also, styling the anchor tag with the same styles as those normally given to the span tag allows links to be made around icons, such as those in the examples below.
Sizing
Add the relative form sizing classes to the .input-group itself and contents within will automatically resize—no need for repeating the form control size classes on each element.
Checkboxes and radio addons
Place any checkbox or radio option within an input group's addon instead of text.
Button addons
Buttons in input groups are a bit different and require one extra level of nesting. Instead of .input-group-addon, you'll need to use .input-group-btn to wrap the buttons. This is required due to default browser styles that cannot be overridden.
Buttons with dropdowns
Segmented buttons
Multiple buttons
While you can only have one add-on per side, you can have multiple buttons inside a single .input-group-btn.
Jumbotron
A lightweight, flexible component that can optionally extend the entire viewport to showcase key content on your site.
Basic Example
Hello, world!
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
The jumbotron has a unique styling that is not found elsewhere in the framework. This is applied by using the .jumbo-style class.
Remove the class to allow the default framework styling to take effect.
Hello, world!
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
If you need to duplicate the styling of the jumbotron header, you can do so by adding class .jumbo to any <h1> tag.
Jumbotron H1
Regular H1
Sizing
To change the width and/or height of the Jumbotron, use the following approaches.
Full Width
To make the jumbotron full width, place it outside all .container classes and instead add a .container class within.
Small
Hello, world!
This is a simple hero unit.
Medium
Hello, world!
This is a simple hero unit.
Large
Hello, world!
This is a simple hero unit.
Extra Large
Hello, world!
This is a simple hero unit.
Content Alignment
The content within the jumbotron can be positioned in the following nine positions. The content must be wrapped within a div with the appropriate alignment class as shown in the examples below. To retain the padding from the jumbotron, add the .align-container class to the same container.
Extend Jumbotron with the grid system by applying appropriate classes as seen below. This allows for different widths of text for different designs and layouts.
Hello, world!
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
When using images in the jumbotron, there are three rules to remember:
Always place any content within a grid (i.e., a column div nested under a row div). If this is not done, the content will always display behind an image placed outside of the area.
Place the image markup before the grid to make it show behind the content.
Place the image markup after the grid to make it show in front of the content.
Image Behind Content
In the example below, the 400 x 400 background image is shown behind the grid (which also contains a 100 x 100 image) because the 400 x 400 image markup is placed above the grid markup.
Hello, world!
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
In the example below, the 400 x 400 background image is shown on top of the grid (which also contains a 100 x 100 image) because the 400 x 400 image markup is placed after the grid markup.
Hello, world!
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
The third party Picturefill plugin is implemented with a few markup updates. The last image specified in the markup is for mobile devices and the min-width breakpoints specified align with Bootstrap's breakpoints.
Hello, world!
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
Using the class .transition-image for an <img> tag enables it to be positioned lower than the container by setting a negative bottom margin with an inline style or through a JS DOM manipulation.
Hello, world!
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
Add any of the below mentioned modifier classes to change the appearance of a label.
DefaultInverseImportantInfoSuccessWarning
Have tons of labels?
Rendering problems can arise when you have dozens of inline labels within a narrow container, each containing its own inline-block element (like an icon). The way around this is setting display: inline-block;. For context and an example, see #13219.
Lexicons
Includes 413 icons in font format from the LXCore custom "Lexicons" set. The icons are vector based, which allows them to be scaled to any size without image pixelation. Any color may also be applied through with .text--{color} classes.
Icon classes cannot be directly combined with other components. They should not be used along with other classes on the same element. Instead, add a nested <span> and apply the icon classes to the <span>.
Only for use on empty elements
Icon classes should only be used on elements that contain no text content and have no child elements.
Accessible icons
Modern versions of assistive technologies will announce CSS generated content, as well as specific Unicode characters. To avoid unintended and confusing output in screen readers (particularly when icons are used purely for decoration), we hide them with the aria-hidden="true" attribute.
If you're using an icon to convey meaning (rather than only as a decorative element), ensure that this meaning is also conveyed to assistive technologies – for instance, include additional content, visually hidden with the .sr-only class.
If you're creating controls with no other text (such as a <button>> that only contains an icon), you should always provide alternative content to identify the purpose of the control, so that it will make sense to users of assistive technologies. In this case, you could add an aria-label attribute on the control itself.
Examples
Use icons in buttons, button groups for a toolbar, navigation, or prepended form inputs.
An icon used in an alert to convey that it's an error message should use additional .sr-only text to convey this hint to users of assistive technologies.
Error:
Enter a valid email address
List group
List groups are a flexible and powerful component for displaying not only simple lists of elements, but complex ones with custom content.
Basic example
The most basic list group is simply an unordered list with list items, and the proper classes. Build upon it with the options that follow, or your own CSS as needed.
Cras justo odio
Dapibus ac facilisis in
Morbi leo risus
Porta ac consectetur ac
Vestibulum at eros
Badges
Add the badges component to any list group item and it will automatically be positioned on the right.
14
Cras justo odio
2
Dapibus ac facilisis in
1
Morbi leo risus
Linked items
Linkify list group items by using anchor tags instead of list items (that also means a parent <div> instead of an <ul>). No need for individual parents around each element.
List group items may be buttons instead of list items (that also means a parent <div> instead of an <ul>). No need for individual parents around each element. Don't use the standard .btn classes here.
Disabled items
Add .disabled to a .list-group-item to gray it out to appear disabled.
Make sure to add the .hidden class, so it only shows when triggered. If you wish to center the loading image, you must also include .center-block.
Square loading image
Loading image sizes
Loading images are available in 3 sizes: small (24px), default (36px), and large (48px). To use the small size, add .loading-img-sm to the div. To use the large size, add .loading-img-lg to the div.
Loading image colors
The loading image will switch out automatically based on the background color it's displayed against.
Loading modal
If you need messaging for a whole page, use this loading modal.
Loading
Media object
Abstract object styles for building various types of components (like blog comments, Tweets, etc) that feature a left- or right-aligned image alongside textual content.
Default media
The default media displays a media object (images, video, audio) to the left or right of a content block.
Media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis. Fusce condimentum nunc ac nisi vulputate fringilla. Donec lacinia congue felis in faucibus.
Media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis. Fusce condimentum nunc ac nisi vulputate fringilla. Donec lacinia congue felis in faucibus.
Nested media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis. Fusce condimentum nunc ac nisi vulputate fringilla. Donec lacinia congue felis in faucibus.
Media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis.
Media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis.
The classes .pull-left and .pull-right also exist and were previously used as part of the media component, but are deprecated for that use as of v3.3.0. They are approximately equivalent to .media-left and .media-right, except that .media-right should be placed after the .media-body in the html.
Media alignment
The images or other media can be aligned top, middle, or bottom. The default is top aligned.
Top aligned media
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis. Fusce condimentum nunc ac nisi vulputate fringilla. Donec lacinia congue felis in faucibus.
Donec sed odio dui. Nullam quis risus eget urna mollis ornare vel eu leo. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Middle aligned media
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis. Fusce condimentum nunc ac nisi vulputate fringilla. Donec lacinia congue felis in faucibus.
Donec sed odio dui. Nullam quis risus eget urna mollis ornare vel eu leo. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Bottom aligned media
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis. Fusce condimentum nunc ac nisi vulputate fringilla. Donec lacinia congue felis in faucibus.
Donec sed odio dui. Nullam quis risus eget urna mollis ornare vel eu leo. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Media list
With a bit of extra markup, you can use media inside list (useful for comment threads or articles lists).
Media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis.
Nested media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis.
Nested media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis.
Nested media heading
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis.
Navbar
Default navbar
Navbars are responsive meta components that serve as navigation headers for your application or site. They begin collapsed (and are toggleable) in mobile views and become horizontal as the available viewport width increases.
Justified navbar nav links are currently not supported.
Overflowing content
Since Bootstrap doesn't know how much space the content in your navbar needs, you might run into issues with content wrapping into a second row. To resolve this, you can:
Change the point at which your navbar switches between collapsed and horizontal mode. Customize the @grid-float-breakpoint variable or add your own media query.
Requires JavaScript plugin
If JavaScript is disabled and the viewport is narrow enough that the navbar collapses, it will be impossible to expand the navbar and view the content within the .navbar-collapse.
The responsive navbar requires the collapse plugin to be included in your version of Bootstrap.
Changing the collapsed mobile navbar breakpoint
The navbar collapses into its vertical mobile view when the viewport is narrower than @grid-float-breakpoint, and expands into its horizontal non-mobile view when the viewport is at least @grid-float-breakpoint in width. Adjust this variable in the Less source to control when the navbar collapses/expands. The default value is 768px (the smallest "small" or "tablet" screen).
Make navbars accessible
Be sure to use a <nav> element or, if using a more generic element such as a <div>, add a role="navigation" to every navbar to explicitly identify it as a landmark region for users of assistive technologies.
Brand image
Replace the navbar brand with your own image by swapping the text for an <img>. Since the .navbar-brand has its own padding and height, you may need to override some CSS depending on your image.
Forms
Place form content within .navbar-form for proper vertical alignment and collapsed behavior in narrow viewports. Use the alignment options to decide where it resides within the navbar content.
As a heads up, .navbar-form shares much of its code with .form-inline via mixin. Some form controls, like input groups, may require fixed widths to be show up properly within a navbar.
Mobile device caveats
There are some caveats regarding using form controls within fixed elements on mobile devices. See our browser support docs for details.
Always add labels
Screen readers will have trouble with your forms if you don't include a label for every input. For these inline forms, you can hide the labels using the .sr-only class. There are further alternative methods of providing a label for assistive technologies, such as the aria-label, aria-labelledby or title attribute. If none of these is present, screen readers may resort to using the placeholder attribute, if present, but note that use of placeholder as a replacement for other labelling methods is not advised.
Buttons
Add the .navbar-btn class to <button> elements not residing in a <form> to vertically center them in the navbar.
Context-specific usage
Like the standard button classes, .navbar-btn can be used on <a> and <input> elements. However, neither .navbar-btn nor the standard button classes should be used on <a> elements within .navbar-nav.
Text
Wrap strings of text in an element with .navbar-text, usually on a <p> tag for proper leading and color.
Non-nav links
For folks using standard links that are not within the regular navbar navigation component, use the .navbar-link class to add the proper colors for the default and inverse navbar options.
Component alignment
Align nav links, forms, buttons, or text, using the .navbar-left or .navbar-right utility classes. Both classes will add a CSS float in the specified direction. For example, to align nav links, put them in a separate <ul> with the respective utility class applied.
These classes are mixin-ed versions of .pull-left and .pull-right, but they're scoped to media queries for easier handling of navbar components across device sizes.
Right aligning multiple components
Navbars currently have a limitation with multiple .navbar-right classes. To properly space content, we use negative margin on the last .navbar-right element. When there are multiple elements using that class, these margins don't work as intended.
We'll revisit this when we can rewrite that component in v4.
Fixed to top
Add .navbar-fixed-top and include a .container or .container-fluid to center and pad navbar content.
Body padding required
The fixed navbar will overlay your other content, unless you add padding to the top of the <body>. Try out your own values or use our snippet below. Tip: By default, the navbar is 50px high.
Make sure to include this after the core Bootstrap CSS.
Fixed to bottom
Add .navbar-fixed-bottom and include a .container or .container-fluid to center and pad navbar content.
Body padding required
The fixed navbar will overlay your other content, unless you add padding to the bottom of the <body>. Try out your own values or use our snippet below. Tip: By default, the navbar is 50px high.
Make sure to include this after the core Bootstrap CSS.
Static top
Create a full-width navbar that scrolls away with the page by adding .navbar-static-top and include a .container or .container-fluid to center and pad navbar content.
Unlike the .navbar-fixed-* classes, you do not need to change any padding on the body.
Inverted navbar
Modify the look of the navbar by adding .navbar-inverse.
Navs
Navs available in Bootstrap have shared markup, starting with the base .nav class, as well as shared states. Swap modifier classes to switch between each style.
Using navs for tab panels requires JavaScript tabs plugin
For tabs with tabbable areas, you must use the tabs JavaScript plugin. The markup will also require additional role and ARIA attributes – see the plugin's example markup for further details.
Make navs used as navigation accessible
If you are using navs to provide a navigation bar, be sure to add a role="navigation" to the most logical parent container of the <ul>, or wrap a <nav> element around the whole navigation. Do not add the role to the <ul> itself, as this would prevent it from being announced as an actual list by assistive technologies.
Tabs
Note the .nav-tabs class requires the .nav base class.
Have fun with it. That's what painting is all about. It should make you feel good when you paint. Let's put some happy little clouds in our world. We spend so much of our life looking - but never seeing.
Example 2
You gotta think like a tree. There are no mistakes. You can fix anything that happens. We don't make mistakes we just have happy little accidents. Just let go - and fall like a little waterfall.
Example 3
It's so important to do something every day that will make you happy. You're the greatest thing that has ever been or ever will be. You're special. You're so very special. That's a crooked tree. We'll send him to Washington. We don't have to be concerned about it. We just have to let it fall where it will.
Pills
Take that same HTML structure, but use .nav-pills instead. This example also shows how to change the markup when tabs are treated as navigational links.
Have fun with it. That's what painting is all about. It should make you feel good when you paint. Let's put some happy little clouds in our world. We spend so much of our life looking - but never seeing.
Profile
You gotta think like a tree. There are no mistakes. You can fix anything that happens. We don't make mistakes we just have happy little accidents. Just let go - and fall like a little waterfall.
Messages
It's so important to do something every day that will make you happy. You're the greatest thing that has ever been or ever will be. You're special. You're so very special. That's a crooked tree. We'll send him to Washington. We don't have to be concerned about it. We just have to let it fall where it will.
Pills can also be vertically stacked. Just add .nav-stacked.
Have fun with it. That's what painting is all about. It should make you feel good when you paint. Let's put some happy little clouds in our world. We spend so much of our life looking - but never seeing.
Profile
You gotta think like a tree. There are no mistakes. You can fix anything that happens. We don't make mistakes we just have happy little accidents. Just let go - and fall like a little waterfall.
Messages
It's so important to do something every day that will make you happy. You're the greatest thing that has ever been or ever will be. You're special. You're so very special. That's a crooked tree. We'll send him to Washington. We don't have to be concerned about it. We just have to let it fall where it will.
Justified
Justified navbar nav links are currently not supported.
Safari and responsive justified navs
As of v9.1.2, Safari exhibits a bug in which resizing your browser horizontally causes rendering errors in the justified nav that are cleared upon refreshing. This bug is also shown in the justified nav example.
Disabled links
For any nav component (tabs or pills), add .disabled for gray links and no hover effects.
Link functionality not impacted
This class will only change the <a>'s appearance, not its functionality. Use custom JavaScript to disable links here.
These navs can be placed in either the right or left rail and have a base class of .nav with an extra class of .nav-rail for necessary styling. The nav should also always be wrapped in a nav html element.
LXK Affixed Navigation
The affixed nav uses the bootstrap scrollspy and affix plugins to work properly. It needs the class .nav-affix applied to the nav element for ready-made javascript and it is then styled with the class .nav-rail class on the ul element.
A simple shell for an h1 to appropriately space out and segment sections of content on a page. It can utilize the h1's default small element, as well as most other components (with additional styles).
Example page header Subtext for header
Page header without bottom rule
A simple shell for an h1 to appropriately space out and segment sections of content on a page. It can utilize the h1's default small element, as well as most other components (with additional styles).
Example page header Subtext for header
Pagination
Design patterns for pagination should be chosen based on the specific environment it will be used. We do not have a one-pagination-fits-all. Refer to the sections below to help you determine the best pagination pattern to use for your specific UX/UI needs. Our design was inspired by Rdio. It features large blocks to accommodate ideal click/touch areas.
Default pagination
This pagination is our most used design pattern. Best for search results where only a small number of returned results are expected (5 pages or less). If this pattern is used with more than 5 pages, the placeholder ellipsis would be used to keep the pagination from breaking on small mobile phones, which is not the most ideal experience. In that case, it would be better to use the page number input design.
Labelling the pagination component
The pagination component should be wrapped in a <nav> element to identify it as a navigation section to screen readers and other assistive technologies. In addition, as a page is likely to have more than one such navigation section already (such as the primary navigation in the header, or a sidebar navigation), it is advisable to provide a descriptive aria-label for the <nav> which reflects its purpose. For example, if the pagination component is used to navigate between a set of search results, an appropriate label could be aria-label="Search results navigation".
Disabled and active states
Links are customizable for different circumstances. Use .disabled for unclickable links and .active to indicate the current page.
You can optionally swap out active or disabled anchors for <span>, or omit the anchor in the case of the previous/next arrows, to remove click functionality while retaining intended styles.
Sizing
Add .pagination-lg or .pagination-sm for additional sizes.
Page number input
This pagination is based on our default design, but is tailored for searches that will return a large number of results (6 pages or more). The input box allows users to manually type in a specific page number. Users can advance to the first or last page, in addition to one page prior or next. Links can also use the general .disabled utility class from the default pagination design. The additional sizing options are not availabe for this layout, because it has built-in resizing for touch devices. Add .pull-right to the ul tag to right-align pagination.
Advance by page (Pager)
This design pattern is best used for navigating from page to page within a blog, magazine, PDF, etc. Links can also use the general .disabled utility class from the default pagination design.
Translation considerations
When using pagination designs containing words in addition to icons, translations need to be considered, especially when used outside of english-speaking locales.
Default example
By default, the buttons are centered within the div. The words and arrow styles are interchangable.
Button Alignment
Alternatively, you can align each button to their respective sides. Add class="previous" and class="next" to the li tags.
Panels
While not always necessary, sometimes you need to put your DOM in a box. For those situations, try the panel component.
Basic example
By default, all the .panel does is apply some basic border and padding to contain some content.
Basic panel example
Panel with heading
Easily add a heading container to your panel with .panel-heading. You may also include any <h1>-<h6> with a .panel-title class to add a pre-styled heading. However, the font sizes of <h1>-<h6> are overridden by .panel-heading.
For proper link coloring, be sure to place links in headings within .panel-title.
Panel heading without title
Panel content
Panel title
Panel content
Panel with footer
Wrap buttons or secondary text in .panel-footer. Note that panel footers do not inherit colors and borders when using contextual variations as they are not meant to be in the foreground.
Panel content
Contextual alternatives
Like other components, easily make a panel more meaningful to a particular context by adding any of the contextual state classes.
Panel title
Panel content
Panel title
Panel content
Panel title
Panel content
Panel title
Panel content
Panel title
Panel content
With tables
Add any non-bordered .table within a panel for a seamless design. If there is a .panel-body, we add an extra border to the top of the table for separation.
Panel heading
Some default panel content here. Nulla vitae elit libero, a pharetra augue. Aenean lacinia bibendum nulla sed consectetur. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Nullam id dolor id nibh ultricies vehicula ut id elit.
#
First Name
Last Name
Username
1
Mark
Otto
@mdo
2
Jacob
Thornton
@fat
3
Larry
the Bird
@twitter
If there is no panel body, the component moves from panel header to table without interruption.
Panel heading
#
First Name
Last Name
Username
1
Mark
Otto
@mdo
2
Jacob
Thornton
@fat
3
Larry
the Bird
@twitter
With list groups
Easily include full-width list groups within any panel.
Panel heading
Some default panel content here. Nulla vitae elit libero, a pharetra augue. Aenean lacinia bibendum nulla sed consectetur. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Nullam id dolor id nibh ultricies vehicula ut id elit.
Cras justo odio
Dapibus ac facilisis in
Morbi leo risus
Porta ac consectetur ac
Vestibulum at eros
Progress bars
Provide up-to-date feedback on the progress of a workflow or action with simple yet flexible progress bars.
Cross-browser compatibility
Progress bars use CSS3 transitions and animations to achieve some of their effects. These features are not supported in Internet Explorer 9 and below or older versions of Firefox. Opera 12 does not support animations.
Content Security Policy (CSP) compatibility
If your website has a Content Security Policy (CSP) which doesn't allow style-src 'unsafe-inline', then you won't be able to use inline style attributes to set progress bar widths as shown in our examples below. Alternative methods for setting the widths that are compatible with strict CSPs include using a little custom JavaScript (that sets element.style.width) or using custom CSS classes.
Basic example
Default progress bar.
60% Complete
With label
Remove the <span> with .sr-only class from within the progress bar to show a visible percentage.
60%
To ensure that the label text remains legible even for low percentages, consider adding a min-width to the progress bar.
0%
2%
Contextual alternatives
Progress bars use some of the same button and alert classes for consistent styles.
40% Complete (success)
70% Complete (important)
20% Complete (information)
60% Complete (warning)
Striped
Uses a gradient to create a striped effect. Not available in IE9 and below.
40% Complete (success)
70% Complete (important)
20% Complete (information)
60% Complete (warning)
Animated
Add .active to .progress-bar-striped to animate the stripes right to left. Not available in IE9 and below.
45% Complete
Stacked
Place multiple bars into the same .progress to stack them.
35% Complete (success)
20% Complete (warning)
10% Complete (danger)
Responsive embed
Allow browsers to determine video or slideshow dimensions based on the width of their containing block by creating an intrinsic ratio that will properly scale on any device.
Rules are directly applied to <iframe>, <embed>, <video>, and <object> elements; optionally use an explicit descendant class .embed-responsive-item when you want to match the styling for other attributes.
Pro-Tip! You don't need to include frameborder="0" in your <iframe>s as we override that for you.
Social Share Icons
Alignment
Add any of the alignment helper classes to the <div> container with the .social class to align the area to center (.text-left) or right(.text-right). Left alignment is the default; therefore, no additional class is needed.
Left Aligned - Default
Share this page
Centered
Share this page
Right Aligned
Share this page
Style Variations
Default - Stacked
Share this page
Default - Inline
Share this page
Dark - Stacked
Share this page
Dark - Inline
Share this page
Light - Stacked
Share this page
Light - Inline
Share this page
In Background Color - Stacked
Share this page
In Background Color - Inline
Share this page
Tags
Tag your categories with a bit of style.
The following examples provide a way to style tags for use in displaying keywords or terms within search filters and other related uses. Interaction functionality must be developed separately.
Usage notes
The styles tag, tag-active, tag-not-active, and tag-close-btn may be used on either <a> or <div> tags.
The examples shown below use the following additional tag color classes based upon our site's color classes.
tag-border-b1
tag-border-b2
tag-border-b3
tag-border-b4
tag-border-b5
tag-border-b6
tag-border-b7
tag-border-b8
tag-border-b9
tag-border-b10
tag-border-n1
tag-border-n2
tag-border-n3
tag-border-n4
tag-border-n5
tag-border-n6
tag-border-black
tag-border-white
Thumbnails
Extend Bootstrap's grid system with the thumbnail component to easily display grids of images, videos, text, and more.
If you're looking for Pinterest-like presentation of thumbnails of varying heights and/or widths, you'll need to use a third-party plugin such as Masonry, Isotope, or Salvattore.
Default example
By default, Bootstrap's thumbnails are designed to showcase linked images with minimal required markup.
Custom content
With a bit of extra markup, it's possible to add any kind of HTML content like headings, paragraphs, or buttons into thumbnails.
Thumbnail label
Cras justo odio, dapibus ac facilisis in, egestas eget quam. Donec id elit non mi porta gravida at eget metus. Nullam id dolor id nibh ultricies vehicula ut id elit.
Instead of using a <div> for the thumbnail wrapper element, instead use an <a> tag with the class of thumbnail. Then add a <p> tag with a class of call-to-action to meet usability requirements.
Thumbnail component with text only
Apply a class of thumbnail-text to the thumbnail outer <div> and wrap the thumbnail content with a <div> and color class of .bg-** to style a text-only thumbnail properly.
Horizontal Thumbnails
For horizontally placed thumbnails with custom content use the grid system to properly place image and text for all screen sizes. The <img> will need a class of img-responsive applied to it for proper sizing.
Thumbnail label
Cras justo odio, dapibus ac facilisis in, egestas eget quam. Donec id elit non mi porta gravida at eget metus. Nullam id dolor id nibh ultricies vehicula ut id elit.