Hi Prajwal, Thanks for the kind words and for raising this.
The blog separation worked because blogs aren't tied to a release. Documentation is the opposite; every feature PR updates its docs in the same commit, on the same branch. That gives us atomic reviews and version-correct docs per release line. Splitting /website out would probably also break fluss-docgen, which reflects over ConfigOptions.java at build time, and turn release votes into a two-repo coordination problem. The biggest issue with assets is mainly on the blog, where we add many things frequently, compared to the website and docs assets. If you have more concerns, we can definitely start a separate DISCUSS thread on dev@ if others want to push further for this or discuss more. Best, Giannis On Sat, May 9, 2026 at 10:46 AM Prajwal Banakar <[email protected]> wrote: > Hi Giannis, > > The new website is looking beautiful and feels much more modern and easier > for newcomers to understand. > > One thought I had while looking through this: since the website is already > maintained as a submodule in the Fluss main repo, would it make sense to > move the new website into a separate dedicated repository as well? > > Since the blogs were recently moved into a separate repo too, I was > wondering whether it could make sense to eventually have > > - a dedicated website repo > > - merge the website and blog repositories together > > - faster iteration/design improvements without touching the main Fluss repo > frequently > > Also, if we ever want to refer back to context or assets from the existing > website during future iterations, having a dedicated place for > website-related work may make that easier to manage. > > I feel website/UI/content changes usually evolve very quickly, and keeping > them isolated might make contributions easier and reduce noise/confusion in > the main repository history. > > Curious to hear your thoughts on this approach! > > Best, > > prajwal > > On Fri, 8 May 2026 at 17:37, Giannis Polyzos <[email protected]> > wrote: > > > Hi folks, > > > > Since the project was open-source we had a few discussions around > updating > > our website. However due to bandwidth and the lack of a website designer > we > > couldn't really do much. > > > > Along with that, we have received lot's of feedback from people > interested, > > that when landing to the website its really hard to understand what fluss > > is, why should someone care or how it compared with Kafka for example. > > > > These days we are lucky to have AI tools and with that we made an effort > > using AI, to try and update our website. You can find a branch you can > > build and see a new proposed website here: > > > > https://github.com/apache/fluss/pull/3226 > > > > There are some screenshots attached for reference. Initially we also had > a > > toggle between light and dark mode, however because our current diagrams > > don't render really well in dark mode I disabled them. > > > > Please let me know your thoughts and any feedback you might have so we > can > > improve. > > > > Best, > > Giannis > > >
