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.
But our community is also working on other products that have a different release cycle, use case, docs build tool and needs
and other: #10550, #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 solution is moving all documentations to our app documentation:
#11136
#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
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.
But our community is also working on other products that have a different release cycle, use case, docs build tool and needs
and other: #10550, #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 solution is moving all documentations to our app documentation:
#11136
#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