Twitter Bootstrap 2.0 Markup for Rails
This gem focuses on making it easier to use Twitter's Bootstrap 2.0. It's a collection of helpers which should make it faster to use all the components provided by Twitter Bootstrap.
Add to your
gem 'twitter-bootstrap-markup-rails', '0.2.0'
- Alert messages
- Inline labels
Documentation is available on RubyDoc.
Render Alert in your view:
bootstrap_alert_tag("Hello!") # => '<div class="alert"><a class="close">×</a>Hello!</div>'
Render Info Block Alert in your view:
bootstrap_alert_info_block_tag("Hello!") # => '<div class="alert alert-block alert-info"><a class="close">×</a>Hello!</div>'
Same with basic helper:
bootstrap_alert_tag("Hello!", :block => true, :type => "info") # => '<div class="alert alert-block alert-info"><a class="close">×</a>Hello!</div>'
Add Alert heading:
bootstrap_alert_tag("Hello!", :heading => "Hola!") # => '<div class="alert"><a class="close">×</a><strong>Hola!</strong>Hello!</div>'
Notice Inline Label:
bootstrap_inline_label_notice_tag("Info") # => '<span class="label notice">Info</span>'
If you are using
simple-navigation gem you can use the navigation renderer like this:
render_navigation(level: 1..2, renderer: :bootstrap_topbar_list, expand_all: true)
In the spirit of free software, everyone is encouraged to help improve this project.
Here are some ways you can contribute:
- by using alpha, beta, and prerelease versions
- by reporting bugs
- by suggesting new features
- by writing or editing documentation
- by writing specifications
- by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
- by refactoring code
- by closing issues
- by reviewing patches
Submitting an Issue
We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate support for an existing issue by voting it up. When submitting a bug report, please include a gist that includes a stack trace and any details that may be necessary to reproduce the bug, including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with failing specs.
Submitting a Pull Request
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix.
- Add documentation for your feature or bug fix.
bundle exec rake yard. If your changes are not 100% documented, go back to step 4.
- Add specs for your feature or bug fix.
bundle exec rake spec. If your changes are not 100% covered, go back to step 6.
- Commit and push your changes.
- Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)
Supported Ruby Versions
This library aims to support and is tested against the following Ruby implementations:
- Ruby 1.8.7
- Ruby 1.9.2
- Ruby 1.9.3