Introduce an automated Hugo build and publish branch.

[Ma77Ball]

Task Summary

This PR adds a GitHub Actions workflow that builds the Hugo site and publishes the generated static files to a new publish branch. Previously, the repo stored built static files directly in main and staging; this workflow cleanly separates source from output and ensures reproducible builds.

After merging, pushes to main will automatically rebuild and deploy the website to publish.

Priority

P3 – Low

Task Type

• Code Implementation
• Documentation
• Refactor / Cleanup
• Testing / QA
• DevOps / Deployment

[chenlica]

@aglinxinyuan What are your thoughts?

[aglinxinyuan]

It’s a good idea. Please check the asf.yaml documents — they include an automated publishing feature.

[Ma77Ball]

@chenlica @aglinxinyuan I looked at asf.yml, but it only automates the build process for Jekyll and Pelican. I raised a PR to do this using GitHub workflows, as other sites do, which will also allow us to add checks on the website to ensure compliance with the Apache Infra website requirements. Please review and let me know how it looks.

pr link: apache/incubator-texera-site#13

[chenlica]

I merged it. Please test the staging site.

[Ma77Ball]

The staging site looks good to me, which I'm surprised by, as I thought the .asf.yml would need to be in main. The workflow did precisely what it was supposed to (made publish-staging), and the website looks the same. This will help with code review as changes won't be static content but Hugo config and MD files.

[chenlica]

Please let me know if you want me to raise a PR to deploy the staging site to the main site.

[Ma77Ball]

I think we can merge after resolving #4063, since this is a convenience, and merging would only leave the main website incomplete.