Hi everyone, I'd like to let you know that the blog content has been moved from the main Fluss repository (apache/fluss) to a dedicated repository:https://github.com/apache/fluss-blog
See https://github.com/apache/fluss/issues/3128 for the full context. Why the change? The website/blog/ directory in the main repo contained blog posts along with a large number of image assets. As the blog grows, these binary files significantly increase the repository size, slow down clones, and add noise to the main codebase which is primarily focused on the Fluss engine itself. What changes for blog contributors? New repo for blog contributions: All blog-related PRs (new posts, edits, images) should now be submitted to apache/fluss-blog instead of the main repo. * Standalone preview: The blog repo includes a minimal Docusaurus setup, so you can preview posts locally by simply running npm install && npm start — no need to build the full website. * Post format unchanged: The blog post format (Markdown frontmatter, image paths, authors.yml, tags.yml) remains the same. * Auto-publishing: Once a blog post PR is merged into the main branch of fluss-blog, a CI pipeline will automatically build and publish the content to https://fluss.apache.org/blog. What changes for website developers? A website/setup_blog.sh script has been added to the main repo. Run it once to clone the blog content into website/blog/ before local website development. The CI workflow (docs-check.yaml) has been updated to run this script automatically, so the full website build (with blog) continues to work as before. If you have any questions or concerns, please don't hesitate to reach out. Best regards, Jark Wu
