This directory contains documentation for the Apache Airflow project and the providers packages that are closely related to it. You can contribute to the Airflow Docs in the same way and for the same reasons as contributing code; Docs contributions that improve existing content, fix bugs, and create new content are welcomed and encouraged.
This README gives an overview about how Airflow uses Sphinx to write and build docs. It also includes instructions for how to make Docs changes locally or with the GitHub UI.
You can find documentation for the current development version at s.apache.org/airflow-docs, where it is automatically built and published.
Airflow Documentation uses Sphinx, a reStructure Text (.rst) markup language that was developed to document Python and Python projects, to build the docs site.
For most Docs writing purposes, the reStructured Text Primer provides a quick reference of common formatting and syntax.
When you make changes to the docs, it follows roughly the same process as creating and testing code changes. However, for docs, instead of unit tests and integration tests, you run pre-commit checks, spell checks, and visual inspection of your changes in a documentation build.
- Decide to edit in GitHub UI or locally - Depending on the size and type of docs update you want to make, it might be easier to work in the UI or to make your edits in a local fork.
- Find the source files to edit - While you can access most of the docs source files using the Suggest a change on this page button or by searching for a string in the
/docs/file directory, in some cases, the source strings might be located in different provider docs or in the source code itself. - If editing locally, run spellcheck and the build to identify any blocking errors - Docs require build, spellcheck, and precommit CI/CD tests to pass before they can merge. This means that if you have a pull request with docs changes, a docs build error can prevent your code merge. Checking the build and spelling locally first can help speed up reviews. If you made formatting changes, checking a local build of your docs allows you to make sure you correctly formatted elements like tables, text styling, and line breaks.
- Make your pull request - When you make a PR, Github automatically assigns reviewers and runs CI/CD tests.
- Fix any build errors or spelling mistakes - Your PR can't be merged if there are any spelling or build errors. Check to see which builds are failing and click Show details. The output of the tests share the errors, location of the problems, and suggest resolutions. Common Docs failures occur due to incorrect formatting and whitespace.
You have two options for editing Airflow docs:
- Through the online GitHub Editor by clicking Suggest a change on this page in the docs, or by selecting a file in GitHub.
- Locally with a forked copy of the Airflow repo, where you can run local builds and tests prior to making a pull request.
| Type of Docs update | Suggested Editor | Explanation |
|---|---|---|
| I need to edit multiple files. | Local Editor | It's easier to batch-edit files in an editor, than make multiple PRs or changes to individual files in a GitHub editor. |
| I want to fix a quick typo or a broken link. | GitHub Editor | Allows you to quickly edit without any local installation or build required. |
| My edits contain tables or other formatting changes. | Local Editor | GitHub can provide Markdown previews, but might
change .rst styling. Use a local build. |
| I want to make a new page/ delete a page. | Local Editor | Will need a local build to check navigation and link redirects. |
| I want to edit autogenerated content on a page. | Either, probably Local Editor | Allows you to easily find the correct file and generate a preview before creating the PR. |
Sphinx has _roles_ and _directives_, where Markdown docs frameworks often do not have similar functionality. This means that Airflow uses directives to pull code examples, autogenerate indexes and tables of contents, and reference from resources across the codebase and across documentation provider packages. This can make it confusing to find the content source on certain types of reference pages.
For example, in Command Line Interface and Environment Variables Reference, the CLI reference is autogenerated, and requires more complex scripting. While the Environment Variables are explicitly written.
To make an edit to an autogenerated doc, you need to make changes to a string in the Python source file. In the previous example, to make edits to the CLI command reference text, you must edit the cli_config.py source file.
To generate a local version of the docs you can use ../BREEZE.rst.
The documentation build consists of verifying consistency of documentation and two steps:
- spell checking
- building documentation
You can choose to run the complete build, to build all the docs and run spellcheck. Or, you can use package names and the optional flags, --spellcheck-only or --docs-only to choose the scope of the build.
Build all docs and spell check them:
breeze build-docsJust run spellcheck:
breeze build-docs --spellcheck-onlyBuild docs without checking spelling:
breeze build-docs --docs-onlyBuild documentation of just one provider package by calling the PACKAGE_ID.
breeze build-docs PACKAGE_IDSo, for example, to build just the apache-airflow-providers-apache-beam package docs, you would use the following:
breeze build-docs apache.beamOr, build docs for more than one provider package in the same command by listing multiple package IDs:
breeze build-docs PACKAGE1_ID PACKAGE2_IDYou can also use shorthand names as arguments instead of using the full names for airflow providers. To find the short hand names, follow the instructions in :ref:`generating_short_form_names`.
You can see all the available arguments via --help.
breeze build-docs --helpAfter you build the documentation, you can check the formatting, style, and documentation build at http://localhost:28080/docs/
by starting a Breeze environment or by running the following command from the root directory.
You need to have Python installed to run the command:
docs/start_doc_server.shThen, view your docs at localhost:8000. If you use a virtual machine, like WSL2,
you need to find the WSL2 machine IP address and replace "0.0.0.0" in your browser with it. The address looks like
http://n.n.n.n:8000, where n.n.n.n is the IP of the WSL2.
Skip the apache-airflow-providers- from the usual provider full names.
Now with the remaining part, replace every dash("-") with a dot(".").
Example:
If the provider name is apache-airflow-providers-cncf-kubernetes, it will be cncf.kubernetes.
Note: For building docs for apache-airflow-providers index, use apache-airflow-providers as the
short hand operator.
Cross-references are generated by many semantically interpreted text roles. Basically, you only need to write:
:role:`target`And Sphinx creates a link to the item named target of the type indicated by role. The link's text is the same as target.
You can supply an explicit title and reference target, like in reST direct hyperlinks:
:role:`title <target>`This will refer to target, but the link text will be title.
Here are practical examples:
:class:`airflow.models.dag.DAG` - link to Python API reference documentation
:doc:`/docs/operators` - link to other document
:ref:`handle` - link to section in current or another document
.. _handle:
Section title
----------------------------------Role :class: works well with references between packages. If you want to use other roles, it is a good idea to specify a package:
:doc:`apache-airflow:installation/index`
:ref:`apache-airflow-providers-google:write-logs-stackdriver`If you still feel confused then you can view more possible roles for our documentation:
./list-roles.shFor more information, see: Cross-referencing syntax in Sphinx documentation
If you are creating example_dags directory, you need to create an example_dags/__init__.py file. You can leave the file empty and the pre-commit processing
adds the license automatically. Otherwise, you can add a file with the Apache license or copy another __init__.py file that contains the necessary license.
.rst syntax is sensitive to whitespace, linebreaks, and indents, and can affect build output. When you write content and either skip indentations, forget linebreaks, or leave trailing whitespace, it often produces docs build errors that block your PR's mergeability.
Certain Sphinx elements, like lists and code blocks, require a blank line between the element and the next part of the content. If you do not add a blank line, it creates a build error.
WARNING: Enumerated list ends without a blank line; unexpected unindent.
While easy to resolve, there's a Sphinx bug in certain versions that causes the
warning to report the wrong line in the file for your missing white space. If your PR has the unexpected unindent warning blocking your build,
and the line number it reports is wrong, this is a known error. You can find the missing blank space by searching for the syntax you used to make your
list, code block, or other whitespace-sensitive markup element.
If you need help, write to #documentation channel on Airflow's Slack.
For more resources about working with Sphinx or reST markup syntax, see the Sphinx documentation.
The Write the Docs community also includes a #Sphinx Slack channel for questions and additional support.