You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge?
We do not currently have a blog set up for DataFusion.
The DataFusion website at https://datafusion.apache.org is published from the sphinx documentation in the core DataFusion project. Sphinx does not have blogging functionality built-in, so we will need to set up a blog using some other solution.
The Apache Arrow site, where we previously published DataFusion posts, uses Jekyll [1], so the easiest path is for us to continue to use jekyll. We could even choose to republish old DataFusion posts on the new site so we have a complete history here.
I propose that we create a datafusion-site or datafusion-blog repo for the blog content to keep it separate from the software.
The Apache Arrow site, where we previously published DataFusion posts, uses Jekyll [1], so the easiest path is for us to continue to use jekyll. We could even choose to republish old DataFusion posts on the new site so we have a complete history here.
+1
I propose that we create a datafusion-site or datafusion-blog repo for the blog content to keep it separate from the software.
A separate repo makes sense to me. Eventually we should probably move all doc content into a repo like datafusion-site but there is pretty serious value at the moment in my mind to being able to make a single PR with code changes and the relevant doc changes (which would not be possible if we moved the docs to a different repo)
Is your feature request related to a problem or challenge?
We do not currently have a blog set up for DataFusion.
The DataFusion website at https://datafusion.apache.org is published from the sphinx documentation in the core DataFusion project. Sphinx does not have blogging functionality built-in, so we will need to set up a blog using some other solution.
The Apache Arrow site, where we previously published DataFusion posts, uses Jekyll [1], so the easiest path is for us to continue to use jekyll. We could even choose to republish old DataFusion posts on the new site so we have a complete history here.
I propose that we create a
datafusion-site
ordatafusion-blog
repo for the blog content to keep it separate from the software.[1] https://github.com/apache/arrow-site
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: