At Shore we create our own builds of Bootstrap. We do this for several reasons:
- maintain our custom Shore theme
- select only the features we need
- add custom element styles
- distribute as npm private module, so that we can easily use it in multiple projects to ensure a consistent brand experience
Visit the Shore Bootstrap Theme Test Page hosted on Shore CDN!
Install via npm with
npm install @email@example.com.N (replace N with latest version)
and use the files from
shore-bootstrap3 branch as a basis. Do not commit your changes to
Install the required npm packages from the project root via:
Simple theme testing
npm run test-server
to open the theme test page and start hacking the less files. The test-server will watch for files changes and autom. reloads the test page.
How to update the Shore Icon Font?
- Go to Fontastic
- Make sure shore-icons is selected (top-left, below Fontastic logo)
- Select new icons
- Go to Publish page
- Click on DOWNLOAD button
- Extract ZIP file and copy folder
shore-iconsto project root folder
npm run -s generate-shore-icons-less
npm run build
Publishing on NPM
This has to be done locally by calling
- bump version to 3.3.5-shore.(n+1)
- git push (with tags)
- publish on npm
Bootstrap is a sleek, intuitive, and powerful front-end framework for faster and easier web development, created by Mark Otto and Jacob Thornton, and maintained by the core team with the massive support and involvement of the community.
To get started, check out http://getbootstrap.com!
Table of contents
- Quick start
- Bugs and feature requests
- Copyright and license
Several quick start options are available:
- Download the latest release.
- Clone the repo:
git clone https://github.com/twbs/bootstrap.git.
- Install with Bower:
bower install bootstrap.
- Install with npm:
npm install bootstrap.
- Install with Meteor:
meteor add twbs:bootstrap.
- Install with Composer:
composer require twbs/bootstrap.
Read the Getting started page for information on the framework contents, templates and examples, and more.
Within the download you'll find the following directories and files, logically grouping common assets and providing both compiled and minified variations. You'll see something like this:
bootstrap/ ├── css/ │ ├── bootstrap.css │ ├── bootstrap.css.map │ ├── bootstrap.min.css │ ├── bootstrap-theme.css │ ├── bootstrap-theme.css.map │ └── bootstrap-theme.min.css ├── js/ │ ├── bootstrap.js │ └── bootstrap.min.js └── fonts/ ├── glyphicons-halflings-regular.eot ├── glyphicons-halflings-regular.svg ├── glyphicons-halflings-regular.ttf ├── glyphicons-halflings-regular.woff └── glyphicons-halflings-regular.woff2
We provide compiled CSS and JS (
bootstrap.*), as well as compiled and minified CSS and JS (
bootstrap.min.*). CSS source maps (
bootstrap.*.map) are available for use with certain browsers' developer tools. Fonts from Glyphicons are included, as is the optional Bootstrap theme.
Bugs and feature requests
Running documentation locally
- If necessary, install Jekyll (requires v2.5.x).
- Windows users: Read this unofficial guide to get Jekyll up and running without problems.
- Install the Ruby-based syntax highlighter, Rouge, with
gem install rouge.
- From the root
jekyll servein the command line.
- Open http://localhost:9001 in your browser, and voilà.
Learn more about using Jekyll by reading its documentation.
Documentation for previous releases
Documentation for v2.3.2 has been made available for the time being at http://getbootstrap.com/2.3.2/ while folks transition to Bootstrap 3.
Previous releases and their documentation are also available for download.
Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development.
Get updates on Bootstrap's development and chat with the project maintainers and community members.
- Follow @getbootstrap on Twitter.
- Read and subscribe to The Official Bootstrap Blog.
- Join the official Slack room.
- Chat with fellow Bootstrappers in IRC. On the
irc.freenode.netserver, in the
- Implementation help may be found at Stack Overflow (tagged
- Developers should use the keyword
bootstrapon packages which modify or add to the functionality of Bootstrap when distributing through npm or similar delivery mechanisms for maximum discoverability.
For transparency into our release cycle and in striving to maintain backward compatibility, Bootstrap is maintained under the Semantic Versioning guidelines. Sometimes we screw up, but we'll adhere to those rules whenever possible.