mirror of
https://github.com/twbs/bootstrap.git
synced 2024-11-30 12:24:19 +01:00
129 lines
6.4 KiB
Markdown
129 lines
6.4 KiB
Markdown
---
|
|
layout: docs
|
|
title: Introduction
|
|
description: Get started with Bootstrap, the world's most popular framework for building responsive, mobile-first sites, with BootstrapCDN and a template starter page.
|
|
group: getting-started
|
|
aliases:
|
|
- "/docs/4.3/getting-started/"
|
|
- "/docs/getting-started/"
|
|
- "/getting-started/"
|
|
toc: true
|
|
---
|
|
|
|
## Quick start
|
|
|
|
Looking to quickly add Bootstrap to your project? Use BootstrapCDN, provided for free by the folks at StackPath. Using a package manager or need to download the source files? [Head to the downloads page](/docs/{{< param docs_version >}}/getting-started/download/).
|
|
|
|
### CSS
|
|
|
|
Copy-paste the stylesheet `<link>` into your `<head>` before all other stylesheets to load our CSS.
|
|
|
|
{{< highlight html >}}
|
|
<link rel="stylesheet" href="{{< param "cdn.css" >}}" integrity="{{< param "cdn.css_hash" >}}" crossorigin="anonymous">
|
|
{{< /highlight >}}
|
|
|
|
### JS
|
|
|
|
Many of our components require the use of JavaScript to function. Specifically, they require our own JavaScript plugins and [Popper.js](https://popper.js.org/). Place the following `<script>`s near the end of your pages, right before the closing `</body>` tag, to enable them. Popper.js must come first, and then our JavaScript plugins.
|
|
|
|
{{< highlight html >}}
|
|
<script src="{{< param "cdn.popper" >}}" integrity="{{< param "cdn.popper_hash" >}}" crossorigin="anonymous"></script>
|
|
<script src="{{< param "cdn.js" >}}" integrity="{{< param "cdn.js_hash" >}}" crossorigin="anonymous"></script>
|
|
{{< /highlight >}}
|
|
|
|
If you use `<script type="module">`, please refer to our [using Bootstrap as a module](/docs/{{< param docs_version >}}/getting-started/javascript/#using-bootstrap-as-a-module) section.
|
|
|
|
Curious which components explicitly require our JavaScript and Popper.js? Click the show components link below. If you're at all unsure about the general page structure, keep reading for an example page template.
|
|
|
|
Our `bootstrap.bundle.js` and `bootstrap.bundle.min.js` include [Popper](https://popper.js.org/). For more information about what's included in Bootstrap, please see our [contents](/docs/{{< param docs_version >}}/getting-started/contents/#precompiled-bootstrap) section.
|
|
|
|
{{< partial "getting-started/components-requiring-javascript" >}}
|
|
|
|
## Starter template
|
|
|
|
Be sure to have your pages set up with the latest design and development standards. That means using an HTML5 doctype and including a viewport meta tag for proper responsive behaviors. Put it all together and your pages should look like this:
|
|
|
|
{{< highlight html >}}
|
|
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<!-- Required meta tags -->
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
|
|
<!-- Bootstrap CSS -->
|
|
<link rel="stylesheet" href="{{< param "cdn.css" >}}" integrity="{{< param "cdn.css_hash" >}}" crossorigin="anonymous">
|
|
|
|
<title>Hello, world!</title>
|
|
</head>
|
|
<body>
|
|
<h1>Hello, world!</h1>
|
|
|
|
<!-- Optional JavaScript -->
|
|
<!-- Popper.js first, then Bootstrap JS -->
|
|
<script src="{{< param "cdn.popper" >}}" integrity="{{< param "cdn.popper_hash" >}}" crossorigin="anonymous"></script>
|
|
<script src="{{< param "cdn.js" >}}" integrity="{{< param "cdn.js_hash" >}}" crossorigin="anonymous"></script>
|
|
</body>
|
|
</html>
|
|
{{< /highlight >}}
|
|
|
|
That's all you need for overall page requirements. Visit the [Layout docs](/docs/{{< param docs_version >}}/layout/overview/) or [our official examples](/docs/{{< param docs_version >}}/examples/) to start laying out your site's content and components.
|
|
|
|
## Important globals
|
|
|
|
Bootstrap employs a handful of important global styles and settings that you'll need to be aware of when using it, all of which are almost exclusively geared towards the *normalization* of cross browser styles. Let's dive in.
|
|
|
|
### HTML5 doctype
|
|
|
|
Bootstrap requires the use of the HTML5 doctype. Without it, you'll see some funky incomplete styling, but including it shouldn't cause any considerable hiccups.
|
|
|
|
{{< highlight html >}}
|
|
<!doctype html>
|
|
<html lang="en">
|
|
...
|
|
</html>
|
|
{{< /highlight >}}
|
|
|
|
### Responsive meta tag
|
|
|
|
Bootstrap is developed *mobile first*, a strategy in which we optimize code for mobile devices first and then scale up components as necessary using CSS media queries. To ensure proper rendering and touch zooming for all devices, **add the responsive viewport meta tag** to your `<head>`.
|
|
|
|
{{< highlight html >}}
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
{{< /highlight >}}
|
|
|
|
You can see an example of this in action in the [starter template](#starter-template).
|
|
|
|
### Box-sizing
|
|
|
|
For more straightforward sizing in CSS, we switch the global `box-sizing` value from `content-box` to `border-box`. This ensures `padding` does not affect the final computed width of an element, but it can cause problems with some third party software like Google Maps and Google Custom Search Engine.
|
|
|
|
On the rare occasion you need to override it, use something like the following:
|
|
|
|
{{< highlight css >}}
|
|
.selector-for-some-widget {
|
|
box-sizing: content-box;
|
|
}
|
|
{{< /highlight >}}
|
|
|
|
With the above snippet, nested elements—including generated content via `::before` and `::after`—will all inherit the specified `box-sizing` for that `.selector-for-some-widget`.
|
|
|
|
Learn more about [box model and sizing at CSS Tricks](https://css-tricks.com/box-sizing/).
|
|
|
|
### Reboot
|
|
|
|
For improved cross-browser rendering, we use [Reboot](/docs/{{< param docs_version >}}/content/reboot/) to correct inconsistencies across browsers and devices while providing slightly more opinionated resets to common HTML elements.
|
|
|
|
## Community
|
|
|
|
Stay up to date on the development of Bootstrap and reach out to the community with these helpful resources.
|
|
|
|
- Follow [@getbootstrap on Twitter](https://twitter.com/{{< param twitter >}}).
|
|
- Read and subscribe to [The Official Bootstrap Blog]({{< param blog >}}/).
|
|
- Join [the official Slack room]({{< param slack >}}/).
|
|
- Chat with fellow Bootstrappers in IRC. On the `irc.freenode.net` server, in the `##bootstrap` channel.
|
|
- Implementation help may be found at Stack Overflow (tagged [`bootstrap-4`](https://stackoverflow.com/questions/tagged/bootstrap-4)).
|
|
- Developers should use the keyword `bootstrap` on packages which modify or add to the functionality of Bootstrap when distributing through [npm](https://www.npmjs.com/search?q=keywords:bootstrap) or similar delivery mechanisms for maximum discoverability.
|
|
|
|
You can also follow [@getbootstrap on Twitter](https://twitter.com/{{< param twitter >}}) for the latest gossip and awesome music videos.
|