Skip to content
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

Add datafusion website #148

Merged
merged 1 commit into from
Sep 20, 2021
Merged

Add datafusion website #148

merged 1 commit into from
Sep 20, 2021

Conversation

houqp
Copy link
Member

@houqp houqp commented Sep 20, 2021

Following the advice from @kszucs : https://lists.apache.org/thread.html/r5c9341fe5360ae249532724da2bf92bd2ed661d1c58f599212e82107%40%3Cdev.arrow.apache.org%3E.

This is the document build from https://github.com/apache/arrow-datafusion/tree/master/docs.

I will add link to the home page header as follow up PR after the first version of the page have been deployed and validated.

Here is what the page looks like from local build:

df-doc-new

@kszucs kszucs changed the title add datafusion website Add datafusion website Sep 20, 2021
Copy link
Member

@kszucs kszucs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @houqp!

@kszucs kszucs merged commit e6c5dd7 into apache:asf-site Sep 20, 2021
@kszucs
Copy link
Member

kszucs commented Sep 20, 2021

It is available at: https://arrow.apache.org/datafusion/

Is the website update process documented in the datafusion release guide?

What do you think about placing the datafusion docs page under the docs dir, so it would be reachable at: https://arrow.apache.org/docs/datafusion/ ?

@houqp houqp deleted the qp_asf-site branch September 20, 2021 17:33
@houqp
Copy link
Member Author

houqp commented Sep 20, 2021

Thanks @kszucs for being thorough and asked for a documentation update :) I was planning to add docs for the release step later this week after I validated the process with a successful release.

The reason I kept it under /datafusion path was due to the feedback from apache/arrow#10982 (comment). From a grouping point of view, it seems more logical to have all sub paths within the docs folder to be linked in https://arrow.apache.org/docs/. Perhaps a better path for us would be https://arrow.apache.org/datafusion/docs/?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants