From f41bf2f7c5640da7a17872cb9f4dc0175246b100 Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Mon, 26 Jul 2021 23:14:24 -0600 Subject: Rename Build Tools page to Contribute (#34578) Co-authored-by: XhmikosR --- .../docs/5.0/examples/starter-template/index.html | 2 +- .../docs/5.0/getting-started/build-tools.md | 102 -------------------- .../content/docs/5.0/getting-started/contribute.md | 103 +++++++++++++++++++++ site/content/docs/5.0/getting-started/download.md | 6 +- site/data/sidebar.yml | 2 +- 5 files changed, 108 insertions(+), 107 deletions(-) delete mode 100644 site/content/docs/5.0/getting-started/build-tools.md create mode 100644 site/content/docs/5.0/getting-started/contribute.md diff --git a/site/content/docs/5.0/examples/starter-template/index.html b/site/content/docs/5.0/examples/starter-template/index.html index 48a5cbfad..3623ff180 100644 --- a/site/content/docs/5.0/examples/starter-template/index.html +++ b/site/content/docs/5.0/examples/starter-template/index.html @@ -40,7 +40,7 @@ extra_css:
  • }}">Bootstrap quick start guide
  • }}">Bootstrap Webpack guide
  • }}">Bootstrap Parcel guide
    • -
  • }}">Contributing to Bootstrap
    • +
  • }}">Contributing to Bootstrap
    • diff --git a/site/content/docs/5.0/getting-started/build-tools.md b/site/content/docs/5.0/getting-started/build-tools.md deleted file mode 100644 index d0286375e..000000000 --- a/site/content/docs/5.0/getting-started/build-tools.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -layout: docs -title: Build tools -description: Learn how to use Bootstrap's included npm scripts to build our documentation, compile source code, run tests, and more. -group: getting-started -toc: true ---- - -## Tooling setup - -Bootstrap uses [npm scripts](https://docs.npmjs.com/misc/scripts/) for its build system. Our [package.json]({{< param repo >}}/blob/v{{< param current_version >}}/package.json) includes convenient methods for working with the framework, including compiling code, running tests, and more. - -To use our build system and run our documentation locally, you'll need a copy of Bootstrap's source files and Node. Follow these steps and you should be ready to rock: - -1. [Download and install Node.js](https://nodejs.org/en/download/), which we use to manage our dependencies. -2. Either [download Bootstrap's sources]({{< param "download.source" >}}) or fork [Bootstrap's repository]({{< param repo >}}). -3. Navigate to the root `/bootstrap` directory and run `npm install` to install our local dependencies listed in [package.json]({{< param repo >}}/blob/v{{< param current_version >}}/package.json). - -When completed, you'll be able to run the various commands provided from the command line. - -## Using npm scripts - -Our [package.json]({{< param repo >}}/blob/v{{< param current_version >}}/package.json) includes numerous tasks for developing the project. Run `npm run` to see all the npm scripts in your terminal. **Primary tasks include:** - - - - - - - - - - - - - - - - - - - - - - - - - - -
    TaskDescription
    - npm start - - Compiles CSS and JavaScript, builds the documentation, and starts a local server. -
    - npm run dist - - Creates the dist/ directory with compiled files. Requires Sass, Autoprefixer, and terser. -
    - npm test - - Runs tests locally after running npm run dist -
    - npm run docs-serve - - Builds and runs the documentation locally. -
    - -{{< callout info >}} -{{< partial "callout-info-npm-starter.md" >}} -{{< /callout >}} - -## Sass - -Bootstrap uses [Dart Sass](https://sass-lang.com/dart-sass) for compiling our Sass source files into CSS files (included in our build process), and we recommend you do the same if you're compiling Sass using your own asset pipeline. We previously used Node Sass for Bootstrap v4, but LibSass and packages built on top of it, including Node Sass, are now [deprecated](https://sass-lang.com/blog/libsass-is-deprecated). - -Dart Sass uses a rounding precision of 10 and for efficiency reasons does not allow adjustment of this value. We don't lower this precision during further processing of our generated CSS, such as during minification, but if you chose to do so we recommend maintaining a precision of at least 6 to prevent issues with browser rounding. - -## Autoprefixer - -Bootstrap uses [Autoprefixer][autoprefixer] (included in our build process) to automatically add vendor prefixes to some CSS properties at build time. Doing so saves us time and code by allowing us to write key parts of our CSS a single time while eliminating the need for vendor mixins like those found in v3. - -We maintain the list of browsers supported through Autoprefixer in a separate file within our GitHub repository. See [.browserslistrc]({{< param repo >}}/blob/v{{< param current_version >}}/.browserslistrc) for details. - -## RTLCSS - -Bootstrap uses [RTLCSS](https://rtlcss.com/) to process compiled CSS and convert them to RTL – basically replacing horizontal direction aware properties (eg. `padding-left`) with their opposite. It allows us only write our CSS a single time and make minor tweaks using RTLCSS [control](https://rtlcss.com/learn/usage-guide/control-directives/) and [value](https://rtlcss.com/learn/usage-guide/value-directives/) directives. - -## Local documentation - -Running our documentation locally requires the use of Hugo, which gets installed via the [hugo-bin](https://www.npmjs.com/package/hugo-bin) npm package. Hugo is a blazingly fast and quite extensible static site generator that provides us: basic includes, Markdown-based files, templates, and more. Here's how to get it started: - -1. Run through the [tooling setup](#tooling-setup) above to install all dependencies. -2. From the root `/bootstrap` directory, run `npm run docs-serve` in the command line. -3. Open `http://localhost:9001/` in your browser, and voilà. - -Learn more about using Hugo by reading its [documentation](https://gohugo.io/documentation/). - -## Troubleshooting - -Should you encounter problems with installing dependencies, uninstall all previous dependency versions (global and local). Then, rerun `npm install`. - -[autoprefixer]: https://github.com/postcss/autoprefixer diff --git a/site/content/docs/5.0/getting-started/contribute.md b/site/content/docs/5.0/getting-started/contribute.md new file mode 100644 index 000000000..407081c22 --- /dev/null +++ b/site/content/docs/5.0/getting-started/contribute.md @@ -0,0 +1,103 @@ +--- +layout: docs +title: Contribute +description: Help develop Bootstrap with our documentation build scripts and tests. +group: getting-started +toc: true +aliases: "/docs/5.0/getting-started/build-tools/" +--- + +## Tooling setup + +Bootstrap uses [npm scripts](https://docs.npmjs.com/misc/scripts/) to build the documentation and compile source files. Our [package.json]({{< param repo >}}/blob/v{{< param current_version >}}/package.json) houses these scripts for compiling code, running tests, and more. These aren't intended for use outside our repository and documentation. + +To use our build system and run our documentation locally, you'll need a copy of Bootstrap's source files and Node. Follow these steps and you should be ready to rock: + +1. [Download and install Node.js](https://nodejs.org/en/download/), which we use to manage our dependencies. +2. Either [download Bootstrap's sources]({{< param "download.source" >}}) or fork [Bootstrap's repository]({{< param repo >}}). +3. Navigate to the root `/bootstrap` directory and run `npm install` to install our local dependencies listed in [package.json]({{< param repo >}}/blob/v{{< param current_version >}}/package.json). + +When completed, you'll be able to run the various commands provided from the command line. + +## Using npm scripts + +Our [package.json]({{< param repo >}}/blob/v{{< param current_version >}}/package.json) includes numerous tasks for developing the project. Run `npm run` to see all the npm scripts in your terminal. **Primary tasks include:** + + + + + + + + + + + + + + + + + + + + + + + + + + +
    TaskDescription
    + npm start + + Compiles CSS and JavaScript, builds the documentation, and starts a local server. +
    + npm run dist + + Creates the dist/ directory with compiled files. Requires Sass, Autoprefixer, and terser. +
    + npm test + + Runs tests locally after running npm run dist +
    + npm run docs-serve + + Builds and runs the documentation locally. +
    + +{{< callout info >}} +{{< partial "callout-info-npm-starter.md" >}} +{{< /callout >}} + +## Sass + +Bootstrap uses [Dart Sass](https://sass-lang.com/dart-sass) for compiling our Sass source files into CSS files (included in our build process), and we recommend you do the same if you're compiling Sass using your own asset pipeline. We previously used Node Sass for Bootstrap v4, but LibSass and packages built on top of it, including Node Sass, are now [deprecated](https://sass-lang.com/blog/libsass-is-deprecated). + +Dart Sass uses a rounding precision of 10 and for efficiency reasons does not allow adjustment of this value. We don't lower this precision during further processing of our generated CSS, such as during minification, but if you chose to do so we recommend maintaining a precision of at least 6 to prevent issues with browser rounding. + +## Autoprefixer + +Bootstrap uses [Autoprefixer][autoprefixer] (included in our build process) to automatically add vendor prefixes to some CSS properties at build time. Doing so saves us time and code by allowing us to write key parts of our CSS a single time while eliminating the need for vendor mixins like those found in v3. + +We maintain the list of browsers supported through Autoprefixer in a separate file within our GitHub repository. See [.browserslistrc]({{< param repo >}}/blob/v{{< param current_version >}}/.browserslistrc) for details. + +## RTLCSS + +Bootstrap uses [RTLCSS](https://rtlcss.com/) to process compiled CSS and convert them to RTL – basically replacing horizontal direction aware properties (eg. `padding-left`) with their opposite. It allows us only write our CSS a single time and make minor tweaks using RTLCSS [control](https://rtlcss.com/learn/usage-guide/control-directives/) and [value](https://rtlcss.com/learn/usage-guide/value-directives/) directives. + +## Local documentation + +Running our documentation locally requires the use of Hugo, which gets installed via the [hugo-bin](https://www.npmjs.com/package/hugo-bin) npm package. Hugo is a blazingly fast and quite extensible static site generator that provides us: basic includes, Markdown-based files, templates, and more. Here's how to get it started: + +1. Run through the [tooling setup](#tooling-setup) above to install all dependencies. +2. From the root `/bootstrap` directory, run `npm run docs-serve` in the command line. +3. Open `http://localhost:9001/` in your browser, and voilà. + +Learn more about using Hugo by reading its [documentation](https://gohugo.io/documentation/). + +## Troubleshooting + +Should you encounter problems with installing dependencies, uninstall all previous dependency versions (global and local). Then, rerun `npm install`. + +[autoprefixer]: https://github.com/postcss/autoprefixer diff --git a/site/content/docs/5.0/getting-started/download.md b/site/content/docs/5.0/getting-started/download.md index e3c982d30..67bc295a9 100644 --- a/site/content/docs/5.0/getting-started/download.md +++ b/site/content/docs/5.0/getting-started/download.md @@ -21,10 +21,10 @@ This doesn't include documentation, source files, or any optional JavaScript dep Compile Bootstrap with your own asset pipeline by downloading our source Sass, JavaScript, and documentation files. This option requires some additional tooling: -- [Sass compiler]({{< docsref "/getting-started/build-tools#sass" >}}) for compiling Sass source files into CSS files +- [Sass compiler]({{< docsref "/getting-started/contribute#sass" >}}) for compiling Sass source files into CSS files - [Autoprefixer](https://github.com/postcss/autoprefixer) for CSS vendor prefixing -Should you require our full set of [build tools]({{< docsref "/getting-started/build-tools#tooling-setup" >}}), they are included for developing Bootstrap and its docs, but they're likely unsuitable for your own purposes. +Should you require our full set of [build tools]({{< docsref "/getting-started/contribute#tooling-setup" >}}), they are included for developing Bootstrap and its docs, but they're likely unsuitable for your own purposes. }}" class="btn btn-bd-primary" onclick="ga('send', 'event', 'Getting started', 'Download', 'Download source');">Download source @@ -52,7 +52,7 @@ If you're using our compiled JavaScript and prefer to include Popper separately, ## Package managers -Pull in Bootstrap's **source files** into nearly any project with some of the most popular package managers. No matter the package manager, Bootstrap will **require a [Sass compiler]({{< docsref "/getting-started/build-tools#sass" >}}) and [Autoprefixer](https://github.com/postcss/autoprefixer)** for a setup that matches our official compiled versions. +Pull in Bootstrap's **source files** into nearly any project with some of the most popular package managers. No matter the package manager, Bootstrap will **require a [Sass compiler]({{< docsref "/getting-started/contribute#sass" >}}) and [Autoprefixer](https://github.com/postcss/autoprefixer)** for a setup that matches our official compiled versions. ### npm diff --git a/site/data/sidebar.yml b/site/data/sidebar.yml index b4f63bfae..4bfdcc0ab 100644 --- a/site/data/sidebar.yml +++ b/site/data/sidebar.yml @@ -8,12 +8,12 @@ - title: Contents - title: Browsers & devices - title: JavaScript - - title: Build tools - title: Webpack - title: Parcel - title: Accessibility - title: RFS - title: RTL + - title: Contribute - title: Customize pages: -- cgit v1.2.3