I did some reviews of the PRs that led up to this, and I think the new site is much easier to maintain and deploy. +1 from my end :)
Cheers, Fokko Op ma 29 jan 2024 om 15:15 schreef Jean-Baptiste Onofré <j...@nanthrax.net>: > +1 > > Regards > JB > > On Fri, Jan 26, 2024 at 11:40 PM Brian Olsen <bitsondata...@gmail.com> > wrote: > > > > Hey everyone, > > > > As discussed during the community sync, I'd like to get a vote on moving > forward with the documentation. I have created a PR ( > https://github.com/apache/iceberg/pull/9520) that references the changes > that have happened up to this point. > > > > Simpler contribution by collocating the website and documentation in the > same repository. > > We don't want the versioned docs or javadoc files to be tracked in the > > main branch to avoid multiple copies of the docs being indexed in GitHub > or > > IDEs. > > We need a top level (non-versioned) Iceberg website that links versioned > > docs and contains evergreen constructs. > > The current docs release process is cumbersome and the code lives across > > multiple repositories making it difficult to know where to contribute for > > documentation: https://github.com/apache/iceberg/issues/8151. > > We wanted there to be an easy way to apply retroactive fixes to older doc > > versions. > > A simple release process can now be automated once we validate things > work well manually by starting a workflow and reviewing a PR. > > Restyle Mkdocs default theme to look like the existing Iceberg theme. > > Fix broken links (there were a lot). > > > > It would be great to get a quick vote on moving forward with this > process. Thanks! > > > > - Bits >
