@@ -4,11 +4,11 @@ Build process customization
4
4
Read the Docs has a :doc: `well-defined build process </builds >` that works for many projects.
5
5
We also allow customization of builds in two ways:
6
6
7
- Extend or partially override the build process
7
+ Customize our standard build process
8
8
Keep using the default commands for MkDocs or Sphinx,
9
9
but extend or override the ones you need.
10
10
11
- Completely override the build process
11
+ Define a build process from scratch
12
12
This option gives you *full control * over your build.
13
13
Read the Docs supports any tool that generates HTML.
14
14
@@ -17,8 +17,8 @@ Extend or override the build process
17
17
18
18
In the normal build process, the pre-defined jobs ``checkout ``, ``system_dependencies ``, and ``upload `` are executed.
19
19
If you define a :ref: `config-file/v2:sphinx ` or :ref: `config-file/v2:mkdocs ` configuration,
20
- the ``create_environment ``, ``install ``, and ``build `` jobs will use the default commands for the selected tool,
21
- otherwise, they will default to run nothing .
20
+ the ``create_environment ``, ``install ``, and ``build `` jobs will use the default commands for the selected tool.
21
+ If no tool configuration is specified, these jobs won't execute anything by default .
22
22
23
23
The jobs where users can customize our default build process are:
24
24
0 commit comments