-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation #114
Comments
The name |
Just curious, what would be the relationship with docs of crates on docs.rs? |
cc @Xuanwo |
From the ASF perspective, anything outside of |
I took a look at |
I'm not super familiar with the Rust ecosystem, but I don't see any issues with having that on docs.rs. For other things, for example, how to contribute, how to release etc it would be best to keep that on the Apache side. It would also be great if we use mkdocs to make it easier to potentially merge the languages later on. |
Just FYI, rust ecosystem has centralized online docs, here is just an example: |
I'm fine with not keeping a main branch for the API documentation. We can begin with the simplest approach and expand it later. |
cc @Xuanwo Are you working on this? I think we are ok to ship the first release now, all blockers has been resolved. |
I expect to finish it in next week. |
It would be great to have a minimal set of docs. I think we can get a lot of inspiration from the PyIceberg project where we use mkdocs: https://github.com/apache/iceberg-python/tree/main/mkdocs
We can copy the structure and the CI to deploy it.
With the
CNAME
file we can tell the ASF to set up a DNS entry to the docs. We could dohttps://rs.iceberg.apache.org/
orhttps://rust.iceberg.apache.org/
, but I'll leave that up to the project.The text was updated successfully, but these errors were encountered: