Hi Dmitri, I propose having a separate documentation folder for each tool, which would make maintenance easier. Regarding versioning, I believe it is achievable.
As a side note, it may be worth considering moving each tool to a dedicated repository at some point, but we can discuss that separately :) Regards, JB On Tue, Dec 16, 2025 at 8:38 AM Dmitri Bourlatchkov < [email protected]> wrote: > Hi JB, > > This approach sounds good to me. > > I wonder, though, are we going to have separate docs sub-dirs for each tool > or one global tools docs? > > Are we going to archive versioned tools docs the same way we do for > the main docs? > > Thanks, > Dmitri. > > On Tue, Dec 16, 2025 at 11:04 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi folks, > > > > Currently, the website and documentation for Polaris are stored within > the > > polaris repository. > > > > While this structure works well for documenting the Polaris design, > server, > > and CLI, it doesn't effectively cover the documentation for the > associated > > tools (Catalog Migrator, Benchmark, MCP Server, and Console). > > > > I propose we consider having the specific tool documentation to the > > polaris-tools repository. This would ensure the documentation remains > > up-to-date with the latest tool features. We could then link to this > > documentation from the main website (currently in the polaris repo). > > > > Thoughts on this approach? > > > > Regards, > > JB > > >
