Bootstrap is a toolkit from Twitter designed to kickstart development of web apps and sites. It includes base CSS and HTML for typography, forms, buttons, tables, grids, navigation, and more.
twitter-bootstrap-rails project integrates Bootstrap CSS toolkit for Rails Asset Pipeline (Rails 6, Rails 5 and Rails 3.x versions are supported)
Screencasts provided by RailsCasts (Ryan Bates)
Twitter Bootstrap Basics in this episode you will learn how to include Bootstrap into Rails application with the twitter-bootstrap-rails gem.
More on Twitter Bootstrap in this episode continues on the Bootstrap project showing how to display flash messages, add form validations with SimpleForm, customise layout with variables, and switch to using Sass. (Note: This episode is pro episode)
The Twitter Bootstrap Rails gem can provide the Bootstrap stylesheets in two ways.
The plain CSS way is how Bootstrap is provided on the official website.
The Less way provides more customisation options, like changing theme colors and provides useful Less mixins for your code, but requires the Less gem and the Ruby Racer Javascript runtime (not available on Microsoft Windows).
To use Less stylesheets, you'll need the less-rails gem, and one of JavaScript runtimes supported by CommonJS.
Include these lines in the Gemfile to install the gems from RubyGems.org:
gem "therubyracer"
gem "less-rails" #Sprockets (what Rails 3.1 uses for its asset pipeline) supports LESS
gem "twitter-bootstrap-rails"
or you can install from latest build;
gem 'twitter-bootstrap-rails', :git => 'git://github.com/seyhunak/twitter-bootstrap-rails.git'
Then run bundle install from the command line:
bundle install
Then run the bootstrap generator to add Bootstrap includes into your assets:
rails generate bootstrap:install less
If you need to skip coffeescript replacement into app generators, use:
rails generate bootstrap:install --no-coffeescript
If you don't need to customize the stylesheets using Less, the only gem you need is the twitter-bootstrap-rails gem:
gem "twitter-bootstrap-rails"
After running bundle install, run the generator:
rails generate bootstrap:install static
If your Rails server is running, make sure to restart it.
You can run following generators to get started with Bootstrap quickly.
Layout (generates Bootstrap compatible layout) - (Haml and Slim supported)
Usage:
rails g bootstrap:layout [LAYOUT_NAME]
Themed (generates Bootstrap compatible scaffold views.) - (Haml and Slim supported)
Usage:
rails g bootstrap:themed [RESOURCE_NAME]
Example:
rails g scaffold Post title:string description:text
rake db:migrate
rails g bootstrap:themed Posts
Notice the plural usage of the resource to generate bootstrap:themed.
Bootstrap was built with Preboot, an open-source pack of mixins and variables to be used in conjunction with Less, a CSS preprocessor for faster and easier web development.
You have to require Bootstrap LESS (bootstrap_and_overrides.css.less) in your application.css
/*
*= require bootstrap_and_overrides
*/
/* Your stylesheets goes here... */
To use individual components from bootstrap, your bootstrap_and_overrides.less could look like this:
// Core variables and mixins
@import "twitter/bootstrap/variables.less";
@import "twitter/bootstrap/mixins.less";
// Reset and dependencies
@import "twitter/bootstrap/normalize.less";
@import "twitter/bootstrap/print.less";
//@import "twitter/bootstrap/glyphicons.less"; // Excludes glyphicons
// Core CSS
@import "twitter/bootstrap/scaffolding.less";
@import "twitter/bootstrap/type.less";
@import "twitter/bootstrap/code.less";
@import "twitter/bootstrap/grid.less";
@import "twitter/bootstrap/tables.less";
@import "twitter/bootstrap/forms.less";
@import "twitter/bootstrap/buttons.less";
// Components
@import "twitter/bootstrap/component-animations.less";
@import "twitter/bootstrap/dropdowns.less";
@import "twitter/bootstrap/button-groups.less";
@import "twitter/bootstrap/input-groups.less";
@import "twitter/bootstrap/navs.less";
@import "twitter/bootstrap/navbar.less";
@import "twitter/bootstrap/breadcrumbs.less";
@import "twitter/bootstrap/pagination.less";
@import "twitter/bootstrap/pager.less";
@import "twitter/bootstrap/labels.less";
@import "twitter/bootstrap/badges.less";
@import "twitter/bootstrap/jumbotron.less";
@import "twitter/bootstrap/thumbnails.less";
@import "twitter/bootstrap/alerts.less";
@import "twitter/bootstrap/progress-bars.less";
@import "twitter/bootstrap/media.less";
@import "twitter/bootstrap/list-group.less";
@import "twitter/bootstrap/panels.less";
@import "twitter/bootstrap/responsive-embed.less";
@import "twitter/bootstrap/wells.less";
@import "twitter/bootstrap/close.less";
// Components w/ JavaScript
@import "twitter/bootstrap/modals.less";
@import "twitter/bootstrap/tooltip.less";
@import "twitter/bootstrap/popovers.less";
@import "twitter/bootstrap/carousel.less";
// Utility classes
@import "twitter/bootstrap/utilities.less";
@import "twitter/bootstrap/responsive-utilities.less";
If you'd like to alter Bootstrap's own variables, or define your LESS styles inheriting Bootstrap's mixins, you can do so inside bootstrap_and_overrides.css.less:
@link-color: #ff0000;
If you are using SASS to compile your application.css (e.g. your manifest file is application.css.sass or application.css.scss) you may get this:
Invalid CSS after "*": expected "{", was "= require twitt..."
(in app/assets/stylesheets/application.css)
(sass)
If this is the case, you must use @import instead of *= in your manifest file, or don't compile your manifest with SASS.
By default, this gem (when using less generator) won't enable standard Bootstraps's Glyphicons.
If you would like to restore the default Glyphicons, inside the generated bootstrap_and_overrides.css.less uncomment these lines:
// Glyphicons are not required by default, uncomment the following lines to enable them.
@glyphiconsEotPath: font-url("glyphicons-halflings-regular.eot");
@glyphiconsEotPath_iefix: font-url("glyphicons-halflings-regular.eot?#iefix");
@glyphiconsWoffPath: font-url("glyphicons-halflings-regular.woff");
@glyphiconsTtfPath: font-url("glyphicons-halflings-regular.ttf");
@glyphiconsSvgPath: font-url("glyphicons-halflings-regular.svg#glyphicons_halflingsregular");
@import "twitter/bootstrap/glyphicons.less";
This gem was used to bundle the excellent Font-Awesome library. However that was another maintenance effort that is not worth to do here.
For Rails projects that need it there is the font-awesome-rails gem that provides same functionality that this gems was used to provide and it also have some other interesting features (e.g. view helpers).
Require Bootstrap JS (bootstrap.js) in your application.js
//= require twitter/bootstrap
$(function(){
/* Your JavaScript goes here... */
});
If you want to customize what is loaded, your application.js would look something like this
#= require jquery
#= require jquery_ujs
#= require twitter/bootstrap/transition
#= require twitter/bootstrap/alert
#= require twitter/bootstrap/modal
#= require twitter/bootstrap/button
#= require twitter/bootstrap/collapse
...and so on for each bootstrap js component.
Using Bootstrap with the CoffeeScript is easy. twitter-bootstrap-rails generates a "bootstrap.js.coffee" file for you to /app/assets/javascripts/ folder.
jQuery ->
$("a[rel~=popover], .has-popover").popover()
$("a[rel~=tooltip], .has-tooltip").tooltip()
You can create modals easily using the following example. The header, body, and footer all accept content_tag or plain html. The href of the button to launch the modal must match the id of the modal dialog. It also accepts a block for the header, body, and footer. If you are getting a complaint about the modal_helper unable to merge a hash it is due to this.
<%= content_tag :a, "Modal", href: "#modal", class: 'btn', data: {toggle: 'modal'} %>
<%= modal_dialog id: "modal",
header: { show_close: true, dismiss: 'modal', title: 'Modal header' },
body: { content: 'This is the body' },
footer: { content: content_tag(:button, 'Save', class: 'btn') } %>
It should let you write things like:
<%= nav_bar fixed: :top, brand: "Fashionable Clicheizr 2.0", responsive: true do %>
<%= menu_group do %>
<%= menu_item "Home", root_path %>
<%= menu_divider %>
<%= drop_down "Products" do %>
<%= menu_item "Things you can't afford", expensive_products_path %>
<%= menu_item "Things that won't suit you anyway", harem_pants_path %>
<%= menu_item "Things you're not even cool enough to buy anyway", hipster_products_path %>
<% if current_user.lives_in_hackney? %>
<%= menu_item "Bikes", fixed_wheel_bikes_path %>
<% end %>
<% end %>
<%= menu_item "About Us", about_us_path %>
<%= menu_item "Contact", contact_path %>
<% end %>
<%= menu_group pull: :right do %>
<% if current_user %>
<%= menu_item "Log Out", log_out_path %>
<% else %>
<%= form_for @user, url: session_path(:user), html => {class: "navbar-form pull-right"} do |f| -%>
<p><%= f.text_field :email %></p>
<p><%= f.password_field :password %></p>
<p><%= f.submit "Sign in" %></p>
<% end -%>
<% end %>
<% end %>
<% end %>
In your view file (most likely application.html.erb) to get a basic navbar set up you need to do this:
<%= nav_bar %>
Which will render:
<div class="navbar">
<div class="container">
</div>
</div>
If you want the navbar to stick to the top of the screen, pass in the option like this:
<%= nav_bar fixed: :top %>
To render:
<div class="navbar navbar-fixed-top">
<div class="container">
</div>
</div>
If you want a full-width navbar that scrolls away with the page, pass in the option like this:
<%= nav_bar static: :top %>
To render:
<div class="navbar navbar-static-top">
<div class="container">
</div>
</div>
Add the name of your site on the left hand edge of the navbar. By default, it will link to root_url. Passing a brand_link option will set the url to whatever you want.
<%= nav_bar brand: "We're sooo web 2.0alizr", brand_link: account_dashboard_path %>
Which will render:
<div class="navbar">
<div class="container">
<a class="navbar-brand" href="/accounts/dashboard">
We're sooo web 2.0alizr
</a>
</div>
</div>
If you want the responsive version of the navbar to work (One that shrinks down on mobile devices etc.), you need to pass this option:
<%= nav_bar responsive: true %>
Which renders the html quite differently:
<div class="navbar">
<div class="container">
<!-- .navbar-toggle is used as the toggle for collapsed navbar content -->
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<!-- Everything in here gets hidden at 940px or less -->
<div class="navbar-collapse collapse">
<!-- menu items gets rendered here instead -->
</div>
</div>
</div>
This is the 'meat' of the code where you define your menu items.
You can group menu items in theoretical boxes which you can apply logic to - e.g. show different collections for logged in users/logged out users, or simply right align a group.
The active menu item will be inferred from the link for now.
The important methods here are menu_group and menu_item.
menu_group only takes one argument - :pull - this moves the group left or right when passed :left or :right.
menu_item generates a link wrapped in an li tag. It takes two arguments and an options hash. The first argument is the name (the text that will appear in the menu), and the path (which defaults to "#" if left blank). The rest of the options are passed straight through to the link_to helper, so that you can add classes, ids, methods or data tags etc.
<%= nav_bar fixed: :top, brand: "Ninety Ten" do %>
<%= menu_group do %>
<%= menu_item "Home", root_path %>
<%= menu_item "About Us", about_us_path %>
<%= menu_item "Contact", contact_path %>
<% end %>
<% if current_user %>
<%= menu_item "Log Out", log_out_path %>
<% else %>
<%= menu_group pull: :right do %>
<%= menu_item "Sign Up", registration_path %>
<%= form_for @user, url: session_path(:user) do |f| -%>
<p><%= f.text_field :email %></p>
<p><%= f.password_field :password %></p>
<p><%= f.submit "Sign in" %></p>
<% end -%>
<% end %>
<% end %>
<% end %>
For multi-level list options, where it makes logical sense to group menu items, or simply to save space if you have a lot of pages, you can group menu items into drop down lists like this:
<%= nav_bar do %>
<%= menu_item "Home", root_path %>
<%= drop_down "Products" do %>
<%= menu_item "Latest", latest_products_path %>
<%= menu_item "Top Sellers", popular_products_path %>
<%= drop_down_divider %>
<%= menu_item "Discount Items", discounted_products_path %>
<% end %>
<%= menu_item "About Us", about_us_path %>
<%= menu_item "Contact", contact_path %>
<% end %>
Dividers are just vertical bars that visually separate logically disparate groups of menu items
<%= nav_bar fixed: :bottom do %>
<%= menu_item "Home", root_path %>
<%= menu_item "About Us", about_us_path %>
<%= menu_item "Contact", contact_path %>
<%= menu_divider %>
<%= menu_item "Edit Profile", edit_user_path(current_user) %>
<%= menu_item "Account Settings", edit_user_account_path(current_user, @account) %>
<%= menu_item "Log Out", log_out_path %>
<% end %>
At the moment - this is just a how to...
You need to add this class to the form itself (Different form builders do this in different ways - please check out the relevant docs)
.navbar-form
To pull the form left or right, add either of these classes:
.pull-left
.pull-right
If you want the Bootstrap search box (I think it just rounds the corners), use:
.navbar-search
Instead of:
.navbar-form
To change the size of the form fields, use .span2 (or however many span widths you want) to the input itself.
You can shift things to the left or the right across the nav bar. It's easiest to do this on grouped menu items:
<%= nav_bar fixed: :bottom do %>
<% menu_group do %>
<%= menu_item "Home", root_path %>
<%= menu_item "About Us", about_us_path %>
<%= menu_item "Contact", contact_path %>
<% end %>
<% menu_group pull: :right do %>
<%= menu_item "Edit Profile", edit_user_path(current_user) %>
<%= menu_item "Account Settings", edit_user_account_path(current_user, @account) %>
<%= menu_item "Log Out", log_out_path %>
<% end %>
<% end %>
If you want to put regular plain text in the navbar anywhere, you do it like this:
<%= nav_bar brand: "Apple" do %>
<%= menu_text "We make shiny things" %>
<%= menu_item "Home", root_path %>
<%= menu_item "About Us", about_us_path %>
<% end %>
It also takes the :pull option to drag it to the left or right.
Add flash helper <%= bootstrap_flash %> to your layout (built-in with layout generator).
You can pass the attributes you want to add to the main div returned: <%= bootstrap_flash(class: "extra-class", id: "your-id") %>
Notice If your application is using breadcrumbs-on-rails you will have a namespace collision with the add_breadcrumb method. For this reason if breadcrumbs-on-rails is detected in Gemfile gem methods will be accessible using boostrap prefix, i.e. render_bootstrap_breadcrumbs and add_bootstrap_breadcrumb
Usually you do not need to use these breadcrumb gems since this gem provides the same functionality out of the box without the additional dependency.
However if there are some breadcrumbs-on-rails features you need to keep you can still use them and use this gem with the prefixes explained above.
Add breadcrumbs helper <%= render_breadcrumbs %> to your layout.
You can also specify a divider for it like this: <%= render_breadcrumbs('>') %> (default divider is /).
If you do not need dividers at all you can use nil: <%= render_breadcrumbs(nil) %>.
Full example:
render_breadcrumbs(" / ", { class: '', item_class: '', divider_class: '', active_class: 'active' })
class ApplicationController
add_breadcrumb :root # 'root_path' will be used as url
end
class ExamplesController < ApplicationController
add_breadcrumb :index, :examples_path
def edit
@example = Example.find params[:id]
add_breadcrumb @example # @example.to_s as name, example_path(@example) as url
add_breadcrumb :edit, edit_example_path(@example)
end
end
All symbolic names translated with I18n. See I18n Internationalization Support section.
Badge:
<%= badge(12, :warning) %> <span class="badge badge-warning">12</span>
Label:
<%= tag_label('Gut!', :success) %> <span class="label label-success">Gut!</span>
Glyph:
<%= glyph(:pencil) %> <i class="icon-pencil"></i>
<%= glyph(:pencil, {tag: :span}) %> <span class="icon-pencil"></span>
<%= glyph(:pencil, {class: 'foo'}) %> <i class="icon-pencil foo"></i>
The installer creates an English translation file for you and copies it to config/locales/en.bootstrap.yml
NOTE: If you are using Devise in your project, you must have a devise locale file for handling flash messages, even if those messages are blank. See https://github.com/plataformatec/devise/wiki/I18n
Please see CHANGELOG.md for more details
Please see CONTRIBUTERS.md for contributors list
Senior Software Developer Istanbul / Turkey seyhunak [at] gmail com
Bootstrap and all twitter-bootstrap-rails contributors http://twbs.github.io/bootstrap
Support us with a monthly donation and help us continue our activities. [Become a backer]
Become a sponsor and get your logo on our README on Github with a link to your site. [Become a sponsor]
Copyright (c) 2017 (since 2012) by Seyhun Akyürek
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
