Bootstrap is a sleek, intuitive, and powerful front-end framework for faster and easier web development, created and maintained by Mark Otto and Jacob Thornton.
To get started, check out http://getbootstrap.com!
Three quick start options are available:
- Download the latest release.
- Clone the repo:
git clone git://github.com/twitter/bootstrap.git. - Install with Bower:
bower install bootstrap.
Read the Getting Started page for information on the framework contents, templates and examples, and more.
Have a bug or a feature request? Please open a new issue. Before opening any issue, please search for existing issues and read the Issue Guidelines, written by Nicolas Gallagher.
Bootstrap's documentation, included in this repo in the /docs directory, is built with Jekyll and publicly hosted on GitHub Pages at http://getbootstrap.com. The docs maybe also be run locally.
- If necessary, install Jekyll.
- From the
/bootstrapdirectory, runjekyll servein the command line. - Open http://getbootstrap.dev:9001 in your browser, and voilà.
Learn more about using Jekyll by reading their documentation.
Documentation for v2.3.2 has been made available for the time being at http://getbootstrap.com/2.3.2/docs while folks transition to Bootstrap 3.
For previous releases, documentation is available for download via Git tags.
Bootstrap includes a makefile with convenient methods for working with the framework. Before getting started, install the necessary local dependencies:
$ npm install
When completed, you'll be able to run the various make commands provided.
make runs the Recess compiler to rebuild the /less files and compile the docs. Requires recess and uglify-js.
make bootstrap creates the /bootstrap directory with compiled files. Requires recess and uglify-js.
Runs jshint and qunit tests headlessly in phantomjs (used for ci). Requires phantomjs.
This is a convenience method for watching just Less files and automatically building them whenever you save. Requires the watchr gem.
Should you encounter problems with installing dependencies or running makefile commands, uninstall all previous dependency versions (global and local). Then, rerun npm install.
Please read through our guidelines for contributing to Bootstrap. Included are directions for opening issues, coding standards, and notes on development.
More over, if your pull request contains JavaScript patches or features, you must include relevant unit tests. All HTML and CSS should conform to the Code Guide, maintained by Mark Otto.
Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at http://editorconfig.com.
Keep track of development and community news.
- Follow @twbootstrap on Twitter.
- Read and subscribe to the The Official Twitter Bootstrap Blog.
- Have a question that's not a feature request or bug report? Ask on the mailing list.
- Chat with fellow Bootstrappers in IRC. On the
irc.freenode.netserver, in the##twitter-bootstrapchannel.
For transparency and insight into our release cycle, and for striving to maintain backward compatibility, Bootstrap will be maintained under the Semantic Versioning guidelines as much as possible.
Releases will be numbered with the following format:
<major>.<minor>.<patch>
And constructed with the following guidelines:
- Breaking backward compatibility bumps the major (and resets the minor and patch)
- New additions without breaking backward compatibility bumps the minor (and resets the patch)
- Bug fixes and misc changes bumps the patch
For more information on SemVer, please visit http://semver.org/.
Mark Otto
Jacob Thornton
Copyright 2012 Twitter, Inc under the Apache 2.0 license.