On Fri, Mar 27, 2026 at 3:32 AM Yurii Palamarchuk < [email protected]> wrote:
> Hi there, > > I am proposing an upgrade to the ZooKeeper website and documentation. We > are moving to a modern React.js stack, which allows landing pages and > versioned documentation to live in a single application sharing the same UI > components, libraries, colors, etc. > > The plan is to move all website and documentation source code to the > website branch and remove the zookeeper-docs Maven project from the master > branch. This decouples the Node/JS build environment from the core Java > repository. > > Versioned docs will be managed via archived folders within the website > branch. Documentation updates would move from master to PRs against the > website branch. Also I'm not planning to keep the app as a maven project, > since it's fully JS based. To keep it simple, I will write a bash script > that installs the dependencies, runs the tests, and the build. > > What do you think about moving the docs out of master to centralize the > site? > > Preview: https://zookeeper-website.vercel.app/ > > Looks pretty slick - nice update and visual refresh! Question though - why React? This is a static website, what are the pro/con of React based? Can you explain the impact on common use cases like making updates? ZK team includes a number of people, not all of whom might know React, how hard will it be for them to make changes? Impact on the release process? Regards, Patrick > Best regards, > Yurii Palamarchuk >
