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

Create a DataFusion blog #10535

Closed
andygrove opened this issue May 15, 2024 · 3 comments
Closed

Create a DataFusion blog #10535

andygrove opened this issue May 15, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@andygrove
Copy link
Member

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.

[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

@andygrove andygrove added the enhancement New feature or request label May 15, 2024
@andygrove andygrove self-assigned this May 15, 2024
@andygrove
Copy link
Member Author

I volunteer to take this on

@alamb
Copy link
Contributor

alamb commented May 15, 2024

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)

@andygrove
Copy link
Member Author

This task is complete: https://datafusion.apache.org/blog/

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

No branches or pull requests

2 participants