mik-laj opened a new issue #11152:
URL: https://github.com/apache/airflow/issues/11152
Hi.
I have fantastic news. We are growing! 🐈 Together with this, our
documentation grows and we have newer needs and requirements.
We currently only publish documentation for our app releases.
- https://airflow.apache.org/docs/stable/
But our community is also working on other products that have a different
release cycle, build tool and needs
- Production Docker image: https://hub.docker.com/r/apache/airflow
- Backport packages:
https://github.com/apache/airflow/tree/master/backport_packages
- Helm Chart: https://github.com/apache/airflow/tree/master/chart
- Apache Airflow API client for Go:
https://github.com/apache/airflow-client-go
- Apache Airflow API client for Python:
https://github.com/apache/airflow-client-python
- Apache Airflow API client for Java:
https://github.com/apache/airflow-client-java
- Apache Airflow API client for Javascript:
https://github.com/apache/airflow-client-javascript
- Apache on K8S Operator: https://github.com/apache/airflow-on-k8s-operator
and other: https://github.com/apache/airflow/issues/10550,
https://github.com/apache/airflow/issues/10552
I think it is worth considering how we want to inform users about these
products on our website. One solution is to create an index at:
`https://airflow.apache.org/docs/` (currently there is a redirection to the
latest stable version of the documentation), which will refer you to separate
documentation for each product.
It will look similar to the examples:
https://mc-stan.org/
https://cloud.google.com/sql/docs/
https://www.terraform.io/docs/
An alternative idea is to move the documentation to our app documentation:
https://github.com/apache/airflow/pull/11136
https://github.com/apache/airflow/pull/10998
What is our plan for this documentation? Do we need to standardize our
documentation building tools? What requirements does each documentation have,
e.g. do we always need versioning?
CC: @kaxil @potiuk
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
