Thanks for doing this work, Larry. The draft version is already more usable than what we've had up until now.
I propose we take the time to review the draft contents, and create JIRAs for things like missing information, broken links, and outdated content. Then, folks can assign themselves JIRAs to work on to avoid stepping on each other. The scope of each JIRA can vary such that we can avoid have an unreasonable excess of JIRA issues. We may even want to organize epics corresponding to different topics/areas to minimize conflicts. Docs are especially important for a project like Knox, and I think this will all have been time well spent. Thanks, - Phil On Thu, Jun 12, 2025 at 10:17 AM larry mccay <lmc...@apache.org> wrote: > Hey Folks - > > I've just enabled Github Pages for the Apache Knox Github Mirror > repository and published a draft version of our next gen docs site. > > The site is managed and built using MkDocs and the home page has some very > basic usage tips. > You will find the source in the knox-site folder in the project. > > As mentioned in previous DISCUSS threads, we are standing this up in draft > mode so that we can spin up a Docathon and track down broken links, images, > obsolete content and iterate on it over a couple weeks. > > This will become our new documentation site for 2.1.0 and beyond. > > Here is the link for the draft version. > https://apache.github.io/knox/ > > What do you think about starting to review and fix issues via PR? > Any thoughts on how do we do so without stepping on each other? > I feel like a JIRA per change may be onerous but it is our PR policy. > > thanks, > > --larry > >
