Files
datafusion/docs
Andrew Lamb 013efb4fe1 docs: Refine Communication documentation to highlight Discord (#19714)
## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes #123` indicates that this PR will close issue #123.
-->

- Part of #7013 

## Rationale for this change

I was speaking with someone who wanted to get more involved with
DataFusion recently, and it was not clear from the website that discord
is far more active than Slack. I think it would help new new users to
make this clearer in the documentation to lower the barrier to joining
the communitu


## What changes are included in this PR?


Improve the communication documentation here:
https://datafusion.apache.org/contributor-guide/communication.html and
mention that discord is more active than slack

<img width="1191" height="856" alt="Screenshot 2026-01-09 at 8 54 39 AM"
src="https://github.com/user-attachments/assets/9bbef5d4-645d-45f0-85aa-6b12a2a7eea5"
/>


While I was reviewing the communication documentation, I noticed some
other minor issues that could be improved which I will call out inline

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
2026-01-11 03:21:26 +00:00
..
2024-03-02 08:44:04 -07:00

DataFusion Documentation

This folder contains the source content of the User Guide and Contributor Guide. These are both published to https://datafusion.apache.org/ as part of the release process.

Dependencies

It's recommended to install build dependencies and build the documentation inside a Python virtualenv.

python3 -m venv venv
pip install -r requirements.txt

If using uv the script can be run like so without needing to create a virtual environment:

uv run --with-requirements requirements.txt bash build.sh

Build & Preview

Run the provided script to build the HTML pages.

# If using venv, ensure you have activated it
./build.sh

The HTML will be generated into a build directory. Open build/html/index.html in your preferred browser, e.g.

Preview the site on Linux by running this command.

# On macOS
open build/html/index.html
# On Linux with Firefox
firefox build/html/index.html

Making Changes

To make changes to the docs, simply make a Pull Request with your proposed changes as normal. When the PR is merged the docs will be automatically updated.

Release Process

This documentation is hosted at https://datafusion.apache.org/

When the PR is merged to the main branch of the DataFusion repository, a github workflow which:

  1. Builds the html content
  2. Pushes the html content to the asf-site branch in this repository.

The Apache Software Foundation provides https://datafusion.apache.org/, which serves content based on the configuration in .asf.yaml, which specifies the target as https://datafusion.apache.org/.