aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/_layouts
Commit message (Collapse)AuthorAge
* Add Bazel Vision document.Gravatar Dmitry Lomov2018-07-23
| | | | | | | | Add Bazel Vision document. Closes #5612. PiperOrigin-RevId: 205652638
* Update Bazel and Android sidebar links to provide direct links to core resourcesGravatar jingwen2018-07-12
| | | | | RELNOTES: None. PiperOrigin-RevId: 204320776
* Remove the experimental section on the website.Gravatar laurentlb2018-07-11
| | | | | | | | The page https://docs.bazel.build/versions/master/experimental.html is not useful. The only link is also available via the `Bazel and Apple` section. RELNOTES: None. PiperOrigin-RevId: 204110632
* Document troubleshooting Bazel remote execution using the Docker sandbox ↵Gravatar spomorski2018-06-13
| | | | | | feature. PiperOrigin-RevId: 200451804
* Document adapting custom Bazel rules for remote execution.Gravatar spomorski2018-06-11
| | | | PiperOrigin-RevId: 200060887
* Publish detailed configurable attributes (select()) documentation.Gravatar gregce2018-06-08
| | | | | | Fixes #2154 PiperOrigin-RevId: 199830177
* Add link to the auto-generated Node_JS rules documentation.Gravatar spomorski2018-06-08
| | | | | RELNOTES: None. PiperOrigin-RevId: 199796230
* Fix submenu element ID.Gravatar spomorski2018-06-04
| | | | | RELNOTES: None. PiperOrigin-RevId: 199184609
* Add documentation for building JavaScript outputs.Gravatar spomorski2018-06-04
| | | | | RELNOTES: None. PiperOrigin-RevId: 199151698
* Externalize testing guidance for Skylark codeGravatar brandjon2018-04-23
| | | | | | | Mainly this is about using unittest.bzl to test rules or helper functions. RELNOTES: PiperOrigin-RevId: 193973496
* Rename a few pagesGravatar brandjon2018-03-19
| | | | | | | | | Prefer "Extension" over "Skylark" when referring specifically to Bazel's use of Skylark. Follow-up to https://github.com/bazelbuild/bazel/commit/3ef60b7cdcf8826102ec42a77183645ab0cafcf7. RELNOTES: None PiperOrigin-RevId: 189602396
* Split off troubleshooting section into a FAQ pageGravatar brandjon2018-03-18
| | | | | | | | | Rewrite/add to the contents of this section. Also updated the page titles / navbar entries of Skylark documentation to make them more uniform (title case, avoid redundancy). RELNOTES: None PiperOrigin-RevId: 189503729
* Fixed broken links to user manual in docsGravatar Jingwen Chen2018-03-05
| | | | | | | | The user manual filename has been renamed from `bazel-user-manual.html` to `user-manual.html`. Closes #4662. PiperOrigin-RevId: 187877241
* Update site menuGravatar laurentlb2018-02-23
| | | | | | | In particular, use folding menus for Installing and Tutorials. RELNOTES: None. PiperOrigin-RevId: 186778997
* site/docs: add documentation for remote caching.Gravatar Jakob Buchgraber2018-02-02
| | | | | | Closes #4540. PiperOrigin-RevId: 184349872
* Replace link to cookbook with link to Github examplesGravatar laurentlb2017-12-15
| | | | | RELNOTES: None. PiperOrigin-RevId: 179174976
* Remove the word 'Skylark' when it doesn't add any value.Gravatar laurentlb2017-12-14
| | | | | | | | | | | The word Skylark tends to be overused. We should use it only when we refer to the language itself. In many places, the word 'Skylark' was used, even if the reader may not know it (e.g. "create a rule" is clearer than "create a Skylark rule"). RELNOTES: None. PiperOrigin-RevId: 179024448
* Reorganize menu in "Extending Bazel"Gravatar laurentlb2017-12-12
| | | | | RELNOTES: None. PiperOrigin-RevId: 178765624
* Update section heading.Gravatar spomorski2017-12-11
| | | | | RELNOTES: None. PiperOrigin-RevId: 178618216
* Fixed documentation navigation bar/content layout awkwardness.Gravatar Jingwen2017-12-11
| | | | | | | | | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/4262 A specific browser view width range causes the navigation bar to be stacked on top of the documentation content, therefore requiring a bit of scrolling to get to it. This fix changes col-lg-* to col-md-*, which reduces the view width threshold at which the columns are restyled using `@media queries`. Tested locally on Chrome & Safari. This is also testable by going to the production site and changing the CSS classes in the inspector. Closes #4263. PiperOrigin-RevId: 178605473
* Tweak the grammar of some titles in bazel documentation.Gravatar ahumesky2017-12-08
| | | | | RELNOTES: None. PiperOrigin-RevId: 178406494
* Restructure left-nav to be more intuitive.Gravatar spomorski2017-12-07
| | | | | RELNOTES: None. PiperOrigin-RevId: 178292524
* Fix link to Skyark Linter docs from main docs navigationGravatar Akira Baruah2017-12-04
| | | | | | | | Fixes #4202 Closes #4214. PiperOrigin-RevId: 177829932
* Add Linter & Skylark spec to the website menuGravatar laurentlb2017-11-27
| | | | | RELNOTES: None. PiperOrigin-RevId: 176993543
* Rewrite Bazel platform and toolchain documentation for clarity and split ↵Gravatar spomorski2017-11-06
| | | | | | into separate topics. PiperOrigin-RevId: 174510719
* Adding platform documentation.Gravatar jcater2017-11-06
| | | | PiperOrigin-RevId: 174473387
* Add performance section to Skylark docs.Gravatar tomlu2017-11-03
| | | | | | | This includes docs on how to use the memory profiler. RELNOTES: None PiperOrigin-RevId: 174374064
* Fix link and formatting.Gravatar spomorski2017-10-27
| | | | PiperOrigin-RevId: 173540551
* Create an "Experimental" section.Gravatar spomorski2017-10-25
| | | | PiperOrigin-RevId: 173277159
* Create a Bazel migration guide for Xcode.Gravatar spomorski2017-10-06
| | | | PiperOrigin-RevId: 171193160
* Move "mobile-install (Android)" link in navigation bar to the android ↵Gravatar ahumesky2017-10-06
| | | | | | | section and rename to just "mobile-install". RELNOTES: None. PiperOrigin-RevId: 171021110
* Add Fedora install instructions.Gravatar Jakob Buchgraber2017-09-26
| | | | | | | Closes #3721. Change-Id: I4ce8ef72c4ee2b6352df78301888b85388c7c36d PiperOrigin-RevId: 169922383
* Create the "Android and Bazel" and "Apple apps and Bazel" pages.Gravatar Googler2017-09-14
| | | | PiperOrigin-RevId: 168577347
* Rename bazel-user-manual.html into user-manual.htmlGravatar dmarting2017-09-04
| | | | PiperOrigin-RevId: 167477112
* Link to the Tulsi and IntelliJ plugin pages.Gravatar Googler2017-08-17
| | | | PiperOrigin-RevId: 165493537
* Split the mobile app tutorial into separate Android and iOS tutorials and ↵Gravatar Googler2017-08-09
| | | | | | | eliminate the backend server tutorial. RELNOTES: None. PiperOrigin-RevId: 164653190
* site: add documentation about the BEP and BESGravatar Jakob Buchgraber2017-08-07
| | | | | | | Provide an overview of the Build Event Protocol and Build Event Service. Change-Id: If11a060cea7ce0fef80486a473b0f7c1b523f50c PiperOrigin-RevId: 164435311
* Tutorial about macro creationGravatar laurentlb2017-07-24
| | | | | RELNOTES: None. PiperOrigin-RevId: 162736242
* Tutorial for sharing a variableGravatar laurentlb2017-07-24
| | | | | | | Intended to be an introduction before talking about macros. RELNOTES: None. PiperOrigin-RevId: 162733299
* Fix link in the menuGravatar laurentlb2017-07-20
| | | | | RELNOTES: None. PiperOrigin-RevId: 162512994
* Move Backward compatibility to a separate page.Gravatar laurentlb2017-07-19
| | | | | RELNOTES: None PiperOrigin-RevId: 162476598
* Add a concepts menu to extensions documentationGravatar laurentlb2017-07-18
| | | | | RELNOTES: None. PiperOrigin-RevId: 162242575
* Instructions for migrating from Maven to BazelGravatar Googler2017-07-18
| | | | PiperOrigin-RevId: 162210415
* Docs: Do not display Edit button on Skylark reference pagesGravatar steren2017-07-10
| | | | | | | Fix #3335 RELNOTES: None PiperOrigin-RevId: 161384915
* For topic about generate_workspace tool, fixed broken links and did some ↵Gravatar Googler2017-07-05
| | | | | | rewording. PiperOrigin-RevId: 160955003
* Describe the tool `generate_workspace` in a separate topic. Update ↵Gravatar Googler2017-07-03
| | | | | | instructions for generating a WORKSPACE file. PiperOrigin-RevId: 160673799
* Bazel docs: Fix Edit buttonGravatar steren2017-06-28
| | | | | | | | | | The new doc website has a new URL structure. This change adapts the page extraction code. It also restores the CSS for the edit button which got deleted during refactoring. Fix #3272 RELNOTES: None PiperOrigin-RevId: 160279009
* Rework jekyll-tree build to add redirects from site root.Gravatar dzc2017-06-26
| | | | | | | | | | | | | | As described in the commit message for 5596d3b, the new docs.bazel.build site will have one directory per released version and a master directory for the latest documentation at HEAD. This change reworks the jekyll-tree script to construct a final Jekyll tree containing the documentation at HEAD with documentation under /versions/master and redirect pages at the site root for each documentation page. TESTED=scripts/serve-docs.sh RELNOTES: None PiperOrigin-RevId: 159920553
* Remove Support page from docs.Gravatar dzc2017-06-26
| | | | | RELNOTES: None PiperOrigin-RevId: 159920547
* Fix paths in Bazel docs, removing references to versions/master.Gravatar dzc2017-06-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Follow-up to https://github.com/bazelbuild/bazel/commit/22b85a2a3c79c6f3aef1e0a61e485bb135be4551. This change updates paths and URLs to Bazel docs, removing the versions/master directory and changing bazel.build/docs to docs.bazel.build. For clarification on the convention of the docs site, links referencing docs.bazel.build/foo.html will be redirected to docs.bazel.build/versions/master/foo.html. The versions/master directory will contain the documentation pages pushed from HEAD. Once versioned documentation is ready, then docs.bazel.build/foo.html will instead be redirected to docs.bazel.build/x.y.z/foo.html, where x.y.z is the directory for the latest stable Bazel version. Follow-ups to this change: * Add script that will be used by the daily push job that pushes the latest documentation from HEAD to docs.bazel.build. This script will do the following: * Build the Jekyll tree, run jekyll build, and modify the resulting site tree, moving the docs/ directory into versions/master. * Add redirects for each of the site pages from the root of the site to the corresponding page in versions/master. * This should give us the minimum viable product for the new docs site. * Add script for cutting a release of the docs and pushing to a new versioned directory on the docs.bazel.build bucket. RELNOTES: None PiperOrigin-RevId: 158347197