- Overview
- Quick start
- Compatibility
- Requirements
- Bugs and feature requests
- Documentation
- Compiling CSS and JavaScript
- Contributing
- Versioning
- Authors
- Copyright and license
- Acknowledgements
This is a Google-styled theme for Bootstrap. Because I'm a fan of the new Google UI seen in Gmail, Docs, Calendar, etc, I decided to reproduce the look of these new UI elements for my own personal use.
TODC Bootstrap was created by Tim O'Donnell, and maintained with the support and involvement of the community.
Three quick start options are available:
- Download the latest release.
- Clone the repo:
git clone https://github.com/todc/todc-bootstrap.git. - Install with Bower:
bower install todc-bootstrap.
Read the Getting Started page for information on the framework contents, templates and examples, and more.
This is being tested in the latest versions of Chrome, Firefox, and IE8+.
The following projects are specifically designed for use with todc-bootstrap:
- todc-select2 - Google-themed select menus
- todc-datepicker - Google-themed datepicker component
- LESS - for compiling
.lessfiles into CSS - Bootstrap - this will be automatically checked out, if necessary, during the build process
Have a bug or a feature request? Please first read the issue guidelines and search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue.
TODC Bootstrap's documentation, included in this repo in the root directory, is built with Jekyll and publicly hosted on GitHub Pages at http://todc.github.io/todc-bootstrap/. The docs may also be run locally.
- If necessary, install Jekyll (requires v1.x).
- Windows users: Read this unofficial guide to get Jekyll up and running without problems. We use Pygments for syntax highlighting, so make sure to read the sections on installing Python and Pygments.
- From the root
/todc-bootstrapdirectory, runjekyll servein the command line.
- Windows users: While we use Jekyll's
encodingsetting, you might still need to change the command prompt's character encoding (code page) to UTF-8 so Jekyll runs without errors. For Ruby 2.0.0, runchcp 65001first. For Ruby 1.9.3, you can alternatively doSET LANG=en_EN.UTF-8.
- Open http://localhost:9002 in your browser, and voilà.
Learn more about using Jekyll by reading its documentation.
Documentation for v2.3.2 has been made available for the time being at http://todc.github.io/todc-bootstrap/2.3.2/ while folks transition to TODC Bootstrap 3.
Previous releases and their documentation are also available for download.
Bootstrap uses Grunt with convenient methods for working with the framework. It's how we compile our code, run tests, and more. To use it, install the required dependencies as directed and then run some Grunt commands.
From the command line:
- Install
grunt-cliglobally withnpm install -g grunt-cli. - Navigate to the root
/todc-bootstrapdirectory, then runnpm install. npm will look at package.json and automatically install the necessary local dependencies listed there.
When completed, you'll be able to run the various Grunt commands provided from the command line.
Unfamiliar with npm? Don't have node installed? That's a-okay. npm stands for node packaged modules and is a way to manage development dependencies through node.js. Download and install node.js before proceeding.
grunt checkout-bootstrap - clones Bootstrap and checks out the version specified by the bootstrapVersion variable in Gruntfile.js.
Run grunt to run tests locally and compile the CSS and JavaScript into /dist. Uses Less and UglifyJS.
grunt dist creates the /dist directory with compiled files. Uses Less and UglifyJS.
Run grunt compress - compresses/zips the contents of the /dist folder to todc-bootstrap-x.x.x-dist.zip in the /dist folder.
This is a convenience method for watching just Less files and automatically building them whenever you save.
Should you encounter problems with installing dependencies or running Grunt commands, uninstall all previous dependency versions (global and local). Then, rerun npm install.
Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development.
Moreover, 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.org.
TODC Bootstrap will be maintained under the Semantic Versioning guidelines as much as possible.
Releases will be numbered with the following format:
<major>.<minor>.<patch>-<major>.<minor>.<patch>
The first set of <major>.<minor>.<patch> is the Bootstrap version while the second set is the todc-bootstrap version.
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
For more information on SemVer, please visit http://semver.org/.
Tim O'Donnell
Copyright 2011-2014 Tim O'Donnell. Code released under the MIT license. Docs released under Creative Commons.
NOTE This project was previously and incorrectly licensed under the Public Domain. It has now been changed to be compatible with Bootstrap's current license.
Inspired by Bootstrap and, of course, Google.